The only issue here is it breaking builds. But if it's a major version change
then probably not a big deal. But being consistent for consistency's sake is
generally not all that useful for users.
On May 1, 2015, at 5:02 PM, Dennis Lundberg wrote:
> Not really deps related, but we should make s
You may also want to note as part of making plugins for Maven 3.x is that we
should encourage people _not_ to inject SLF4J loggers. I'll send out another
thread, but I'd like to update to the non-fork Guice 4.0 but there might be a
couple instances of using injected SLF4J loggers in places. I ho
I've started this page based on my first experiences and things mentioned
in this mailthread:
https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies
Op Fri, 01 May 2015 23:02:39 +0200 schreef Dennis Lundberg
:
Not really deps related, but we should make
Not really deps related, but we should make sure that we use the
correct package names when upgrading plugins to require Maven 3. Many
plugins use org.apache.maven.plugin as the package name, but it should
be org.apache.maven.plugins (with an s at the end) to match our
groupId.
On Thu, Apr 30, 201
Not that I'm aware of, but I can think of several steps:
- compile/runtime should not depend on maven-compat (the
plugin-testing-harness still requires it, so test-scope is still required,
though)
- consider testing with a Maven distribution without maven-compat
- use the major release to do
Do we have any wiki page describing the migration steps that would be
recommended to move a plugin from 2.2.1 deps to 3.x deps ?
I'm thinking *both* in terms of avoiding deprecations and "other" troubles
that may arise ?
Kristian
