On 15 October 2010 22:56, Brian Pontarelli <[email protected]> wrote:
> On Oct 15, 2010, at 10:35 AM, Stuart McCulloch wrote: > > On 15 October 2010 16:26, Brian Pontarelli <[email protected]> wrote: > >> >> On Oct 15, 2010, at 9:21 AM, Andrei Pozolotin wrote: >> >> > Alen, hello: >> > >> > On Oct 15, 3: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 >> > >> > maven helps to have all guice jars with all extensions and all latest >> > fixes >> > availaby weekly, instead of every 2 years, >> > >> > maven also helps with not having to mess with your own jars >> > which are not shared and which nobody can relate to; >> > >> > maven helps you to ask a question: "such and such is not working in >> > guice-3.0.1-SNAPSHOT" and receive an answer "I had the same; now it >> > works for me in guice-3.0.3-SNAPSHOT", then make 1 line change in your >> > pom and you up and running; >> >> It's pretty simple to add an Ant target that will produce the POM, JARs >> and source JARs and put them into your local Maven2 cache. That would fix >> this issue as well. Again, no reason to switch Guice to Maven really. All >> the Maven stuff is merely metadata about the project that can be generated >> by anything since it is just XML. Similarly, the Ant target could produce >> Ivy and Savant metadata and publish that information to those local caches >> as well. Why not cover all the dependency management tools at once? >> > > adding a maven build alongside the ant build has other benefits - it helps > people who want to build with maven, or have IDEs that integrate better with > maven > > > Not really. If there are targets to produce Maven artifacts and publish > them locally or remotely then Guice can be easily integrated with Maven. > I was speaking more of people who want to build Guice itself with Maven, and not just consume the occasional artifact pushed to Maven central this is useful both for Maven-based developers who want to contribute back to Guice and also for people debugging problems inside Guice itself IDEs Maven support is generally for Maven central and local repositories. It > doesn't compile local projects unless they are sub-projects. I have to say > again that you can integrate with your Maven project without changing > Guice's build to Maven. If the maintainers don't want to use Maven, it is > simple for them to provide integration hooks without major changes to their > build or directory layout. Maven integration merely requires JARs and an XML > file. > sorry to be blunt, but I'll believe it when I see it - as others have mentioned there are issues that have been open for a long time asking for the extensions, sources, and javadoc, etc. to be uploaded to Maven central. Not to mention regular snapshots that people could try to verify fixes before the next release. so if someone has a patch to add such distribution targets (or the time to write one) please submit it, then at least people have a way to do it themselves anyway as Jason said here are the POMs (and updated build structure) if you want them, but if you don't then no problem - we'll carry on sync'ing trunk with http://github.com/sonatype/sisu-guice as a convenience for Maven developers -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]<google-guice%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-guice?hl=en. > -- Cheers, Stuart -- 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.
