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 housekeeping: remove deprecated parameters,
use direct M3 method calls instead of by reflection.
I'm working on artifact/dependency related issues for the install, invoker
and deploy plugins.
I've created branches for these to give me enough time to fix this
correctly.
thanks,
Robert
Op Thu, 30 Apr 2015 22:29:18 +0200 schreef Kristian Rosenvold
<kristian.rosenv...@gmail.com>:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
