Re: [m2e-dev] Is m2e ignoring output location set in Eclipse?

[Raphael Ackermann <raphael.ackermann@xxxxxxxxx>]

wan't on the list before so cannot properly reply.

This is not an m2e-android issue but looks to be a problem in m2e itself.

Steps to reproduce:

Have a maven project in Eclipse. 

Build it on the command line with mvn test. Tests pass

Run the tests in Eclipse. Tests pass.

Change production code in Ecilpse that would make the tests fail.

Run the tests in Eclipse. Tests still pass even though they should not

Clean the project in Eclipse without rebuilding it. 

Run the tests in Eclipse. Tests still get executed and pass even tough the project is not built.

Run the tests on the commandline. --> tests fail.

See comments and log output at 

https://github.com/rgladwell/m2e-android/issues/221#issuecomment-68313050

By default m2e indeed uses MavenProject to determine project classes and
test-classes directories. There is classifierClasspathProviders
extension point that should allow you to use alternative locations.

--
Regards,
Igor