Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

building a webapp targetting Java 1.5 environment on JDK5 and JDK6 pulled in different dependencies for spring-ws-core 2.0.2 [SWS-727] #818

Closed
gregturn opened this issue Aug 24, 2011 · 2 comments
Assignees
Milestone

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Aug 24, 2011

Dejia Meng opened SWS-727 and commented

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>
    <id>jdk15</id>
    <activation>
        <jdk>!1.6</jdk>
    </activation>
    <dependencies>
        <dependency>
            <groupId>javax.xml.stream</groupId>
            <artifactId>stax-api</artifactId>
        </dependency>

Affects: 2.0.2, 2.0.3

@gregturn
Copy link
Member Author

@gregturn gregturn commented Oct 6, 2011

Arjen Poutsma commented

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.

@gregturn
Copy link
Member Author

@gregturn gregturn commented May 4, 2012

Arjen Poutsma commented

Closing old issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.