Community
Participate
Working Groups
Build Identifier: 20100617-1415 The first Build All for an update site project works just fine, but subsequent builds damage the categories. This means that the generated update site is correct only after the first build. Cleaning it and running Build All for the second/third/etc time generates different content/artifacts.xml, making Eclipse not recognize the categories. Reproducible: Always Steps to Reproduce: 1. create an update site project, add a category and a feature 2. build the project 3. use it as an update site; the category will be visible 4. clear the project (remove the .jar files from features/*.jar, plugins/.jar, artifacts.jar, content.jar) 5. build again the project 6. use it as an update site; the category will NOT be visible 7. clear the project (remove the .jar files from features/*.jar, plugins/.jar, artifacts.jar, content.jar) 8. in the site.xml graphical window, remove the feature below the category 9. add again the feature 10. build the project 11. use it as an update site; the category will again be visible!!!
Created attachment 175575 [details] side to side comparison of good/bad generated files the archive contains artifacts.xml/content.xml for the first and second build. there are obvious differences between them, from the order of elements to more complex differences.
*** Bug 321285 has been marked as a duplicate of this bug. ***
Let me see what's going on here. I'm not sure if this is a PDE thing or a p2 thing.
Ian please update the target milestone.
Sorry, I've not had a chance to look at this.
When creating update sites in this way, I find that the categories show up only occasionally, and not necessarily the first time I build the site.
This bug make me crazy ... how "update site" project can be used ???!!!
Yeah, this is a serious bug IMO.
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.
I'm not able to test it right now due to a reinstalling blues... :-( Perhaps someone else can check?
