[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50256 ]
John Casey commented on MNG-1356:
---------------------------------
Alternately, if your plugin is downloading the containers, can't you simply use
a plugin configuration that specifies ${java.io.tmp.dir} as the value? IIRC,
the parameter expression evaluator should look it up from the sysprops. If not,
that's a problem...
My tendency would be to say that you'd be introducing a bad source of
variability to your POM if you could do:
<project>
...
<version>${user.home}</version>
...
</project>
> Java system properties should be interpolated in pom.xml
> --------------------------------------------------------
>
> Key: MNG-1356
> URL: http://jira.codehaus.org/browse/MNG-1356
> Project: Maven 2
> Type: Improvement
> Components: maven-core
> Versions: 2.0
> Reporter: Vincent Massol
> Fix For: 2.0.1
>
>
> Here's a use case where I'd need ${java.io.tmp.dir} interpolated in my
> pom.xml:
> Some plugins output things. Some of those things can be transient and putting
> them in ${basedir]/target is fine. However there are other cases where you
> want to be sure that what is generated stays even after a clean. This is the
> case for the cargo plugin which can automatically download containers. It
> wouldn't be nice that the downloaded containers be wiped out on a clean. I'd
> like to leave it to the user to decide where to put them and one location
> that would be fine is ${java.io.tmp.dir} (this is the one I want to use in
> the cargo plugin's functional tests).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
