Therein lies my #1 gripe about adopting Maven. The second you might want to do something that is not the Maven Way, you end up backed in a corner. I can't, in good conscience, ever vote in favor of a build system that doesn't offer flexibility should it be needed or desired. I would rather see a build system that builds by convention but allows overrides where you want it.
I personally don't care what the casual builder of our framework wants to use or how they want things laid-out - they don't live in the source code on a regular basis. I care about what the development team prefers. If others on the dev team vote for a directory structure that matches the Maven Way, then I will accept it. I however will not vote that way. But, I just did some googling: http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html "Please try to conform to this structure as much as possible; however, if you can't these settings can be overridden via the project descriptor." So, it appears that they are 'overridable'... On Sat, Dec 27, 2008 at 3:13 PM, Emmanuel Lecharny <[email protected]>wrote: > Les Hazlewood wrote: > > Nope... It's not the 'maven' way :) > > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
