The discussion is interesting, however for something like FitNesse, we will not want to run these tests as part of a build phase. Rather, we would like to create a separate package for deployment to a FitNesse server, or some other acceptance test environment. They don't seem to fit in either main or test.
Thanks for the link, Mike -----Original Message----- From: Alexandre Poitras [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 3:45 PM To: Maven Users List Subject: Re: [M2] Best way to add a new source type This under discussion right now : http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+strategies On 4/25/06, Fisher, Michael (IT) <[EMAIL PROTECTED]> wrote: > Hello, > > What is the recommended way to add a new source type to an existing > Maven2 project? If, for example, I have a project which already has > "src/main" and "src/test", I would like to create a third type of > source code structure for acceptance tests (FitNesse, etc) and have it > be called something like "src/acceptance". I would expect a full > source structure under this folder, including config, scripts, database, etc. > > What is the best way to accomplish this within the Maven2 framework? > I don't want to get too far away from what is supported, since I > intend to upgrade as Maven matures. > > Thanks, > Mike > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
