[GRADLE-2636] ant.exec call failed randomly with message 'exec doesn't support the nested "xslt" element' Created: 16/Jan/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.3
Fix Version/s: None

Type: Bug
Reporter: Jem Mawson Assignee: Unassigned
Resolution: Won't Fix Votes: 3


 Description   

Our script contains the following:

ant.exec(executable: "mkdir") {
println "making: ${ARTIFACTS_HOME}/${artifactFolderName}"
arg(line: "-p ${ARTIFACTS_HOME}/${artifactFolderName}")
}

Usually it works fine, but just now it failed with the Ant error message:

exec doesn't support the nested "xslt" element

It smells like Gradle was trying to construct the XML for an ant exec task (??) and did not successfully transform the internals of that element.



 Comments   
Comment by Simon La Macchia [ 12/Mar/13 ]

I'm getting a similar intermittent error usnig gradle 1.5-rc-1. Most of the time it works fine, but occasionally I get:

"exec doesn't support the nested "exec" element."

Code:

ant.exec(executable: "rpmbuild", dir: "$topDir", failonerror: true, logError: true)

{ arg(line: "-ba SPECS/$specFile --buildroot $buildRootDir --define $appVersionParam") }

Sounds related, but I could be wrong.

Comment by Simon La Macchia [ 13/Mar/13 ]

The above error only occurs when running in parallel (gradle --parallel), so I suspect the conversion to/from XML for ant is not thread safe.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:27:19 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.