[
https://issues.apache.org/activemq/browse/AMQ-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56373#action_56373
]
Werner Guttmann commented on AMQ-2211:
--------------------------------------
Even worse, the second (test) dependency causes some ugly behaviour with log4j
initialization in our environment, as it contains a {{log4j.properties}} 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 {{log4j.properties}}
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.
Personally, I consider this to be reason enough to ship a new Maven release
that fixes this, especially as the fix is easy to apply. And yes, I know
there's a work-around.
> activemq-core activeio-core test-jar
> ------------------------------------
>
> Key: AMQ-2211
> URL: https://issues.apache.org/activemq/browse/AMQ-2211
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Reporter: Finn J Johnsen
>
> activemq-core has the following 2 dependecies to activeio-core:
> <dependency>
> <groupId>${pom.groupId}</groupId>
> <artifactId>activeio-core</artifactId>
> <optional>false</optional>
> </dependency>
> ...
> <dependency>
> <groupId>${pom.groupId}</groupId>
> <artifactId>activeio-core</artifactId>
> <optional>false</optional>
> <type>test-jar</type>
> </dependency>
> The <type>test-jar</type>dependency should also be <scope>test</test>. With
> the current setting, you get the test-jar bundled (transitively) when
> including activemq-core.
> Correct me if i'm wrong...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
