Description David Williams 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"/>