Mule

Rename "spring" module to "spring-extras" for 2.0

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.0.0-RC1
  • Fix Version/s: 2.0.0-RC2
  • Component/s: Modules: Spring
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    MULE-1836 Spring extras module fails to pass tests in 2.0
    MULE-1585 Clean up the Spring Module
    MULE-3885 Support for Spring Security (Acegi 2.0)
    MULE-4052 spring-jms and spring-jdbc should be declared as provided
    MULE-518 Use CommonJ work manager support in Spring 2.0
    MULE-517 Support Spring 2.0 configuration using Namespace Handlers
    MULE-2062 Mule extensions to spring cause the parsing/instantiation of some spring beans to fail
    MULE-1257 Upgrade spring-modules to v0.8
    MULE-5225 Upgrade Spring Security to 3.0.3
    MULE-1316 Move Spring 2.x into the core

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment - 07/Jan/08 01:27 PM

Dan, I think you are closing a circle here. It was called something like that already, and got renamed to simply spring. Is there a real benefit in going back now?

Show
Andrew Perepelytsya added a comment - 07/Jan/08 01:27 PM Dan, I think you are closing a circle here. It was called something like that already, and got renamed to simply spring. Is there a real benefit in going back now?
Hide
Permalink
Daniel Feist added a comment - 07/Jan/08 02:11 PM

This was the conclusion we came to last week with Ross.

Here's the reasoning:

  • Spring configuration code is being pulled out of mule-core into it's own module.
  • Spring configuration code can't go into the existing "spring" module because of dependency issues.
  • A new module called "spring-config" was decided on for the spring configuration code.
  • It was decided to rename "spring" module to "spring-extras" so as to reduce ambiguity about what the "spring" module is about and reduce confusion about which modules users need for what.
Show
Daniel Feist added a comment - 07/Jan/08 02:11 PM This was the conclusion we came to last week with Ross. Here's the reasoning:
  • Spring configuration code is being pulled out of mule-core into it's own module.
  • Spring configuration code can't go into the existing "spring" module because of dependency issues.
  • A new module called "spring-config" was decided on for the spring configuration code.
  • It was decided to rename "spring" module to "spring-extras" so as to reduce ambiguity about what the "spring" module is about and reduce confusion about which modules users need for what.

People

Vote (0)
Watch (0)

Dates

  • Created:
    07/Jan/08 01:06 PM
    Updated:
    08/Jan/08 05:17 PM
    Resolved:
    08/Jan/08 05:17 PM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.