It works just fine. Set sourceDirecotry = unitTestSourceDirectory, and appropriate excludes to the tests and jar plugins so they don't get used inappropriately.
Then you can tell your team not only can you do that, but by default Maven makes you follow best practices and in setting it up it has highlighted some flaws in the environment :) - Brett > -----Original Message----- > From: Chad Woolley [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 9 December 2003 2:12 PM > To: [EMAIL PROTECTED] > Subject: Re: Is it possible to keep unit tests in the same > directories as production classes? > > > Hi, > > Is there any particular reason for these vehement and draconian > objections? :) > > What are the technical issues caused by this? I can > understand how some > plugins won't work, but this could be an acceptable price. I can > understand that separate source trees is the "right" way, but does is > have to be the only way? > > In my particular case, I want to setup maven to illustrate > it's benefits > to the rest of my team. However, if I tell them I have to totally > reorganize the source tree before I can show off maven, I don't think > they are going to buy it. > > It seems like it would be to maven's benefit to be as flexible as > possible when people are migrating to it. Otherwise, people may not > even want to go to the trouble of trying it... > > Thanks, > Chad > > Jason van Zyl wrote: > > Now I'm going to have add something that halts the build if any > > derivatives of org.junit.Test* are found in the source directory > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
