On Fri, Oct 15, 2010 at 4:50 PM, 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? > I suppose you'll know the Guice devs have no intention to migrate from Ant to Maven if you have read this thread. The maven build is mainly to make it easy to deploy Guice to the Maven repository but not a replacement of the existing Ant build. > ... > > How about just putting guice/src and guice/test into guice/core/src > and guice/core/test? This should make Maven happy but still getting > rid of /java and /main/resources? > > So, it is : core/src/main/java, core/src/test/java vs core/src/, core/test/ Honestly, I use Maven's structure for my own projects but it is the Guice developers who work on the Guice codebase day-to-day. They seem to like a simple structure and they definitely should make the decision, and the core/src structure does work for Maven. Just took a quick glance, the core project doesn't even have a property file. All code src are .java and this project doesn't benefit from the Maven structure as much as those that use different kind of src or test files. The only file i would put under /resources is the /META-INF/persistence.xml under guice-persist/test. > Imho Maven is overrated. > I suppose you refer to Maven's project structure but not its distribution channel. And I still disagree with you. Guice is too simple to be benefit from Maven's structure. for a project with different packaging (e.g. some core lib and some web app/war), complex inter-module(sub-project) dependencies (guice's sub-project are all independent extension), using different languages and resource type, Maven's structure helps a lot. Making an open source project that doesn't support Maven and require people to download the jar and add their projects is just like distributing a packaged software as in physical CDs selling in stores without any Internet download. With maven support (i.e. distribute the jar/src/javadoc in the central maven repository, not necessary structure the project in Maven's style), people can try the project by copy-and-paste a few lines of configuration and Maven take care of getting the jar and all the dependencies to put into the project. It is much easier to try and upgrade a library. regards, mingfai > > Cheers > Alen > > -- > 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. > > -- 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.
