On Sat, Oct 9, 2010 at 10:59 AM, Brandon Atkinson <
[email protected]> wrote:
> Yes, maven can handle different layouts, but what's so great about the
> guice style that warrants deviation?
>
> The standard maven layout is used in many projects, which allows many
> developers to dig into the code without learning the layout and build for
> each and every new project out there. This means less impedance mismatch
> for patch submitters.
>
> The consistency that comes from conforming to the convention can be a big
> benefit. Sure, the current layout seems better because it is familiar now,
> but if you were to become familiar with the maven layout, you'd be
> comfortable on hundreds of projects, instantaneously.
>
>
+1.
for sure Maven in theory "should" be able to handle different structure and
Guice's developers could have their own preference, the maven's structure
does have some advantages. Let's compare:
src/...
test/...
with:
core/src/main/java/...
core/src/test/java/...
I'm a Maven user and think /core/src is more symmetrical, but this is just
personal preference.
Disregard the first level ("/core"), the maven structure caters different
type of source, e.g.
src/test/resources/guice.xml // Guice in the xml hell! ;-)
src/main/protobuf/guice.proto
extensions/servlet-example/src/main/webapp/index.jsp //new example maven
module that build as a .war
The maven structure is flexible and a lot of developers are familiar with
it.
Regards,
mingfai
--
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.
