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

Bug 263783

Summary:	[launcher] Add p2.inf for -startup and --launcher.library
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:	caniszczyk, contact, irbull, tjwatson
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Andrew Niefer

2009-02-05 09:23:23 EST

See bug 260066 comment 27
p2 metadata generation currently special cases the launchers and adds configuration actions for the launcher and fragments.  We should consider instead adding META-INF/p2.inf files to the launcher pieces.

org.eclipse.equinox.launcher/META-INF/p2.inf:
instructions.configure = \
           addProgramArg(programArg:-startup);\
           addProgramArg(programArg:@artifact);
instruction.unconfigure= \
           removeProgramArg(programArg:-startup);\
           removeProgramArg(programArg:@artifact);

org.eclipse.equinox.launcher.*/META-INF/p2.inf
instructions.configure = \
           addProgramArg(programArg:--launcher.library);
           addProgramArg(programArg:@artifact);
instruction.unconfigure= \
           removeProgramArg(programArg:--launcher.library);
           removeProgramArg(programArg:@artifact);

Comment 1 Thomas Watson

2009-02-11 10:43:37 EST

We had a long discussion about this at the equinox call.  Andrew wrote up a proposal at http://wiki.eclipse.org/Equinox/p2/GeneratingCUs

If I understand the proposal correctly the p2.inf containing the configuration actions of the launcher bundles would be contained in the RCP configure feature.  Is that correct?

Comment 2 Andrew Niefer

2009-03-06 16:17:35 EST

Removing target milestone.  At this time pde.build is adding these as default generated CUs.

Comment 3 Eclipse Genie

2019-05-18 18:52:40 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.

--
The automated Eclipse Genie.