<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>There are no, up front known issues with maven 3.5,<br><br></div>there are few issues they fixed that will come on handy for us.<br><br></div>But moving WildFly build to require 3.5, is bit to early to say.<br></div>It at least needs some ground testing before we move to that.<br><br></div>As about your two questions.<br><br></div>1) maven resolver is just re-branded name aether project with some extra fixes on top of it.<br></div>project has moved back to maven umbrella from eclipse one which is a good thing as fixes can be more rapid.<br><br></div>2) we don't use ejb3 packaging, quickstarts use maven-ejb-plugin but that is still there and fine.<br><br><br></div>My suggestion would be that developers on the team move to maven 3.5 as soon as convenient,<br></div>and if no major problems are found after a while of usage we can start discussing about requiring it.<br><br></div>In similar fashion we can start testing / moving to 3.5 on CI as well.<br><div><div><br>--<br></div><div>tomaz<br></div><div><br> <br><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 10, 2017 at 10:50 AM, Peter Palaga <span dir="ltr"><<a href="mailto:ppalaga@redhat.com" target="_blank">ppalaga@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi *,<br>
<br>
as you may have noticed, Maven 3.5.0 has been released recently.<br>
<br>
While having a colored console output is nice `mvn clean install<br>
-DskipTests` works, are there any issues/reasons known already why Maven<br>
3.5.0 should not be used for building WildFly & Co.?<br>
<br>
Going through the relnotes [1] I found two potential sources of issues:<br>
<br>
(1) Replaced Eclipse Aether with Maven Resolver - this will perhaps<br>
change the resolution in some cases.<br>
<br>
(2) Removed the artifact handler for ejb3 - do we use ejb3 packaging in<br>
our code at all?<br>
<br>
[1] <a href="https://maven.apache.org/docs/3.5.0/release-notes.html" rel="noreferrer" target="_blank">https://maven.apache.org/docs/<wbr>3.5.0/release-notes.html</a><br>
<br>
Thanks,<br>
<br>
Peter<br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>