Yes, you'd need to include the defaults you need. <excludes> <exclude>**/LongTest.*</exclude> </excludes>
On 11/4/05, Dave Neuer <[EMAIL PROTECTED]> wrote: > So, what is the syntax for <excludes></excludes>? Am I correct that this > goes in a <plugin>..<configuration></configuration> section? And am I > also correct that I will need to include the defaults (i.e., exclude > "Abstract*"? > > I'm finding the documentation not quite clear on this. > > Dave > > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 02, 2005 8:18 PM > To: Maven Users List > Subject: Re: [m2] Problem: How to run some tests only sometimes > > Dave is right that profiles are the right way to go about this. > > You can change the includes/excludes of the test plugin (or even skip > them all for a project) based on the profile in use. > > - Brett > > On 11/3/05, Brill Pappin <[EMAIL PROTECTED]> wrote: > > I used to do this with a special goal in the maven.xml but since it no > > longer graces m2, I would love to hear a solution as well. > > > > - Brill Pappin > > > > On 11/2/05, Dave Neuer <[EMAIL PROTECTED]> wrote: > > > > > > So, here's my situation, I really hope someone can help figure out > how > > > to do this. > > > > > > I have currently got 2 projects, one's a library, the other is more > like > > > an application, and depends on the library. The lib project tests > only > > > use Mocks, because they're "common" objects not tied to a product or > > > database instance. > > > > > > The "app" project depends on both the lib jar and the lib-test jar > (in > > > order to reuse abstract test logic. This has been working great > since > > > the test-jar feature was added in beta 3. > > > > > > Now, unfortunately, some of our tests in the "app" take a > LOOOOONNNNG > > > time to run (i.e., tests that insert hundreds of thousands of rows > into > > > the DB). > > > > > > We really don't want to be in a situation where the tests take so > long > > > to run that developers don't run them, thereby checking in buggy > code. > > > So, the idea was we'd separate out the horrendously long ones and > run > > > them nightly or something. > > > > > > Problem is, I can't figure out a good way to do this. "Lib" and > "app" > > > are both modules in a top level project, normally we do "mvn > install" > > > from the top-level directory to run all of the tests. > > > > > > So, if I add another project "long tests" as a module, the long > tests > > > will be run each time by the developers. If I don't add it as a > module > > > in the top-level project, running it in its own directory requires > that > > > the other modules' jars are installed -- which is fine except that > once > > > that is done once, it won't automatically be done again, and so > changes > > > in the other projects won't be picked up. > > > > > > So is there a way, either with profiles w/ a different test name > > > pattern, or declaring the top-level pom as a parent in the "long > running > > > test" project, to ensure that the other projects are built fresh > when > > > the long tests are run? > > > > > > Thanks in advance. > > > > > > Dave > > > > > > > --------------------------------------------------------------------- > > > 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] > > > --------------------------------------------------------------------- > 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]
