[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [p2-dev] launcher ini generation
|
Hello,
Any reply appreciated.
Thanks,
Dimo
I tried
with p2.gathering=true only, and also with
both p2.gathering=true &
org.eclipse.pde.build.append.launchers=false but with no
success. There is no launcher generated but
unfortunately there is an empty eclipse.ini generated. This seems to be an
issue with the p2 director.
Thanks,
Dimo
I'm not sure exactly, but the launcher.ini
may only be generated if there is content to put in it. This will depend
on the metadata. By default, pde.build will
generate metadata that automatically sets -startup and --launcher.library in the
.ini. Similarly any program/jvm args in the product file will be placed
there. So, yes, in a headless build,
setting includeLaunchers=false may be sufficient. If you still want the launcher jar and fragments, it gets
trickier. If you are building using p2.gathering=true, you can create a
p2.inf beside your .product file and set "org.eclipse.pde.build.append.launchers=false". I don't know if
there is any way to suppress these arguments if you are using
p2.generate.metadata. -Andrew
From:
| <Warren_Paul@xxxxxxx>
|
To:
| <p2-dev@xxxxxxxxxxx>
|
Date:
| 08/06/2009 05:31 AM
|
Subject:
| RE: [p2-dev] launcher ini generation
|
Sent by:
| p2-dev-bounces@xxxxxxxxxxx |
Isn't there a includeLaunchers=false
switch that you can provide as part of the pde build process?
_Paul
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stoilov, Dimo
Sent: 06 August 2009
08:44
To: P2 developer discussions
Subject: RE: [p2-dev]
launcher ini generationHello,
Is it possible to skip the generation
of launcher ini during bundles installation? I thought this depends on the combination of the config.ini and the
profile properties. I provide no launcherName property, but a default
eclipse.ini is generated. If I provide no installFolder and no
osgi.install.area then a NPE happens in org.eclipse.equinox.internal.frameworkadmin.equinox.ParserUtils.getOSGiInstallArea()
- launcherData.getLauncher().getParentFile()
is null. Thanks,
Dimo
P.S. Our osgi app structure is different from
the eclipse "eclipse/plugins" one. _______________________________________________
p2-dev
mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev