ActiveMQ
  1. ActiveMQ
  2. AMQ-1884

maven-activemq-plugin doesn't have proper VM transport support

    Details

    • Type: Wish Wish
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 5.1.0
    • Fix Version/s: NEEDS_REVIEW
    • Component/s: Broker
    • Labels:
      None

      Description

      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>

        Activity

        Hide
        Claus Ibsen added a comment -

        VM transport is only intended for running in same JVM, not when forking the JVM.

        Show
        Claus Ibsen added a comment - VM transport is only intended for running in same JVM, not when forking the JVM.

          People

          • Assignee:
            Claus Ibsen
            Reporter:
            Tuomas Kiviaho
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development