Thanks for the help. What I did was to simply (re?)define it in the specific
plugin.properties file to be its defined default using
maven.test.dest=${maven.build.dir}/test-classes, and everything started working.
Woohoo...
-----Original Message-----
From: Gilles Dodinet [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 14, 2004 4:56 PM
To: Maven Users List
Subject: Re: maven jelly tag and build.properties properties
Ebersole, Steven wrote:
> actually, my bad. it does not work. it is maven.build.dest that works, not
> maven.test.dest
heres my understanding of it, i may be wrong - correct me if am :
maven.build.dest should always be available (core behavorial property),
maven.test.dest is being made available by the test plugin,
so to look it up we have to use the context of the test plugin..
however, if specified in build.properties, this late property becomes
always available. the few tests ive just made tend to confirm it (using
both ${maven.test.dest} and ${pom.getPluginContext...) and
<j:set xmlns:mytest="test" var="testDestProp"
value="${pom.getPluginContext('maven-test-plugin').getVariable('maven.test.dest')}"/>
does work just fine for me, returning the expected result.
-- gd
---------------------------------------------------------------------
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]
