You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@activemq.apache.org by Jamie McCrindle <ja...@gmail.com> on 2008/05/22 20:18:37 UTC

AMQ-1132 workaround?

Hi all,

I'm getting hit by AMQ-1132 - the activeio-core-test.jar is being
included by maven and the log4j.properties inside the jar file is
overriding my own log4j.properties (with associated /target/test.log
exception).

Anybody know a workaround in maven. The exclusions mechanism doesn't
allow for a <type>test-jar</type> element...

cheers,
j.

Re: AMQ-1132 workaround?

Posted by Jamie McCrindle <ja...@gmail.com>.

Solved:

    <dependency>
      <groupId>org.apache.activemq</groupId>
      <artifactId>activemq-core</artifactId>
      <version>5.1.0</version>
      <exclusions>
        <exclusion>
          <groupId>org.apache.activemq</groupId>
          <artifactId>activeio-core</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.apache.activemq</groupId>
      <artifactId>activeio-core</artifactId>
      <version>3.1.0</version>
    </dependency>


On Thu, May 22, 2008 at 7:19 PM, Jamie McCrindle
<ja...@gmail.com> wrote:
> I'm using ActiveMQ 5.1.0 and moving to a 5.2.0 snapshot isn't an option...
>
> On Thu, May 22, 2008 at 7:18 PM, Jamie McCrindle
> <ja...@gmail.com> wrote:
>> Hi all,
>>
>> I'm getting hit by AMQ-1132 - the activeio-core-test.jar is being
>> included by maven and the log4j.properties inside the jar file is
>> overriding my own log4j.properties (with associated /target/test.log
>> exception).
>>
>> Anybody know a workaround in maven. The exclusions mechanism doesn't
>> allow for a <type>test-jar</type> element...
>>
>> cheers,
>> j.
>>
>

Re: AMQ-1132 workaround?

Posted by Jamie McCrindle <ja...@gmail.com>.

I'm using ActiveMQ 5.1.0 and moving to a 5.2.0 snapshot isn't an option...

On Thu, May 22, 2008 at 7:18 PM, Jamie McCrindle
<ja...@gmail.com> wrote:
> Hi all,
>
> I'm getting hit by AMQ-1132 - the activeio-core-test.jar is being
> included by maven and the log4j.properties inside the jar file is
> overriding my own log4j.properties (with associated /target/test.log
> exception).
>
> Anybody know a workaround in maven. The exclusions mechanism doesn't
> allow for a <type>test-jar</type> element...
>
> cheers,
> j.
>