Sorry, I meant configuring the generated suite with exclude/ includeTestFiles in the pom.
We had legacy test runners which built their own suites (one for unit tests, one for integration tests against our Jetty server) programmatically that we ran prior to porting our Flex build process over to maven, I was hoping to leverage these; however, we are refactoring to move all of our integration tests (AS and Java) to a separate module (so that we can run them from the same VM as the server), so I can now allow flexmojos to work its magic, using the default suite generation to compile and run all of our *Test (and of course *ITest) classes in the separate modules. Thanks again for the quick responses. cholm On Jun 30, 1:38 pm, Marvin Froeder <[email protected]> wrote: > On Tue, Jun 30, 2009 at 4:35 PM, cholm <[email protected]> wrote: > > although my hunch now is that explicit configuration in > > the pom will continue to be most efficient). > > Configuration of what? The template? You must declare on pom, take a look > on the sample and you will see. > > Or you mean that the socket configuration should be in the pom? > > VELO --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos?hl=en?hl=en http://blog.flex-mojos.info/ -~----------~----~----~----~------~----~------~--~---
