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 into
code".
It's an interesting challenge and I've done similar things with Jelly but I
cannot 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 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:
> > > <preGoal name="test">
> > > <!-- Exclude MsAccess (ODBC) tests from Non-Windows runs -->
> > > <j:choose> <j:when
> > > test="${systemScope['os.name'].startsWith('Windows')}">
> > > <ant:echo>Including MsAccess(ODBC) Tests</ant:echo>
<ant:property
> > > name="test.extra.excludes" value="**/*MsAccess*.java"/>
> > > </j:when>
> > > <j:otherwise>
> > > <ant:echo>Excluding MsAccess(ODBC) Tests</ant:echo>
> > > <ant:property name="test.extra.excludes"
> > > value="FaKecLaSs.java"/>
> > > </j:otherwise>
> > > </j:choose>
> > > </preGoal>
> >
> > These are not ant properties. Set them for the JellyContext. Use j:set
(assuming you have bound J to jelly:core).
> >
> > - Jörg
> >
> > ---------------------------------------------------------------------
> >
> >
> > 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]
