[GRADLE-1829] ant.importBuild should support <ivy:*> tags in the Ant build file Created: 11/Oct/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-3
Fix Version/s: None

Type: Improvement
Reporter: Blaine Simpson Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

I know how to add to the classpath for Ant taskdefs, but the goal of ant.importBuild() is to support existing Ant build files. Since the Gradle team fully appreciates the beautiful tool Ivy, and Ivy is a major component of Gradle, I think it should support the most common use case for Ant build files using Ivy as documented in the Ivy reference guide.

The average Ant+Ivy user does not write taskdef tasks, they just make sure that an Ivy jar file is in the global Ant CLASSPATH and then use the <ivy:*> tags (per documentations sited above). Seeing as Gradle obviously has Ivy in its own CLASSPATH, I don't see how it could be very difficult to allow it to also be in Gradle's Ant execution CLASSPATH.

 Comments   
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:05:28 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.