[GRADLE-2166] Ability to directly load an Ant file from within a jar Created: 12/Mar/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: Kristian Kime Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Currently the ant import functionality must have a file on disk to load (via project.ant.importBuild("location/on/disk/...") for example). It would be convenient to have a way to have a way to load ant files that were included as a resources in plugin jars.

By way of motivation I can say one of the things that made convincing my company to switch from Ant to Gradle much easier was the fact that we were able to build a Gradle plugin that could perform all of the previous custom ant tasks we were using. But the way we built this functionality was the somewhat awkward method of including the old ant xml files as resources in the jar. Then whenever the Gradle build is run it copies the ant files out to a temp location, imports them and continues on. While this works it hurts the normally nearly seamless integration between Gradle and Ant and having a convenience method to load the ant resource files directly seems reasonable.

 Comments   
Comment by Luke Daley [ 13/Mar/12 ]

This does seem like a good idea. We should be able to do something here post 1.0.

Comment by Szczepan Faber [ 13/Mar/12 ]

Thanks for feedback - we'll consider this feature for improving ant integration

Comment by Szczepan Faber [ 13/Mar/12 ]

Thanks for feedback - we'll consider this feature for improving the ant integration.

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