[
https://issues.apache.org/jira/browse/WICKET-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569628#action_12569628
]
James Carman commented on WICKET-1348:
--------------------------------------
Interestingly enough, Maven2 is smart enough to use the latest version of the
dependency. If my project declares a dependency on artifactId=spring
version=2.5.1, then the only thing on my classpath (even with the transitive
dependency declared by wicket-spring) would be spring-2.5.1.jar and not
spring-2.0.jar. Is it your experience that most people use the "spring"
artifact and not a combination of the spring-* artifacts (like orm, tx, core,
context, etc.)? I usually try to piece together what I need out of the
smaller jars, but maybe I'm just doing too much work! Anyway, I guess this is
no big deal and maven appears to be doing all that it can to help by using the
latest version of the library. Should we close this issue and start another
one to "upgrade" wicket-spring's spring dependency to 2.5.1?
> 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.
