[SWS-681] Manifest files in 2.0.0 release are incorrect Created: 17/Jan/11 Updated: 04/May/12 Resolved: 21/Mar/11
|Project:||Spring Web Services|
|Affects Version/s:||2.0 GA|
|Reporter:||Casey Hadden||Assignee:||Arjen Poutsma|
|Original Estimate:||Not Specified|
The manifest files in the 2.0 release jars appear incorrect.
The spring-ws-core jar does not include OSGi information, while the spring-ws-security jar and others reference the 2.0.0.M4 release.
|Comment by Richard Kettelerij [ 13/Feb/11 ]|
This turns out to be an issue for Apache Camel, see https://issues.apache.org/jira/browse/CAMEL-3659.
|Comment by David Geary [ 15/Mar/11 ]|
Also ensure that javax package imports do not include version numbers (or are verison "0") where possible (ie for packages now part of java se)
eg in spring ws 1.5.9 the imports are (extract from manifest)
whereas in spring ws 2.0.0.M1 more versions are referenced ie
compared to core spring (3.0.5) where the imports are just
Since spring ws currently forces the version, to get the spring ws bundles resolved you need to install additional bundles (eg javax.xml.stream) but even then this will cause a conflict with core spring which gets wired to the underlying JRE javax classes.
Not having the version number allows the everything to pick up the underlying JRE javax classes.
|Comment by Arjen Poutsma [ 21/Mar/11 ]|
This should be fixed now.
I've uploaded a new snapshot for you to verify. Could you please download this snapshot and see if the manifests are correct now?
|Comment by David Geary [ 21/Mar/11 ]|
Seems to be fixed, tested on Karaf - the snapshot bundles install and resolve now.
|Comment by Arjen Poutsma [ 04/May/12 ]|
Closing old issues