ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 52993] New: xmlproperty not working as advertised
Date Tue, 27 Mar 2012 22:48:18 GMT

             Bug #: 52993
           Summary: xmlproperty not working as advertised
           Product: Ant
           Version: 1.8.2
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
    Classification: Unclassified

Not sure if this is an issue with me understanding the documentation or it not

I'm trying to load xml properties from Jira for the sake of configuring an ant
build. When I view the xml that I'm having problems with from Jira it looks

    <issuelinktype id="10000">
        <outwardlinks description="depends upon">
                <issuekey id="14214">BUILD-460</issuekey>
                <issuekey id="14182">BUILD-446</issuekey>
        <inwardlinks description="is a dependency of">
                <issuekey id="14183">BUILD-447</issuekey>
    <issuelinktype id="10002">
        <outwardlinks description="fixes">
                <issuekey id="14215">BUILD-461</issuekey>

I expected to be able to output the id as part of the property names so that
they don't collapse. But could not get it to work the way I need it to. I get
the following properties back from xmlproperty:

[echoproperties] a
dependency of

This is problematic because it combines different elements from different
parent elements and then I can't parse to determine the Jira issues that have a
particular link type (such as depends on).

Am I reading something wrong or isn't the includeSemanticAttribute=true suppose
to include the id value in the property name?

Is there any workaround? This is a showstopper for me. Thanks for any and all

You can test this with any Jira that provides xml search results.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message