activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pieter Iserbyt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1132) activeio test package inclusion and logging properties
Date Mon, 18 Aug 2008 15:11:53 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45031#action_45031
] 

Pieter Iserbyt commented on AMQ-1132:
-------------------------------------

In my case, upgrading to maven 2.0.9 fixed my issues. The test jar is still included, but
does not trigger the log4j problem somehow (don't ask me why, I'm totally confused).

> activeio test package inclusion and logging properties
> ------------------------------------------------------
>
>                 Key: AMQ-1132
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1132
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: incubation
>            Reporter: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> When you include activemq-core as a dependency on an empty project, even simplest examples
fails with
> java.io.FileNotFoundException: /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 logging.properties 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.


Mime
View raw message