Maven baseline for non-plugins
Hi folks, do we have a policy for Maven dependencies for non-plugins after Karl Heinz has raised the baseline to 2.2.1? I'd like to release Maven Archiver and raise dependency versions, especially Maven to 2.2.1. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven baseline for non-plugins
Hi, In my opinion the new minimum level of Maven (2.2.1) should cover all of our projects, not just plugins. Standardizing on a single base version will also mean less artifacts to download for new Maven installations. This reminds me of something I've been meaning to do for a while now. We have a dependency plugin at my day job, that is a bit like the dependency convergence report, but it works on a much larger scale. We run it on a trunks checkout from svn, that contains an aggregator pom and externals for all our code. The plugin reports all usages of all dependencies across the entire code base, sorted in different ways. Let me see if I can set it up to run on all of Maven, at least the parts that are in svn. It should help us with our minimum Maven version updates. -- Dennis Lundberg Den 26 okt 2014 17:08 skrev Michael Osipov micha...@apache.org: Hi folks, do we have a policy for Maven dependencies for non-plugins after Karl Heinz has raised the baseline to 2.2.1? I'd like to release Maven Archiver and raise dependency versions, especially Maven to 2.2.1. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven baseline for non-plugins
Am 2014-10-26 um 17:32 schrieb Dennis Lundberg: Hi, In my opinion the new minimum level of Maven (2.2.1) should cover all of our projects, not just plugins. Standardizing on a single base version will also mean less artifacts to download for new Maven installations. This reminds me of something I've been meaning to do for a while now. We have a dependency plugin at my day job, that is a bit like the dependency convergence report, but it works on a much larger scale. We run it on a trunks checkout from svn, that contains an aggregator pom and externals for all our code. The plugin reports all usages of all dependencies across the entire code base, sorted in different ways. Let me see if I can set it up to run on all of Maven, at least the parts that are in svn. It should help us with our minimum Maven version updates. That sounds really good. A report would be helpful. I will proceed with the updates on Maven Archiver. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven baseline for non-plugins
Hi, we have already a very simple report which shows which plugins are at 2.2.1 and which not... https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html But what Dennis has suggested sounds like lightyears better kind regards Karl Heinz Marbaise On 10/26/14 5:08 PM, Michael Osipov wrote: Hi folks, do we have a policy for Maven dependencies for non-plugins after Karl Heinz has raised the baseline to 2.2.1? I'd like to release Maven Archiver and raise dependency versions, especially Maven to 2.2.1. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven baseline for non-plugins
Hi again, I've uploaded some reports for plugins and shared, which should keep people busy for a while. The reports are in text format, and should be easy to grasp. The one you want in this case is the dependency-graf.txt http://people.apache.org/~dennisl/dependency-reports/ Feedback is very welcome. On Sun, Oct 26, 2014 at 5:32 PM, Dennis Lundberg denn...@apache.org wrote: Hi, In my opinion the new minimum level of Maven (2.2.1) should cover all of our projects, not just plugins. Standardizing on a single base version will also mean less artifacts to download for new Maven installations. This reminds me of something I've been meaning to do for a while now. We have a dependency plugin at my day job, that is a bit like the dependency convergence report, but it works on a much larger scale. We run it on a trunks checkout from svn, that contains an aggregator pom and externals for all our code. The plugin reports all usages of all dependencies across the entire code base, sorted in different ways. Let me see if I can set it up to run on all of Maven, at least the parts that are in svn. It should help us with our minimum Maven version updates. -- Dennis Lundberg Den 26 okt 2014 17:08 skrev Michael Osipov micha...@apache.org: Hi folks, do we have a policy for Maven dependencies for non-plugins after Karl Heinz has raised the baseline to 2.2.1? I'd like to release Maven Archiver and raise dependency versions, especially Maven to 2.2.1. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
