activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuomas Kiviaho (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-1884) maven-activemq-plugin doesn't have proper VM transport support
Date Thu, 14 Aug 2008 08:45:52 GMT
maven-activemq-plugin doesn't have proper VM transport support
--------------------------------------------------------------

                 Key: AMQ-1884
                 URL: https://issues.apache.org/activemq/browse/AMQ-1884
             Project: ActiveMQ
          Issue Type: Wish
          Components: Broker
    Affects Versions: 5.1.0
            Reporter: Tuomas Kiviaho
            Priority: Minor


I tried to use broker by forking it for integration test purposes, but noticed that VM transport
doesn't work because of maven classloader created duplicate VMTransportFactory.class instances
<http://maven.apache.org/guides/mini/guide-maven-classloading.html>.

 I even tried to create a plexus container singleton-keep-alive component <http://plexus.codehaus.org/ref/component-configuration.html>
from broker service in order to make sure that same instance of VMTransportFactory is shared
thorough integration test phases. This way I was able to create start stop goals for the plugin
which worked great at pre and post integration test phases but component failed to exist in
different plugins at integration test phase. 

I guess the right approach is to introduce a maven build extension <http://docs.codehaus.org/display/MAVEN/Maven+2.1+Plugin+and+Extension+Loading+Design>

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


Mime
View raw message