You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by bu...@apache.org on 2003/08/01 12:28:08 UTC

DO NOT REPLY [Bug 22044] New: - style-task and undefined parameters

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22044>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22044

style-task and undefined parameters

           Summary: style-task and undefined parameters
           Product: Ant
           Version: 1.5.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: ja@tim.se


Look at the following example and think about
what would happend if $myparam is undefined
in build.xml:

build.xml:

<style ... style="template.xsl">
  <param name="myparam" expression="$myparam"/>
</style>

template.xsl:

...
<xsl:param name="myparam">MyParamDefaultValue</xsl:param>
...

The value of myparam in the stylesheet would be "${myparam}" (litterally),
not "MyParamDefaultValue" as expected. I think the style-task needs
to remove undefined param values, or at least set them to "".

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org