That's the maven default, isn't it? I've mentioned that I really don't like that many directories in my source tree (I know, its my own hangup, but its just something I can't stand - call it a quirk, call it a fatal character flaw, whatever ;) ). The maven default dir tree is a burden if you like to hover in the 'project files' view (not package view) of a project. Feels overly segmented and misdirecting...
I was hoping that Maven could be told to alter its defaults. Is this not possible? On Sat, Dec 27, 2008 at 2:20 PM, Emmanuel Lecharny <[email protected]>wrote: > Les Hazlewood wrote: > >> How do you see the directories, i.e. code, resources, etc.? >>> >>> >> >> After working with wicket source trees in my own project trees, I've >> become >> keen on keeping things co-located based on pacakge. My personal >> preference >> is to have a src and a test directory directly under the module directory >> with code and resources co-located side-by-side for easy access/lookup. I >> noticed this greatly simplified my build scripts too. >> >> so, for example, we would have >> >> trunk/ >> |--build.xml >> |--pom.xml >> |--build.gradle >> |--core/ >> | |--src/ >> | |--test/ >> |--web/ >> | |--src/ >> | |--test/ >> |--support/ >> | |--spring/ >> | | |--src/ >> | | |--test/ >> | |--ehcache/ >> | | |--src/ >> | | |--test/ >> >> etc... >> >> Is this copacetic? If it is, and we were to have a maven build in >> addition >> to the regular build, could maven handle this directory structure? >> >> > Nope. But close... > > you must have something like : > > core/ > |--src > |--main > | |--java > | |--resources > |--test > |--java > |--resources > > This should not be a real burden though. > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
