[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50664 ]
Edwin Punzalan commented on MNG-1356:
-
This is already implemented and should be closed. All values in
System.getProperties() can be interpolated into pom.xml.
btw, its java.io.tmpdir not java.io.tmp.dir. Maybe that's the reason why
you can't get it interpolated?
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]
[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50680 ]
Vincent Massol commented on MNG-1356:
-
Hi Edwin,
I have correctly used java.io.tmp.dir (as shown above in the config). I have
just tried again and once more I got a null.
Do you have an IT test for this that I could look at?
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
Assignee: Edwin Punzalan
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]
[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50729 ]
Edwin Punzalan commented on MNG-1356:
-
This pom is what I used to try it:
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIda/artifactId
version1.0/version
packagingjar/packaging
namea test/name
dependencies
dependency
groupIdtest/groupId
artifactIdtest/artifactId
version1.0-${java.io.tmpdir}/version
/dependency
/dependencies
/project
Also, I tried using: System.getProperties().list(System.out) and found only
java.io.tmpdir, no java.io.tmp.dir. Maybe its something jdk specific. I'm
using 1.4.2_07
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
Assignee: Edwin Punzalan
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]
[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50255 ]
John Casey commented on MNG-1356:
-
are these containers artifacts that could be resolved as part of a
plugin-dependency? That is to say, could you do:
build
plugins
plugin
groupId/
artifactIdcargo-maven-plugin/artifactId
dependencies
dependency
groupId/
artifactIdtomcat/artifactId
version5.0/version
/dependency
/dependencies
/plugin
/plugins
/build
Or are you downloading the stock binaries for these containers?
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]
[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ 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]
[jira] Commented: (MNG-1356) Java system properties should be interpolated in pom.xml
[ http://jira.codehaus.org/browse/MNG-1356?page=comments#action_50276 ]
Vincent Massol commented on MNG-1356:
-
Hi John,
Yes, it's Cargo which is downloading the container distribution.
Using a plugin configuration is exactly what I'm after but it wasn't working
when I tried it. Here's an example of the POM I would like to have:
plugins
plugin
groupIdorg.codehaus.cargo.maven2/groupId
artifactIdcargo-maven2-plugin/artifactId
configuration
waittrue/wait
container
containerId${containerId}/containerId
log${basedir}/target/${containerId}/cargo.log/log
zipUrlInstaller
url${downloadUrl}/url
installDir${java.io.tmp.dir}/cargo/installDir
/zipUrlInstaller
/container
configuration
dir${basedir}/target/${containerId}/container/dir
properties
property
namecargo.servlet.port/name
value${port}/value
/property
property
namecargo.logging/name
valuehigh/value
/property
/properties
/configuration
/configuration
/plugin
/plugins
[...]
Thanks
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]
