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? -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.
