[
https://issues.apache.org/jira/browse/WICKET-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569600#action_12569600
]
James Carman commented on WICKET-1348:
--------------------------------------
I don't care what it's set to. I just don't want maven it to automatically
include spring-2.0.jar in my application when I want to use wicket-spring (I'm
currently wanting to use spring-2.5.1). That's the goal. I don't want to have
to do an exclusion in my dependency to get it to exclude the transitive
dependency. The only scope that I'm aware of that's not transitive is
"provided" which means that the runtime environment will provide this
dependency (or a compatible version of it).
> 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.
