[
https://issues.apache.org/jira/browse/WICKET-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569601#action_12569601
]
Timo Rantalaiho commented on WICKET-1348:
-----------------------------------------
I don't think that "provided" would work well in that case,
but maybe it would be a good idea to update the
wicket-spring Spring dependency version to latest stable 2.5
series version? There's a lot of improvements, good
backwards compatibility and in 80 % of cases that should be
more correct than the current spring 2.0.
For a better solution you should probably improve something
in Maven.
> 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.
