activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Guttmann (JIRA)" <>
Subject [jira] Commented: (AMQ-1132) activeio test package inclusion and logging properties
Date Thu, 10 Dec 2009 19:37:53 GMT


Werner Guttmann commented on AMQ-1132:

Actually, running into this problem again using Maven 2.1.0, and I don't think it's actually
related to Maven at all.

In our case, the second (test) dependency causes some ugly behaviour with log4j initialization
in our environment, as it contains a {{}} file. When ''introduced'' into a
web container in our case, you start relying on the sequence of how JARs are loaded. In our
case, this {{}} unfortunately initialized log4j in such a way that our project
logging settings never were applied, as the ones from activeio-core had been picked up before.
And that made it hard for us - during a functional testing period - to diagnose problems we
had as we lost parts of our logging messages.

Can anybody pretty please look into this and have it fixed for 5.4.0 ?

> activeio test package inclusion and logging properties
> ------------------------------------------------------
>                 Key: AMQ-1132
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: incubation
>            Reporter: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.4.0
> When you include activemq-core as a dependency on an empty project, even simplest examples
fails with
> /target/test.log (No such file or directory)
> exception.
> First of all, the core package includes dependency on activeio-core test jar 
>     <dependency>
>       <groupId>${pom.groupId}</groupId>
>       <artifactId>activeio-core</artifactId>
>       <optional>false</optional>
>       <type>test-jar</type>
>     </dependency>
> for which I'm not sure is needed.
> Second, in this test activeio package is configured so that root logger
writes into ${basedir}/target/test.log, which causes application to fail. It would be better
to set it to write to stdout by default.

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

View raw message