[
https://issues.apache.org/jira/browse/WICKET-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569607#action_12569607
]
Martijn Dashorst commented on WICKET-1348:
------------------------------------------
So use a dependencyManagement section in your pom, which overrides the spring
depencency. That is all you need to do. The solution is *not* for Wicket to
make the dependency 'provided'.
Resources:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
http://maven.apache.org/plugins/maven-dependency-plugin/examples/preparing-dependencies.html
> Please Change Scope of Spring Dependencies in pom.xml File
> ----------------------------------------------------------
>
> Key: WICKET-1348
> URL: https://issues.apache.org/jira/browse/WICKET-1348
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-spring
> Reporter: James Carman
>
> The Spring dependencies need to be marked as "provided" or whatever so that
> they're not picked up transitively. Projects using the wicket-spring library
> might want to use a different version of Spring and this can bring about some
> pretty nasty classpath errors to track down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
