Hi Mike,
woproject/maven2
Command line tools for Maven 2. Can be used to import WO libraries into
local repository, to build WO frameworks and applications using the
Maven way and to create basic project structure for WO projects (Maven
standard layout + WOLips configuration files).
woproject/mavenplugins
Command line tools for Maven 1. I don't know much about these plug-ins.
I also don't know if there is someone using Maven 1 to manage WO projects.
woproject/wolips/maven (The one that appears on Eclipse Software Updates)
Eclipse plug-in to help developing WO projects using Maven 1. Same
comments from the previous item. We could ask on WebObjects list if
anyone uses Maven 1 to manage WO projects. We can hide this option if
nobody is using it.
woproject/wolips/apple (The other one that appears on Eclipse Software
Updates)
Eclipse plug-in that provide wizards to create WO projects using the
Maven standard layout. It was created to make WO developers life easier
when using the nightly builds. The Maven configuration provided by this
plug-in is more verbose than the configuration from the first tool
(woproject/maven2). But it is more flexible too. It also provides some
tools to configure Maven settings (WO version e etc).
I've talked with Daryl Lee and Lachlan Deck to synchronize efforts for
the next steps to avoid overlapping and waste of time. I think we could
write the plan on WOProject Wiki, so other people can help us.
Cheers,
Henrique
Mike Schrag wrote:
> So what exactly is the state of the union on maven plugins? Is there
> overlap between the apple maven plugins and the original plugins? If
> so, I'd like to resolve and kill the lesser of the duped code ... I
> don't use it at this point, but I also don't want people to be confused
> who do.
>
> ms
>
>
This archive was generated by hypermail 2.0.0 : Sat Sep 06 2008 - 11:23:39 EDT