Dean, On Wed, 2009-05-27 at 07:26 -0700, Dean Schulze wrote: > > If conventions are so important I wish they would stick with the most > widely use conventions. (That's why they're called conventions.) > > I haven't seen a project where Java source code is put in src/main. > It's almost always in src/, sometimes src/java. > > I'm not going to refactor existing projects just to conform to a build > system that is not even being used yet. I remember reading where the > src/main non-convention could be changed so hopefully changing the > Java plugin to recognize the real conventions won't be hard to do. > > Is Gradle one of those projects (like Maven) that punishes you if you > haven't been doing things the Gradle way, or is it easy to get Gradle > to conform to the real world? > >
You may not have seen many projects with this structure, but there are a
large number of projects that have it. Maven 1 introduced the
convention and a lot of people followed it. Maven 2 changed the
convention to something more flexible and that is now more or less a de
facto standard.
There is no reason why you should have to refactor -- even if it might
be a good idea. Maven 2 and Gradle (especially Gradle) give you the
flexibility to override the default structure should you wish to/have
to. The variables you have to set to condition the Java plugin are
listed in the documentation.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
