You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/05/02 02:04:01 UTC
[jira] Updated: (MAVEN-1252) Variable/Properties are messed up...
The following issue has been updated:
Updater: Brett Porter (mailto:brett@codehaus.org)
Date: Sat, 1 May 2004 8:02 PM
Changes:
description changed from
I have the following snippet in a plugin...
<j:set var="destFile" value="${maven.increment.central.entities}/${pom.artifactId}.ent" />
<ant:echo>
${maven.increment.central.entities}
${destFile}
</ant:echo>
<ant:copy tofile="${destFile}"
file="${plugin.resources}/entity-template.ent"
filtering="true"
overwrite="true"
/>
The output is;
[echo]
/home/niclas/dev/opensource/avalon/framework/api/../../buildsystem/../versioning
/home/niclas/dev/opensource/avalon/framework/api/../../buildsystem/../versioning/avalon-framework-api.ent
[copy] Copying 1 file to /home/niclas/dev/opensource/avalon/framework/api/versioning
The destination filename is "avalon-framework-api.ent" but in the wrong directory.
The "maven.increment.central.entities" is read into memory in the maven.xml, by;
<util:properties file="${avalon.buildsystem}/project.properties" />
So, HOW on the earth does the <an:copy> manages to pick up the expression "${plugin-default-value}/${pom.artifactId}.ent", where plugin-default-value is the "maven.increment.central.entities" set in plugin.properties of the plugin??
My conclusion is that there are more than one set of Variables, and both are updated in the <j:set>, since manipulating the "value=" in the <j:set> will give me different printout and different destination file.
Fix Version changed to 1.0-rc3
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1252&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1252
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1252
Summary: Variable/Properties are messed up...
Type: Bug
Status: Unassigned
Priority: Critical
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
jelly/ant integration
Fix Fors:
1.0-rc3
Versions:
1.0-rc2
Assignee:
Reporter: Niclas Hedhman
Created: Sat, 1 May 2004 4:40 AM
Updated: Sat, 1 May 2004 8:02 PM
Description:
I have the following snippet in a plugin...
<j:set var="destFile" value="${maven.increment.central.entities}/${pom.artifactId}.ent" />
<ant:echo>
${maven.increment.central.entities}
${destFile}
</ant:echo>
<ant:copy tofile="${destFile}"
file="${plugin.resources}/entity-template.ent"
filtering="true"
overwrite="true"
/>
The output is;
[echo]
/home/niclas/dev/opensource/avalon/framework/api/../../buildsystem/../versioning
/home/niclas/dev/opensource/avalon/framework/api/../../buildsystem/../versioning/avalon-framework-api.ent
[copy] Copying 1 file to /home/niclas/dev/opensource/avalon/framework/api/versioning
The destination filename is "avalon-framework-api.ent" but in the wrong directory.
The "maven.increment.central.entities" is read into memory in the maven.xml, by;
<util:properties file="${avalon.buildsystem}/project.properties" />
So, HOW on the earth does the <an:copy> manages to pick up the expression "${plugin-default-value}/${pom.artifactId}.ent", where plugin-default-value is the "maven.increment.central.entities" set in plugin.properties of the plugin??
My conclusion is that there are more than one set of Variables, and both are updated in the <j:set>, since manipulating the "value=" in the <j:set> will give me different printout and different destination file.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org