[GRADLE-2312] Provide a way to augment the ant builder's classpath Created: 17/May/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

The linked to forum issue is about a failing ant import because the ant build uses Ivy. In the forum post there's a workaround that involves explicitly adding the Ivy dependency to ant via messing with the classloader. There should be a more controlled way of doing this.



 Comments   
Comment by Jurica Krizanic [ 10/Mar/15 ]

Is there a way of solving this issue without messing with the classloader?

I have Ant+Ivy combination which I want to import and Gradle fails with loading Ivy dependency.

Gradle is using own Ant library, not the one in the Ant installation in ANT_HOME, but it gives me a warning that library should exists on ANT_HOME\lib.

Tell me if I am wrong!

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:18:32 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.