From kevinb9n on February 26, 2007 19:03:55

is there really any significant pain this would address?  to me, working with this
project is a breeze!  should this be 'low' priority?

From crazyboblee on February 26, 2007 20:03:09

I filed this before I configured all the Ant builds which I did after I decided Maven
was too much of a pain. Maven would have been nice because it's higher level while
the Ant config is hacked together in an ad hoc manner. Maven can generate your IDE
config so you don't have to maintain module deps in two different places.

Status: WontFix

From arikkfir on April 03, 2007 16:30:30

Perhaps guice-devs could reconsider please? The added value is not only to
developers, but also to users that like building Guice from svn - and running "mvn
install" is as easy as it gets.

Of course, running "ant dist" is just as easy - but the added value comes when one
wants to integrate Guice into a mavenized project; one just adds a "<dependency>" in
his/her project referencing the (newly-built) Guice and violla...

It doesn't have to replace your existing Ant build. And IMO it would please both worlds.

just my 2 cents ;-)

From crazyboblee on April 03, 2007 16:43:07

I actually tried to do this. We want you to be able to check out, run a script, and
build successfully. The problem I ran into with Maven was that I needed newer
versions of some dependencies which weren't in any Maven repos.

From arikkfir on April 03, 2007 18:19:59

Ahh ;-)  Well this can easily be taken care of. Which ones are missing?

From dhanji on April 03, 2007 18:22:02

"We want you to be able to check out, run a script, and
build successfully."

@boblee

Curious why this doesnt work with ant? Couldnt the deps be checked into the repo as well?

From arikkfir on April 03, 2007 18:25:28

Yes, they can, with an extra step (running "mvn install:install-file ..."). If you do
this once/twice, its a non-issue...

But having to do this after each build is too much redundancy... There's nothing in
this issue that prevents mavenized projects to use guice. The issue is only to make
mavenized people less headaches ;-)

From brianpontarellidocs on April 04, 2007 08:33:52

You could also integrate with Savant or Ivy to handle dependencies and publish out
JAR files and still maintain ant builds. If you are only switching to maven for
dependency management, there are many other solutions out there.

From hani@formicary.net on April 04, 2007 08:35:40

Please close this issue, maven is not needed nor should there be a switch to it (maven artifacts is a separate
issye)

From gk5885 on April 04, 2007 09:12:26

I'll agree with Hani that if you're thinking of switching to maven to do the exact
same thing as you're doing with ant, it makes more sense to keep doing it with ant.
However, if you're looking at some of the other features like reporting, release
management, etc. then it's a good tool to consider.

From crazyboblee on April 04, 2007 09:21:00

The only reason I'd consider switching to Maven is its ability to generate IDE
configurations.

From brianpontarellidocs on April 04, 2007 09:45:57

I have a wicked good Ant plugin for that if you want to check it out. Works pretty
well for web and lib projects for IntelliJ. It needs some work for Eclipse though.
Right now it is tweaked for Savant usage, but changing that would be simple. Plus, it
uses the Groovy plugin because it requires a bit of heavy lifting with respect to
String parsing and XML creation.