On 07/17/2013 05:23 AM, Olivier Lamy wrote:
Due to some non backward compat changes in maven core 3.1.x, this doesn't work anymore.
Do you mean that the current plugin cannot be used to run a Maven 3.1.0+ tool? That is certainly unfortunate; I guess that means that there must be a third Maven process factory? Is there an issue filed for this?
I recently assigned JENKINS-11362 [1] to you, which is related but distinct: upgrading the bundled Maven used to parse POMs, since 3.0.5 has a grave performance bug affecting certain complex projects.
Certainly it would be great to have a refactored plugin which uses EventSpy (3.0.3+) or similar to allow bin/mvn to be run directly. This would avoid bugs like JENKINS-18178 [2] and JENKINS-18403 [3]. The latter I plan on resolving just by documenting that Jenkins (with the native Maven project type) no longer supports running Maven itself on JDK 5, and perhaps offering some automated workarounds.
[1] https://issues.jenkins-ci.org/browse/JENKINS-11362 [2] https://issues.jenkins-ci.org/browse/JENKINS-18178 [3] https://issues.jenkins-ci.org/browse/JENKINS-18403 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
