Hello guys,
Recent test plugin (1.8) changed to not depend on java:compile if
maven.test.skip = true or no test are present.
This introduced MPWAR-62, that is now solved.
AFAIK this also introduce a bug in jar plugin that will compile two
times the java sources
This also creates a bug when using other plugins, like the "javaapp"
plugin (from [EMAIL PROTECTED]), that uses the test:test goal to
ensure classes compilation.
I agree the test plugin should not be used by other plugin to compile
application sources, but this seems to be a commonly used bad-practice,
that will break builds on several projects.
Maybe this would be better to make the test plugin depend on
java:compile in any case, or perhaps make this optional, or any better
solution that would avoid breaking existing.
Thanks
Nico.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
