views:

136

answers:

1

I would like to know why some of the libraries are not released during a normal release cycle. For example, from http://repo2.maven.org/maven2/org/springframework/

while spring-core have 3.0.3-RELEASE, spring-remoting and spring-jmx were released only in 2.0.8. Can someone tell me what this would mean? I agree that if there are no changes in the component say spring-jmx then they don't have to release it, but since 90% of the world uses Maven for dependency management can they not just re-release the same libs (of spring-remoting and spring-jmx?)

I ask this because I declare my deps like,

<dependency>
  <groupId>org.springframework</groupId>
  <artifactId>spring-core</artifactId>
  <version>${spring.version}</version>
</dependency>
<dependency>
  <groupId>org.springframework</groupId>
  <artifactId>spring-remoting</artifactId>
  <version>${spring.version}</version>
</dependency>

and I would prefer supplying one spring.version instead of keeping version numbers upto date for all components?

The four libraries of interest to me are spring-dao, spring-support, spring-jmx, spring-remoting

+5  A: 

spring-remoting and spring-jmx became a part of spring-context, so newer versions are released with spring-context.

axtavt
Thanks @axtavt, Can I ask you what happened to spring-dao and support? Basically how do I find out how/where/if these projects have merged? (I ask this because the next time I have a similar problem I want to know how to find this ....)
Calm Storm
This might help, although the details are sparse: http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/new-in-3.html#new-in-3-modules-build
matt b