On Sun, Oct 18, 2009 at 10:39 AM, Antonio Petrelli <[email protected]> wrote: > 2009/10/15 Antonio Petrelli <[email protected]>: >>>>>> There is only *one* test that I am not able to execute, since it needs a >>>>>> container, i.e. it is an integration test and it needs, essentially, a >>>>>> web >>>>>> project (correct me if I am wrong). >>>>>> Is it the case to exclude the Maven path for merely a single >>>>>> *integration* >>>>>> test? >>>>> >>>>> well, it wasn't/isn't a mere integration test. it was (is?) the key >>>>> test for the VelocityView tools, as nothing else tested those. >>>> >>>> Ok a functional test then. It still needs a container. >>> >>> is there a way to do that with Maven? or could we just have Maven >>> drive the Ant task for it? >> >> Maven, with the Cargo plugin, can do it, but there is the need for a >> separate module containing the web application. > > I noticed that, in fact, the ViewToolsTests class tests Velocity Tools > using the showcase webapp, so it's testing the Showcase functionality. > This test, then, can be moved into the showcase, when even these > examples are mavenized.
Yeah, that would make sense. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
