I am about to start a new project and in prep have been coding up a few little test projects in order to evaluate Maven2
on the whole I am confident enough re Maven2 to push for it for my new project, but have resigned myself to writing a few plugins to make up for various missing bits
also there are a few bugs with the javadoc plugin (on mac osx) and others that could impact your project. but depending on the size of your project you may still be in the use-cae and functional req gathering stage still when m2 goes final. That is certainly my hope.
Kind regards,
Dave Sag
"Gregory Gerard" <[EMAIL PROTECTED]> wrote on 11/10/2005 05:20:25 AM:
> Hi,
>
> I'm planning to break out a rather large project already in Ant into
> modules. I believe Maven to be the right tool. I have a few reservations but
> maintaining Ant is just from hell.
>
> If you were to start a new project today (or refactor an existing build),
> which version of Maven would you choose? 1.1B* or Maven2 whatever-is-latest?
>
> Ideally, I'd like to have all my projects in Eclipse and have them all
> interlinked correctly (the JAR from one eclipse project is available to the
> next; Maven would just scribble out all the inter-project dependencies
> whenever I ask it to) so debugging works seamlessly.
>
> Speaking of Eclipse, Mevenide would be handy but seems kinda zombie.
>
> Thanks for tips and clues!
> greg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
