Maven Evangelism

spring-support should have all dependencies be optional

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Resolution: Won't Fix
  • Component/s: Dependencies
  • Labels:
    None
  • Group ID:
    org.springframework
  • Artifact ID:
    spring-support
  • Version:
    1.2.6

Description

All the dependencies in spring-support should have <optional>true</optional> added. spring-support consists of miscellaneous supporting utility clases. So, for instance, if I'm using the EHCache features, then I don't need any of the other dependencies.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Carlos Sanchez added a comment -

This is fixed in 2.0m1 and will be fixed in 1.2.7 if it goes out.
I'm reluctant to make changes in 1.2.6 as it has become pretty stable.
It'd be nice if you could raise your voice in spring forums/mailing lists to ask them to split spring-support in submodules, it worked with the orm stuff that in 2.0 is already splitted.

Show
Carlos Sanchez added a comment - This is fixed in 2.0m1 and will be fixed in 1.2.7 if it goes out. I'm reluctant to make changes in 1.2.6 as it has become pretty stable. It'd be nice if you could raise your voice in spring forums/mailing lists to ask them to split spring-support in submodules, it worked with the orm stuff that in 2.0 is already splitted.
Hide
Permalink
Stephen Duncan Jr added a comment -

Ok. I'll look and see where I can bring this up with Spring.

The only reason it's a pain not to have optional set correctly in the POM is because I can't really rely on using dependencyManagement in a parent POM because of http://jira.codehaus.org/browse/MNG-1557 & http://jira.codehaus.org/browse/MNG-1797

But I don't think anybody else in my organization is likely to use the other excluded pieces with Maven anytime soon. So, as long as it's done in future versions, that's good enough for me.

Show
Stephen Duncan Jr added a comment - Ok. I'll look and see where I can bring this up with Spring. The only reason it's a pain not to have optional set correctly in the POM is because I can't really rely on using dependencyManagement in a parent POM because of http://jira.codehaus.org/browse/MNG-1557 & http://jira.codehaus.org/browse/MNG-1797 But I don't think anybody else in my organization is likely to use the other excluded pieces with Maven anytime soon. So, as long as it's done in future versions, that's good enough for me.
Hide
Permalink
Carlos Sanchez added a comment -

Will be fixed in next versions, not in 1.2.6

Show
Carlos Sanchez added a comment - Will be fixed in next versions, not in 1.2.6

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.