| [wtp-dev] WTP 3.6.1 features may get reverted to 3.6.0 on p2 install (bug 446465) |
Folks,
For WTP 3.6.1 (Luna SR1), we went through a conversion of our build from CruiseControl/PDE to CBI using Tycho/Maven/Hudson. One of the "benefits" of doing this is that tagging map files is no longer required- qualifiers are based off of commit times, not a tag. One of the things we lost was automated version checking- the Releng team is working on restoring that for WTP 3.6.2. So for WTP 3.6.1, we did a version check by hand. Mistakes were made. An example of this is org.eclipse.wst.server_adapters.feature, which had a version of 3.2.400.v20140501_1027-7L3FJPCcNBHRBuJmLBVNB for WTP 3.6.0 and 3.2.400.v201405011426 for WTP 3.6.1. Tags such as these were left alone- obviously the content had not changed in the WTP 3.6.1 release, and the CBI qualifier appeared to be newer- both are dated May 1, 2014, the PDE tag has a time stamp of 1027 and the CBI has a time stamp of 1426. However, p2 does not judge by parsing the time stamp, it compares the strings, and the underscore in the tag is deemed to be of later value (greater than) the 1 digit for the CBI time, thus the WTP 3.6.0 features are judged to be "newer". This can cause some WTP 3.6.0 features to overwrite the WTP 3.6.1 versions, resulting in a mixed install. Full details of this can be found in https://bugs.eclipse.org/bugs/show_bug.cgi?id=446465 .
The question is, what do we do now? And what impact will this have on adopters? The best place for discussion of that would be https://bugs.eclipse.org/bugs/show_bug.cgi?id=446465 - if you have any questions/comments/concerns/ideas, please add a comment. I have also opened up four other bugs, linked from that one, to get all of the features in question to raise their version id for our next WTP release. I apologize for the inconvenieces that this has caused, but unfortunately things like this happen when a transition of build systems occurs.
FWIW,
- Carl Anderson
WTP Build guy