Thank everyone for the suggestions, they are all great ideas.
Thanks,
Corey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> -Original Message-
> From: Corey Scott [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 03, 2004 8:25 AM
> To: Maven Dev List
> Subject: Problem dynamically excluding some tests
>
>
> Currently I am trying to exclude a certain set of tests from running
> on different machines based
From: Florin Vancea [mailto:[EMAIL PROTECTED]
Sent: Friday, December 03, 2004 11:27 AM
To: Maven Developers List; Corey Scott
Subject: Re: Problem dynamically excluding some tests
On second thought; just an idea.
Maybe you can fiddle with the POM var available in Jelly. After all there
are lots of thing
Maven Developers List; Corey Scott
> Subject: Re: Problem dynamically excluding some tests
>
>
> On second thought; just an idea.
> Maybe you can fiddle with the POM var available in Jelly. After all there
> are lots of things possible there, as it's described "turning XML
test it now and provide a final solution.
- Original Message -
From: "Corey Scott" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, December 03, 2004 12:06 PM
Subject: Re: Problem dynamically excluding some tests
> That didnt
That didnt work either, I think I will just stick with the build.props.
Thanks away,
-CS
On Fri, 3 Dec 2004 10:55:15 +0100, Jörg Schaible
<[EMAIL PROTECTED]> wrote:
> Corey Scott wrote on Friday, December 03, 2004 8:25 AM:
> [snip]
>
>
> > Extract from my maven.xml:
> >
> >
> > >
Corey Scott wrote on Friday, December 03, 2004 8:25 AM:
[snip]
> Extract from my maven.xml:
>
>
> test="${systemScope['os.name'].startsWith('Windows')}">
> Including MsAccess(ODBC) Tests name="test.extra.excludes" value="**/*MsAccess*.java"/>
>
>
> Excl
Yeah, that is what I had expected.
I was trying not to use build.props to make it auto-detect but it
looks like I will have to.
Thanks,
Corey
On Fri, 3 Dec 2004 09:38:18 +0200, Florin Vancea <[EMAIL PROTECTED]> wrote:
> I'm no expert but I believe project.xml is already parsed when you get to
>
I'm no expert but I believe project.xml is already parsed when you get to
maven.xml. Therefore it's useless to change that property within maven.xml.
Maybe you can use build.properties to specify test.extra.excludes and
configure different build.properties on different machines.
Florin
- Orig
