[
http://jira.codehaus.org/browse/MPTEST-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121979
]
David Wong commented on MPTEST-13:
----------------------------------
Hi,
Has this issue been fixed? When I do mvn -X to see the classpath when running
an unit test; the build path is still before the test path. I'm running Maven
4.2.
[DEBUG] Test Classpath :
[DEBUG] W:\data\ejb\target\classes
[DEBUG] W:\data\ejb\target\test-classes
[DEBUG] ...
Shouldn't test path be come before the build path?
Thanks,
David
> Order of classpath entries should be changed
> --------------------------------------------
>
> Key: MPTEST-13
> URL: http://jira.codehaus.org/browse/MPTEST-13
> Project: Maven 1.x Test Plugin
> Issue Type: Bug
> Reporter: Michal Maczka
> Attachments: test-diff.txt, test.zip
>
>
> Behavior of my application is controlled through set of configuration
> files(like log4j.propertrties).
> I want to control behavior of my application differently for the test
> environment and differently for the production environment.
> The problem is that currently in maven the "production" resources are
> preceding the test resources in the classpath
> and [test] plugin is always taking them in first order.
> I am including short example showing where is the problem.
> Basically in it I have two log4j.properties files: one in
> 'test-resources', second in 'resources' directory.
> This example shows that the the one kept in test-resources is never used and
> it is not possible to easily control
> the "test environment" when it is overlapping with "production'
> environment".
> As a result of this program the output of log statements is always written to
> production.log. Test resources are containing log4j.properties file which
> configures the log system for tests and directs log statements to a file
> test.log. This example shows that
> this file is never created.
> Other problem here is: if any of the dependencies in the classpath contains
> log4j.properties this file will even preceeds the log4j.properties in the
> classpath.
> So the best solution in my opinion will be to have followiing order of
> entries in the class path:
> <classpath>
> <pathelement location="${maven.test.dest}"/>
> <path refid="maven.dependency.classpath"/>
> <pathelement location="${maven.build.dest}"/>
> <pathelement path="${plugin.getDependencyPath('junit')}"/>
> </classpath>
> The problem is generic and not only typical to log4j. The same applies for
> example to jndi.properties.
> Michal Maczka
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
