Announcement Announcement Module
No announcement yet.
why move the class amount maven packages all the time ? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • why move the class amount maven packages all the time ?


    I understand that there was quite some changes in the packaging(where classes are packaged in which maven package/jar) from 2.0.x to 2.5 and I can understand that it may be necessary and it being a half version upgrade, can be expected(though I hope there is some documentation about them).

    However, why would there be such change when going from 2.5 -> 2.5.1 ?

    org.springframework.web.bind.* now moved from spring-web to spring-webmvc.

    The result is every upgrade is painful unless I don't use maven and just drop all the jars from the spring package into say WEB-INF/lib

  • #2
    You could just use the spring.jar instead of the separate modules, that would save you many of the changes during an update.


    • #3
      I know.

      But in that case, there isn't that much point to have them seperate in various packages, just release one single maven package that includes everything, from the very beginning. Or just stop releasing seperate maven packages and have only one giant one starting from 2.5.1