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" <[email protected]>: > 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: [email protected] > For additional commands, e-mail: [email protected] > >
