Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 314171 - [publisher] ProductPublisherApplication should not depend on a pre-existing config.ini file to generate the bundles.info
Summary: [publisher] ProductPublisherApplication should not depend on a pre-existing c...
Status: RESOLVED INVALID
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-24 18:26 EDT by Hugues Malphettes CLA
Modified: 2010-05-26 17:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hugues Malphettes CLA 2010-05-24 18:26:14 EDT
Currently to get the ProductPublisherApplication to generate the org.eclipse.equinox.simpleconfigurator/bundles.info it is necessary to generate a config.ini file and that file must contain the property:
"org.eclipse.equinox.simpleconfigurator.configUrl"

This is because ProductFileAdvice#createDataLoader() returns null if no config.ini file could be located and also because the org.eclipse.equinox.internal.p2.publisher.eclipse.DataLoader is looking for that property.

It would be a good enhancement to support generating everything from the product file. For example when we see that the product file defines org.eclipse.equinox.simpleconfigurator in the autostart bundles with the level-1 the publisher could generate the rest of the config for the simpleconfigurator and bundles.info.
Comment 1 Hugues Malphettes CLA 2010-05-26 17:20:10 EDT
This was happening when I was having director install into an existing non-p2-abled eclipse application.
When installing in a brand new folder there is no such issue.
I don't think this is an interesting situation to support.

Sorry for the noise.