Well depending on if you want to use Maven and even bind the execution to a lifecycle or not. Since you said it runs manually and required manual interaction, I keep thinking you want to prepare your environment once and then run it multiple times from the command line. But either way, there's no difference really; main point was that I'd put the manual test in a separate module.
Kalle On Fri, Jan 9, 2009 at 7:29 AM, Trevor Harmon <tre...@vocaro.com> wrote: > On Jan 7, 2009, at 5:01 PM, Kalle Korhonen wrote: > > If it's a manually run test application I'd create a separate module for >> it. >> You can set the main application as a dependency of this module, then spit >> out the required classpath with dependency:build-classpath and put the run >> parameters in your pom file, then write them out to a filtered shell or >> batch script. >> > > > Is there some advantage to building the classpath and script manually? I'd > have thought using the Exec plugin would be a lot simpler. > > > Trevor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
