Eugene Kuleshov wrote:
Mohan, first of all allow me to thank you for trying out not announced
dev build and also for a colorful problem description. I especially
admire parts about "clobbers <properties> element" and "wreaking havoc".
:-)
I have just upgraded and have yet another problem with test classpath
resolution.
Some time ago the classpath resolution changed:
moduleA
1) /src/main/resources
2) /src/test/resources
moduleB/
3) /src/main/resources
4) /src/test/resources
running a test in moduleB once had all 4 paths on classpath. Later on
the build was changed to reflect the actual command line behavior.
Now running the test in module B gets 1) 3) and 4) into the classpath.
If one wants 2) this has to be used:
<dependency>
<groupId>...</groupId>
<artifactId>moduleA</artifactId>
<scope>test</scope>
<classifier>tests</classifier>
</dependency>
up until todays version. My application loads property files from
classpath. Today this happened:
INFO 2008-12-01 13:28.00:453 [PropertyPlaceholderConfigurer] Loading
properties file from file
[C:\dev\projects\halcyon\clients\files\target\test-classes\META-INF\properties\test.properties]
INFO 2008-12-01 13:28.00:453 [PropertyPlaceholderConfigurer] Loading
properties file from file
[C:\dev\projects\halcyon\client-core-stock\target\test-classes\META-INF\properties\stock-test.properties]
this should not be on classpath - this is other's module
src/test/resources
INFO 2008-12-01 13:28.00:453 [PropertyPlaceholderConfigurer] Loading
properties file from file
[C:\dev\projects\halcyon\client-core-documents\target\test-classes\META-INF\properties\documents-test.properties]
same here
The problem occurs only with client-core-stock and client-core-documents
modules OPEN as projects. Closing the projects makes the problem go away.
This problem actually happened a few times before - kept happening often
enough that test application contains now:
public class TestClient {
public static void main( String[] args ) {
if ( TestClient.class.getClassLoader().getResource(
"META-INF/properties/stock-test.properties" ) != null )
throw new RuntimeException( "m2eclipse problem again" );
Client.main( args );
}
}
I am unable to reproduce it. I have created the simplest project and it
works fine. Is there any way to deduce what is happening?
lg
--
Leszek Gawron
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
