Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346094

Summary: webservice features have open ended requirement for org.jdom
Product: [WebTools] WTP Webservices Reporter: David Williams <david_williams>
Component: jst.ws.jaxwsAssignee: Shane Clarke <shane_clarke>
Status: RESOLVED FIXED QA Contact: Shane Clarke <shane_clarke>
Severity: normal    
Priority: P1 CC: keith.chong.ca
Version: unspecifiedFlags: david_williams: pmc_approved+
Target Milestone: 3.3 RC2   
Hardware: PC   
OS: Linux   
Whiteboard: PMC_approved

Description David Williams CLA 2011-05-17 10:12:42 EDT
2 of the webservice features include org.jdom, but specify it in an "open ended" fashion such that it pulls in the highest available from Orbit. In current cases, that means it gets version 1.1.1 of org.jdom, but as far as I can see, we have opened a CQ for only 1.0.0. This involves two features (that I can see): 

org.eclipse.jst.ws.cxf.feature
org.eclipse.jst.ws.jaxws.feature

If desired to "use the latest" of org.jdom, then a new "piggy back" CQ should be filed. But even then, its best if the feature.xml specifies the specific version we expect, in case a higher version is added to Orbit later. 

But especially since so late for CQs (even though piggy back ones are a little easier), if there is no known reason to require 1.1.1, might be best to simply specify the 1.0.0 version in features, as Dali does, with a plugin specification similar to 

   <plugin
         id="org.jdom"
         download-size="0"
         install-size="0"
         version="1.0.0.qualifier"
         unpack="false"/>

instead of the current form of 

   <plugin
         id="org.jdom"
         download-size="0"
         install-size="0"
         version="0.0.0"
         unpack="false"/>
Comment 1 David Williams CLA 2011-05-17 10:14:37 EDT
Marking as p1, since is _required_ for release ... preferably for this week's RC2 build. 

Of course, if there is already a CQ for us to use 1.1.1, and the auto-check tools are just missing it, and the auto IP log is missing it, then that's fine ... we just need to make sure its in IP log.
Comment 2 Keith Chong CLA 2011-05-17 11:54:53 EDT
Hi Shane,

Please fix the two features for 3.3 RC2.
Comment 3 Shane Clarke CLA 2011-05-17 13:17:33 EDT
Updating the features now.
Comment 4 Shane Clarke CLA 2011-05-17 13:46:06 EDT
Updated and released to HEAD.