The biggest deal is in updating the POMs, because the artifacts will
be changing.
If you look at the examples, you'll see that I've changed them to use
scope=import for the org.apache.isis:release artifact dependencies, as
being preferrable to inheriting from this artifact. This is on the way
to the mixin idea that I see is planned to be introduced in Maven 3.1
[1]. (NB, I see that Maven 3 has just been released [2]. Hooray!)
It might be worth a page on the wiki capturing the mechanics of what
needs to be done.
Fixing up imports is little more than Source > Reorganize Imports.
Bottom line: given the size of our community, it probably wouldn't be
worth the time and effort to build a tool. At any rate, I don't intend to.
Cheers
Dan
[1] http://jaxenter.com/maven-3-0-the-future-of-maven-10580.html
[2] http://maven.apache.org/docs/3.0/release-notes.html
On 18/10/2010 09:11, Kevin Meyer - KMZ wrote:
Hey all,
Has anyone given any thought to some kind of tool to refactor existing
pom's, dom's and properties, etc, to migrate from NOF to Apache
Isis? ;)
Regards,
Kevin
