Once you force a convention the convention stops being convention and becomes a rule/law. So no, in case of maven it is still a convention :)
So it's still possible to have resources along with the source code (if it happens that the convention isn't suitable for you). I beleived I had to do it a couple of times when I needed to bend maven to follow IBM RAD 6 'rules'. It didn't work the other way (suprise!) so I didn't have much choice... So, what I did was redefined resources folder to point at the java source tree and excluded *.java (and other stuff like CVS stuff). If this doesn't work you've probably hit a bug with the latest release (and looking at the original post it *is* a bug). Try a different version... I also see a few posts 'above' that a snapshot 2.7-SNAPSHOT is there so you can try it. If you don't know how to do it. Post on the mailing list, I am pretty *sure* the community will help. Good luck. Best regards, Siarhei Dudzin On Thu, Apr 16, 2009 at 7: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. > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
