Spring Framework
  1. Spring Framework
  2. SPR-2011

Remove rebundling of aopalliance inside spring-aop.jar

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.7, 2.0 M3, 2.0 M4
    • Fix Version/s: 2.0 M5
    • Component/s: Core:AOP
    • Labels:
      None
    • Last commented by a User:
      false

      Description

      I don't see the need of putting aopalliance classes inside the spring jars, why is this dependency different than all the other ones?

        Activity

        Hide
        Juergen Hoeller added a comment -

        This was actually changed for Spring 1.2; the AOP Alliance classes had to be linked in explicitly before.

        The reasoning here is that the AOP Alliance interfaces are often used implicitly, even more so in Spring 2.0. We just wanted to avoid forcing people to worry about adding an aopalliance.jar just for implicit use of AOP, for example through a TransactionProxyFactoryBean or an <aop:config> definition that only refers to pre-built interceptors.

        As we haven't heard of any problems with this up to now, we do not have any plans of changing this approach.

        That said, I tend to agree that spring-aop.jar should probably not include the AOP Alliance classes anymore, since it's intended for use in a multi-jar environment anyway. This would mean that only the full spring.jar, provided as a convenience over the fine-grained jars, would include the AOP Alliance classes.

        Juergen

        Show
        Juergen Hoeller added a comment - This was actually changed for Spring 1.2; the AOP Alliance classes had to be linked in explicitly before. The reasoning here is that the AOP Alliance interfaces are often used implicitly, even more so in Spring 2.0. We just wanted to avoid forcing people to worry about adding an aopalliance.jar just for implicit use of AOP, for example through a TransactionProxyFactoryBean or an <aop:config> definition that only refers to pre-built interceptors. As we haven't heard of any problems with this up to now, we do not have any plans of changing this approach. That said, I tend to agree that spring-aop.jar should probably not include the AOP Alliance classes anymore, since it's intended for use in a multi-jar environment anyway. This would mean that only the full spring.jar, provided as a convenience over the fine-grained jars, would include the AOP Alliance classes. Juergen
        Hide
        Juergen Hoeller added a comment -

        Removed AOP Alliance interfaces from spring-aop.jar; the aopalliance.jar needs to be added explicitly for such a scenario now. However, spring.jar still does include the AOP alliance interfaces as a convenience (since many users do not even know or care about AOP Alliance in the first place, despite it being required for any use of AOP under the covers).

        Juergen

        Show
        Juergen Hoeller added a comment - Removed AOP Alliance interfaces from spring-aop.jar; the aopalliance.jar needs to be added explicitly for such a scenario now. However, spring.jar still does include the AOP alliance interfaces as a convenience (since many users do not even know or care about AOP Alliance in the first place, despite it being required for any use of AOP under the covers). Juergen

          People

          • Assignee:
            Juergen Hoeller
            Reporter:
            Carlos Sanchez
            Last updater:
            Trevor Marshall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              7 years, 47 weeks, 5 days ago