Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317235

Summary:	[launcher] upversion launchers for 3.7
Product:	[Eclipse Project] Equinox	Reporter:	Andrew Niefer <aniefer>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	tjwatson
Version:	3.4.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Andrew Niefer

2010-06-17 15:56:54 EDT

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)

Comment 1 Thomas Watson

2010-06-17 16:12:26 EDT

Assuming a bug like bug149994 goes in where we add new command line options.  Should we consider moving up the minor versions?

Comment 2 Andrew Niefer

2010-06-17 16:21:04 EDT

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.

Comment 3 Thomas Watson

2010-08-23 17:50:51 EDT

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.

Comment 4 DJ Houghton

2010-08-24 09:41:12 EDT

I updated the fragment-host range requirements to accept the new launcher versions due to bug 323488.

Comment 5 Eclipse Webmaster

2019-09-06 16:07:07 EDT

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.

Comment 6 Eclipse Genie

2021-08-31 16:55:00 EDT

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.