Hello everyone, recent issues encountered and our general historical use of everything latest-and-greatest, we need to discuss timing of making maven-3.5 required for building OpenDaylight.
We currently support and verify maven-3.3.9, which is used for all of our jobs except those running on odlparent master, which hosts odlparent-4.0.0-SNAPSHOT. The reason odlparent-4.0.0 is going to require maven 3.5.0 is SpotBugs, which does not work with maven-3.3.9 -- that dependency needed to be updated to move us from a release candidate to a proper release (and to the next bugfix release). maven-3.5 is being shipped in Fedora 27 and will ship in Ubuntu 18.04 LTS. I have not done any research beyond that, but as Michael recently noted, managing these sorts of dependencies can be done via http://sdkman.io/ or similar (although their HTTPS site does not work, which is worrysome). From yang-maven-plugin perspective, the newer the maven the better and the aether stack has been a world of pain 3.5.x will bring us closer to ending. With that, the question is: should we start to require[1] maven 3.5.0[2] at the beginning of the next development cycle? Thanks, Robert [1] This means running all Jenkins jobs with mvn35 and having maven enforcer plugin fail build with anything below 3.5.0 [2] Version 3.5.0, not 3.5.2 because Fedora 27's maven-3.5.0-6.fc27.noarch does not seem to be affected by the issues we've seen and with vanilla 3.5.0, so excluding it would be unfair.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
