[
https://issues.apache.org/jira/browse/WINK-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved WINK-300.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.2
Fixed, we are now using Srping 3.0.5.RELEASE
> 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
> Fix For: 1.2
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
