[SWS-727] building a webapp targetting Java 1.5 environment on JDK5 and JDK6 pulled in different dependencies for spring-ws-core 2.0.2 Created: 24/Aug/11 Updated: 04/May/12 Resolved: 06/Oct/11 |
|
| Status: | Closed |
| Project: | Spring Web Services |
| Component/s: | Core |
| Affects Version/s: | 2.0.2, 2.0.3 |
| Fix Version/s: | 2.0.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Dejia Meng | Assignee: | Arjen Poutsma |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Building a webapp targetting Java 1.5 envrionment with JDK1.6 as the build environment, doesn't pull in the maven dependency: javax.xml.stream : stax-api, which causes java.lang.ClassNotFoundException: javax.xml.stream.XMLStreamException. The expected result will be that the final artifacts from the build should be the same regardless of the Java version of the build environment. The dependencies should be based on the target Java runtime environment not the build environment. The following is found in spring-ws-core-2.0.2.RELEASE.pom file: <profile> |
| Comments |
| Comment by Arjen Poutsma [ 06/Oct/11 ] |
|
The problem here is that javax.xml.stream is built into JDK 1.6, and not 1.5. Using JDK-profiles at least makes it easy to build, but they are not fool proof, i.e. you'll still have to think about the libraries for the deployment environment. In general, I would not recommend using a different JDK (version) than what deployment uses, but that's another discussion. |
| Comment by Arjen Poutsma [ 04/May/12 ] |
|
Closing old issues |