In general,
<maven:set plugin="maven-test-plugin" property="foo" value="bar" />
>From RC3 is a better way to do this.
HOWEVER - *.src.set is an ant path, so you should use the
<maven:addPath /> to add source directories to the source path. See
the jelly tag documentation.
BUT you don't seem to be modifying the source set - instead you want
to change the tests that are run? There is an issue (MAVEN-515 I
think) raised to add this enhancement in the long run, but you
probably just want to do something like:
${pom.unitTest.includes.add('**/FooTest.java')}
(completely untested, but should work).
Cheers,
Brett
On Sun, 27 Jun 2004 18:54:35 -0700, matthew.hawthorne <[EMAIL PROTECTED]> wrote:
>
> Josip Gracin wrote:
> > How can I modify the maven.test.compile.src.set from within
> > maven.xml? What I need to do is the following:
> > when there is some property set, additional unit tests should
> > be included, otherwise, everything should be run
> > without those tests.
> >
> > I tryed modifying maven.test.compile.src.set, but I couldn't
> > get it to work. Was that the right way to do it?
>
>
> You may have to do something like this:
>
> {pom.getPluginContext('maven-test-plugin').setVariable('maven.test.compile.src.set',
> 'yourDirectory')}
>
> I've done it a few times but I don't have the files anymore. You may
> need to debug by outputting the property values in preGoals or postGoals
> to test:compile, or something like that.
>
>
>
> ---------------------------------------------------------------------
> 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]
