Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 294872 - org.eclipse.equinox.ds generated in config.ini (osgi.bundles prop) instead of in bundles.info
Summary: org.eclipse.equinox.ds generated in config.ini (osgi.bundles prop) instead of...
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-11 09:37 EST by Dimo Stoilov CLA
Modified: 2019-10-08 10:45 EDT (History)
2 users (show)

See Also:


Attachments
SimpleConfiguratorManipulatorImpl.algorithm() (2.11 KB, text/plain)
2009-11-11 09:37 EST, Dimo Stoilov CLA
no flags Details
sample pde build for reproducing of the issue (2.61 MB, application/x-zip-compressed)
2009-11-12 04:02 EST, Dimo Stoilov CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dimo Stoilov CLA 2009-11-11 09:37:16 EST
Created attachment 151943 [details]
SimpleConfiguratorManipulatorImpl.algorithm()

As a result of our PDE build we have a config.ini that has
org.eclipse.equinox.ds in its osgi.bundles property:
osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.1.0.v20090601.jar@1\:start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.100.v20090520-1905.jar@1\:start.
Is this ok? Shouldn't equinox.ds be in the bundles info instead of in
config.ini - like  in the standart eclipse installtion.

Probable reason:

As seen in ProductGenerator.getDefaultStartInfo()
PDE build generates a p2.inf file that specifies:
...
units.175.id=toolingorg.eclipse.equinox.ds
units.175.instructions.configure=setStartLevel(startLevel:1);markStarted(started:true);
...
units.172.id=toolingorg.eclipse.equinox.simpleconfigurator
units.172.instructions.configure=setStartLevel(startLevel:1);markStarted(started:true);
...

And according to SimpleConfiguratorManipulatorImpl.algorithm() (attached) if a
bundle has a start level <= of the start level of the simple configurator, it
goes to the config.ini
Comment 1 Simon Kaegi CLA 2009-11-11 09:54:56 EST
That's fine.
I personally would tend to use SL 2 for DS so bundle.info would be used exclusively but SL 1 should also be safe.

I believe the DS bundle should "also" be bundles.info. Could you confirm.
Comment 2 Dimo Stoilov CLA 2009-11-11 10:05:28 EST
Yes, DS bundle should also be in the bundles.info, that was what I meant
Comment 3 Andrew Niefer CLA 2009-11-11 10:28:33 EST
Dimo, can you confirm whether ds appears in the bundles.info?  I can see cases where the bundle appears only in bundles.info, or the bundle appears in both config.ini and bundles.info.

But I can't see the case where the bundle only appears in config.ini
Comment 4 Dimo Stoilov CLA 2009-11-11 10:51:39 EST
I saw it in the config.ini, so I assumed it appears only there, but now I checked the bundles.info - and it is there also. 

So it appears in both config.ini and bundles.info
Comment 5 Simon Kaegi CLA 2009-11-11 11:10:04 EST
Ok. Good. Thanks Dimo.
Comment 6 Andrew Niefer CLA 2009-11-11 11:24:54 EST
If it is ok that bundles with start level the same as simpleconfigurator appear in both config.ini and bundles.info, then the only problem here is that it is indeterminant which case you actually end up with (bundles.info only, or both).
Comment 7 Dimo Stoilov CLA 2009-11-12 04:02:12 EST
Created attachment 152015 [details]
sample pde build for reproducing of the issue

I'm not sure whether it is ok to have same bundle on both places. What I meant is the DS bundle should appear only in bundles.info. Right? But currently in our case it appears in both config.ini and bundles.info. 
I attached a sample that this issue can be reproduced with. There you can see all the input and output...
Comment 8 Dimo Stoilov CLA 2009-11-13 03:04:54 EST
as the issue is still open (currently: ds bundle appears in both config.ini and bundles.info, expected: appear only in bundles.info), I'm reopening the bug
Comment 9 Eclipse Genie CLA 2019-03-15 18:28:51 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.
Comment 10 Lars Vogel CLA 2019-10-08 10:45:43 EDT
This bug was marked as stalebug a while ago. Marking as wontfix.

If this report is still relevant for the current release, please
reopen and remove the stalebug whiteboard tag.