commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From commons-...@jakarta.apache.org
Subject [jira] Closed: (JELLY-105) Nested element's setName() called with name of tag
Date Wed, 01 Sep 2004 17:52:50 GMT
Message:

   The following issue has been closed.

   Resolver: dion gillard
       Date: Wed, 1 Sep 2004 10:51 AM

Changed AntTag and commented out name property set
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JELLY-105

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: JELLY-105
    Summary: Nested element's setName() called with name of tag
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: jelly
 Components: 
             taglib.ant
   Fix Fors:
             1.0-beta-4

   Assignee: 
   Reporter: Vincent Partington

    Created: Fri, 30 Jan 2004 2:01 AM
    Updated: Wed, 1 Sep 2004 10:51 AM

Description:
I have written an Ant task that can configure a JMeter task for a specific environment. It
is invoked like this from an ant build.xml file:

  <configurejmeter
    basedir="${basedir}/tests"
    destdir="${current.build.dir}"
    includes="*.jmx"
  >
    <property file="${environment.properties}" />
    <property name="nr_threads" value="${test.nr.threads}" />
    <property name="nr_iterations" value="${test.nr.iterations}" />
  </configurejmeter>

The <property file="..."/> element specifies a file containing properties to be inserted
into the JMeter task, while the <property name=".." value="..."/> tags specify specific
properties.

However, when I put this fragment in a maven.xml file, it doesn't work. It seems the setName()
of all the objects created for the nested <property> elements is invoked with the value
"property". The first <property> element won't work because of that because it doesn't
expect setName() to be invoked when setFile() is invoked too.

I've isolated the problem to line 261 in org.apache.commons.jelly.tags.ant.AntTag:
http://jakarta.apache.org/commons/jelly/libs/ant/xref/org/apache/commons/jelly/tags/ant/AntTag.html#260

Why is that line of code there? It seems strange to me, also because the exception is masked.
When I commented out those lines, the problem disappeared.

BTW, I am using Maven 1.0rc1, which includes commons-jelly-tags-ant-20030625.032346.jar.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message