RE: [p2-dev] launcher ini generation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [p2-dev] launcher ini generation

From: "Stoilov, Dimo" <dimo.stoilov@xxxxxxx>
Date: Thu, 6 Aug 2009 09:44:14 +0200
Delivered-to: p2-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/p2-dev>
List-help: <mailto:p2-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/p2-dev>, <mailto:p2-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/p2-dev>, <mailto:p2-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AcoVbFzpFA3rAXueT9uvmgwKrUXWHQA+aDQA
Thread-topic: [p2-dev] launcher ini generation

Hello,

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.

Follow-Ups:
- RE: [p2-dev] launcher ini generation
  - From: Warren_Paul

References:
- Re: [p2-dev] Using remote zip'd repos in p2
  - From: Ian Bull
- Re: [p2-dev] Using remote zip'd repos in p2
  - From: John Arthorne

Prev by Date: Re: [p2-dev] Using remote zip'd repos in p2
Next by Date: RE: [p2-dev] launcher ini generation
Previous by thread: Re: [p2-dev] Using remote zip'd repos in p2
Next by thread: RE: [p2-dev] launcher ini generation
Index(es):
- Date
- Thread

Breadcrumbs