This is not expected, but I'll need a small example project to be able to help troubleshoot the problem.
On May 29, 2014 6:31:09 PM EDT, OramahMaalhur <[email protected]> wrote: >Hello. >I'm using Eclipse Kepler Service Release 2 (Build id: 20140224-0627) >with m2e 1.4.1.20140328-1. I have maven project with configured test >resources filtering and there are several properties files in >src/test/resources with ${..} variables. The issue is, when I run JUnit > >Tests in Eclipse, resources are not filtered and variables in test >properties are not substituted with values. >As far as I understand m2e performs resource filtering when resource is > >changed, but some other builder (Java builder I guess) simply copies >resource with raw ${..} to target/test-classes/ every time autobuild is > >triggered. After I perform "Clean" manually, everything is ok but it's >not so convenient to do "clean" every time before running junit. >I have tried different order of builder and played with excluding that >properties from java build path without any luck. I've also tried to >set >up custom builder calling "mvn resources:testResources", but this leads > >to some kind of race when resource in target/test-classes is >periodically updated by different builders. >What is the way to solve this issue? > >Thanks in assistance. > > >------------------------------------------------------------------------ > >_______________________________________________ >m2e-users mailing list >[email protected] >https://dev.eclipse.org/mailman/listinfo/m2e-users -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
