On Sat, 2003-07-12 at 14:43, Bill Lynch wrote: > I agree - I prefer to manage 2 separate directories and I think it's easier to > understand projects if they're structured that way. But, I do think you're right > - it'd be great if Maven could handle either approach.
Well, I don't think it would be great. Where does it stop then, you just end up with a jumble. One user wants this way, another wants that we allow N different setups for a slew of things and you just end up with a morass again. It's something that I will not let happen so long as I'm around here. > Couldn't Maven pull test cases given a dir and a patternset? I don't see why > technically it has to be in a seperate directory. Technically nothing is impossible but that's not generally why we decide to do things a particular way. I realize that in many cases some compromises are made and not every single user's desires are satisfied but that's something I can live with and I honestly thing in the long run it will better serve new users to Maven. > Regards, > --Bill > > > > > -----Original Message----- > > From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] > > Sent: 12 July 2003 17:59 > > To: Maven Users List > > Subject: Re: Keeping your test source code in a separate, but parallel > > source tree > > > > > > > > On Saturday, July 12, 2003, at 12:20 PM, Dave Ford wrote: > > > > > >>The Maven web site lists "Keeping your test source code in a separate, > >>but > >>parallel source tree" as best practices. > >> > >>Q1: Why is this a best practice? It just seems like an extra thing to > >>maintain to me, making package name refactoring for troublesome. I've > >>been > >>placing my test class next to the tested class. > >> > >>smartsoft.util.Date > >>smartsoft.util.DateTest > >> > >>By naming them this way, they appear next to each other in dir > >>listings. > > > > > > True, although I rarely ever go digging around in the directory to see > > what's there. Generally tools do a good job, such as Eclipse or Idea. > > > > The advantage I see is that you get to have test code that has > > package-level access and because it's in a separate tree, it's easy to > > build binaries that don't include all the test code... > > > > geir > > > > > >>Q2: If I want to continue my practice of keeping them together, is > >>there any > >>way to get Maven to support that? > >> > >>Thanks > >> > >> > >>Dave Ford > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
