[mojo-dev] [jira] (MOJO-1976) Artifact exclusion list for enforceBytecodeVersion

[Baptiste Mathus (JIRA)]

Baptiste Mathus commented on MOJO-1976 Artifact exclusion list for enforceBytecodeVersion FWIW, as there were a lot of changes in m-enforcer-p 1.3.x, I recently enriched the eer CI build with many combination (m3, m3, m-enforcer-p 1.0, 1.3, etc. which is btw not a breeze like matrix builds in jenkins ). I checked the failing IT, I'm not totally sure what it was running, but from what it's downloading, I suppose this is failing with m-enforcer-p 1.3.1/m221. Currently, IT run by default with 1.0. CI runs mvn verify many times, changing the parameter to test many m-enforcer-p versions. I'll have a look if I can reproduce the issue locally.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email