Convention is convention because it's not a rule :) This also means you don't have to follow it but then it will cost you time/effort/extra configuration (you name it)...
And this is valid everywhere where 'convention over configuration' exists (it's kinda by definition)... Best regards, Siarhei Dudzin On Thu, Apr 16, 2009 at 8:42 PM, Grant Rettke <[email protected]> wrote: > On Thu, Apr 16, 2009 at 12:20 PM, Martijn Dashorst > <[email protected]> wrote: > > On Thu, Apr 9, 2009 at 7:58 AM, Arnaud HERITIER <[email protected]> > wrote: > >> 1) The Maven convention and good practice is to put ressources files > like > >> *.txt in src/main/resources. > > > > But *FORCING* this 'convention' on the world is a whole other thing. > > One of the benefits of using maven is that you can adjust it to your > > liking. Such as resources that *belong* to your java classes in the > > same physical source folder. If this is the way forward with maven, I > > assure you all Wicket projects will be switching to a build system > > that doesn't enforce such things upon us. > > I am new to Maven. From what I have read, the driving philosophy of > Maven is to adhere to convention. > > Isn't it? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
