[
https://issues.apache.org/jira/browse/WINK-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890780#action_12890780
]
Bryant Luk commented on WINK-300:
---------------------------------
I prefer option 2 as well unless anyone has an objection.
> Update Spring version to 3.0 or change spring dependency scope 'provided'
> -------------------------------------------------------------------------
>
> Key: WINK-300
> URL: https://issues.apache.org/jira/browse/WINK-300
> Project: Wink
> Issue Type: Improvement
> Components: Spring
> Affects Versions: 1.1.1
> Reporter: Michael Elman
> Priority: Minor
>
> Currently the spring-support module depends on the aggregated jar of 2.5.
> However, since 3.0, Spring doesn't provides an aggregated jar anymore.
> So, when running with 3.0 and Wink, all spring jars must be specified and 2.5
> aggregated jar must be excluded.
> There are two possible fixes:
> 1. Mark Spring dependency as 'provided'. This will eliminate the exclude, but
> will force to specify the spring dependency manually, which is ok, since none
> should be using the spring-support module without using spring by himself.
> 2. Specify the concrete dependency (spring-context, spring-core, anything
> else?) instead of the aggregated jar.
> Let me know what do you think about these options. Personally I prefer option
> 2 and also moving to Spring 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
