Bugzilla – Full Text Bug Listing
| Summary: | two features conflict during unit test install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Releng | Reporter: | David Williams <david_williams> | ||||
| Component: | releng | Assignee: | David Williams <david_williams> | ||||
| Status: | RESOLVED FIXED | QA Contact: | David Williams <david_williams> | ||||
| Severity: | normal | ||||||
| Priority: | P1 | ||||||
| Version: | 3.10 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
One side of this coin is that I was mistakenly installing the unit tests twice, once from those just built, and then again from the previous release. (The "previous release" install is purposely done at time, when we just build part of WTP, such as a patch .. and simply want to rerun previous tests, and I just let scripts leak into each other). But, the other side of the coin is that it shouldn't matter ... well, shouldn't cause a P2 error, that is. This indicates there is (already) a feature that has exact same ID, but different content ... another manifestation of bug 208143. So, I'll leave this bug open until that's fixed, as a reminder not to declare a build with that error. Might also serve as a test case to see if 'comparator' can catch this type of error. I managed to "hack in" a comparator test against our 3.2.2 release, and sure enough, it "caught" one error. The way it "expressed" the error was as below (which is different that the way p2 install would express the error, but bottom line is that org.eclipse.wst.ws_sdk.feature has exact same version, but different contents. From there it'd take some detective work to dig down and figure out exactly what should be incremented ... but could probably use VersioningReport to see that had change and needed service field increment. For cross reference, see also bug 325181 and bug 322601. I'll count this bug as fixed, and track other work in those two bugs ... well, and eventually before any build is "declared" we need to make sure there is none of these errors in what we distribute. = = = = canonical: org.eclipse.update.feature,org.eclipse.wst.ws_sdk.feature,3.2.2.v201008211705-793AD9xVEIMfbS0PCYMeFWvUNJge Difference found for canonical: org.eclipse.update.feature, org.eclipse.wst.ws_sdk.feature,3.2.2.v201008211705-793AD9xVEIMfbS0PCYMeFWvUNJge between file:/shared/webtools/comparatorStandardRepos/maintenance/R-3.2.2-20100915173744/repository/ and file:/shared/webtools/projects/wtp-R3.2.3-M/workdir/M-3.2.3-20100929043917/buildrepository/jst-sdk The entry "Feature: org.eclipse.wst.ws_ui.feature 3.2.2.v201008211705-7I78FZFEtEoO2c5BlJ4jPNwNC-yS" is not present in both features. The entry "Feature: org.eclipse.wst.ws_ui.feature.source 3.2.2.v201008211705-7I78FZFEtEoO2c5BlJ4jPNwNC-yS" is not present in both features. |
Created attachment 179797 [details] log from one run showing issue. In recent M builds, when we go to "install" WTP into a test installation (using p2, not unzipping) we get an error that there is conflicting dependencies. Can't install two versions of xml_core feature, basically. And this is "included" by other WTP features. (indirectly, via xml_ui feature and xml_sdk feature). Ultimately, it is org.eclipse.jst.web_sdk.feature that includes one version of xml, and org.eclipse.wst.ws_sdk.feature that includes another version. I don't see how this is possible, but noticed only recently, after WTP 3.2.2 delivered. Two things changed since then ... one of which is using p2 to install ... I think we were just unzipping previously, in that stream. Two, we moved up to 36_RC4 version of base builder ... was using 36_RC2 version.