You could use maven to kick off the ant build using the antrun plugin, that way you wouldn't have to maintain two separate builds, but you could still use maven plugins (like the eclipse and idea plugins).
The ide plugins alone make a maven project attractive to work on. I can use my ide of choice, and know that mvn eclipse:eclipse will get me up and running without any custom ide configuration. On Sat, Apr 3, 2010 at 3:35 AM, Max Bowsher <[email protected]> wrote: > For the Guice 1.0 and 2.0 releases, Maven pom.xml files were crafted on > a branch after the release, and left on the branch. > > I would like to suggest that the pom.xml files from the 2.0-maven branch > be copied into trunk (replacing <version>2.0</version> with > <version>2.1-SNAPSHOT</version>). > > This would make it more practical to keep them up to date with ongoing > development, and have them ready to go immediately after a release. > > > > As a possible extension, I'd love it if I could use 'mvn > eclipse:eclipse' to trivially build myself Eclipse project files for > Guice. Would adding some things to the POMs to allow this be OK? It > would be bits which are omitted right now because the POMs are for > deployment only. > > > As a possible further extension, how would people feel about making the > POMs capable of building the project? I'd like to build Guice snapshots > and put them into my corporate maven repository, and having Maven > capable of orchestrating the entire build/deploy in one command would be > a big win. This need not replace the existing ant buildsystem, but could > be an option alongside it. > > > > Thanks, > Max. > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
