On Oct 15, 2010, at 7:04 AM, Esko Luontola wrote: > On Oct 15, 11:50 am, Alen Vrečko <[email protected]> wrote: >> I don't get it. Why spend all this effort in being able to build with >> Maven? Surely not because every 2 or so years a couple of jars need to >> be put in maven central? Or because you need to install ant (sudo apt- >> get install ant)? What is next? Converting Gwt to Maven? > > Guice has had a very bad track record in supporting the Maven > ecosystem. Even now there are no sources for Guice 1.0 and 2.0 at > http://repo2.maven.org/maven2/com/google/inject/guice/ and there are > lots of issues related to not making the artifacts available via a > Maven repository: > http://code.google.com/p/google-guice/issues/detail?id=59 > http://code.google.com/p/google-guice/issues/detail?id=382 > http://code.google.com/p/google-guice/issues/detail?id=420 > http://code.google.com/p/google-guice/issues/detail?id=411 > > If Guice could be built with Maven, solving all those issues would > require practically no effort - just one or two commands on the > command line.
Maven is not required to produce Maven artifacts. It is pretty simple to write an ant target to produce correct POMs, JARs, and Source JARs that fulfill Maven's requirements. Then you just need to upload those artifacts to Maven central. Pretty simple actually and you don't even have to install Maven. -bp -- 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.
