Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <22763594.8101271776455263.JavaMail.jira@thor>
Date: Tue, 20 Apr 2010 11:14:15 -0400 (EDT)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-2702) Localize Spring-related classes in a
 separate module
In-Reply-To: <25812368.8081271775853598.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58979#action_58979 ] 

Dejan Bosanac commented on AMQ-2702:
------------------------------------

rev 935952 introduced activemq-spring module and moved a few classes there. Incidentally activemq-pool module doesn't have spring dependency any more.

The main question is what should we do with all tests in activemq-core (and other modules), that depends on Spring (and preventing us to do a better separation). IMHO we should move them either in this newly-created activemq-spring module or activemq-all module or even previously created sys test project. It will require some refactoring and probably make debugging a bit harder, but I think it's the move we have to make. 

> Localize Spring-related classes in a separate module
> ----------------------------------------------------
>
>                 Key: AMQ-2702
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2702
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.3.1
>            Reporter: Dejan Bosanac
>
> We should try reducing Spring dependency on the broker core (and other modules) and move all Spring-related classes in a separate module.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.