Community
Participate
Working Groups
in i0414 There seem to be some cases in which running the director causes a platform.xml and or a bundles.info to be created. I have had a hard time making this happen on purpose but it seems to happen quite often. I suspect it has to do with the presence or absence of simpleconfigurator and whether or not it is marked as started. Unfortunately I can't add much more detail here but will update as I test more. Perhaps others are seeing similar behaviour...
The presence of the platform.xml is probably caused by having the profile set the property causing hte features to be installed (<property name='org.eclipse.update.install.features' value='true'/>). Otherwise it is because it is contained in one of the root file being delivered. Did you notice if the content of the platform.xml was relevant? Next time it happens take a look at the properties of the profile. As for the presence of bundles.info, next time it happens please see if the metadata contains something setting the start level of this bundle and also starting it.
Marking 3.5 to keep in on the radar. Still we need more steps.
wrt the update property. Yes, that property is being set. Perhaps I never noticed it before but I don't recall the platform.xml being generated previously. I did try removing that and it appeared to have eliminated both the platform.xml and the bundles.info. There might be something going on with feature-based vs bundle-based products. Certainly in the former case exporting from the ui gets you a platform.xml. the file has all the right stuff in it. This makes at least some sense as you have features but since Update code is no where in sight its a but unclear why this file is needed. As for the bundles.info file. I did a test last night and found some cases where simply having SC in the configuration caused the bundles.info to be generated and others where SC must be there AND have markup to start it. Of coruse, I cannot reproduce now... On the whole this bug is very unsatisfying. It has been very hard to track things down. Too many moving parts. I have a latent concern that there are some workflows and scenarios that do not work but cannot put my finger on them. Everything I do now to try and reproduce the problems works exactly as expected. That is awesome but sucks at the same time. We can leave this open or close it. either way I will continue to monitor the build stuff and see how it goes.
See this by running org.eclipse.pde.build.tests/PublishingTests#testPublish_FeatureBasedProduct. Set a breakpoint at the end or set the system property "pde.build.noCleanup" to prevent the test artifacts from being cleaned up. See the \junit-workspace\pde.build\featureBasedProduct\I.TestBuild\eclipse-win32.win32.x86.zip which contains "eclipse/configuration/org.eclipse.update/platform.xml". The repository that produced this install is \junit-workspace\pde.build\featureBasedProduct\buildRepo. The product does not contain simple configurator or update configurator.
*** This bug has been marked as a duplicate of bug 272945 ***
