I don't understand this at all. If anyone as a Java developer wants a new version of Maven in the tree, you just have to create a branch, unpack the new version into the directory, push the changes, wait for Bamboo to go green, then make a PR. We're not going to stop anyone from upgrading Maven if it works properly.
The reason that a known version is included in the tree is that in the past, Maven has had significant dependency resolution behavior changes (even across micro versions iirc) that caused build breakages with OpenNMS because of the complexity of our build. For this reason, we added the large dependencyManagement section to the top-level POM and created the dependencies/ POMs so that we would reliably pull in the correct version of all dependencies. I don't want to waste our time debugging Maven problems for all developers when a known version works perfectly for 95% of them. If the main issue here is that "Maven is always out-of-date" then there is an easy solution: upgrade it! Pull requests welcome. -- Seth On 3/22/16 7:20 AM, Ronny Trommer wrote: > Otherwise > we tend to run ancient Maven versions cause nobody really knows and just > adds barriers for Java developers. We should have the project in a shape > where it should always run with latest Maven otherwise we doing > something wrong.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
