Community
Participate
Working Groups
Need to upversion the launchers in head. executable feature goes 3.4.0 -> 3.4.100 most fragments are 1.1.0 -> 1.1.100 gtk.linx.ppc64 is 1.0.0 -> 1.0.100 (fragment was new in 3.6) win32.win32.ia64 is 1.2.0 -> 1.2.100 (? looks like 1.2.0 was a mistake)
Assuming a bug like bug149994 goes in where we add new command line options. Should we consider moving up the minor versions?
Yes I think so. I've already made the changes outlined in comment #0 since I just recompiled the binaries to pick up changes for several bug fixes for 3.7M1. I'll leave this open pending bug 149994.
I updated the org.eclipse.equinox.launcher to version 1.2 because of the fix in bug 323422 to consume the new arguments in 3.7.
I updated the fragment-host range requirements to accept the new launcher versions due to bug 323488.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
