[GRADLE-2039] DefaultAntBuilder always uses script directory as basedir Created: 09/Jan/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Michael Brand Assignee: Unassigned
Resolution: Won't Fix Votes: 10


 Description   

The DefaultAntBuilder.importBuild() method hard-codes a basedir value to the directory containing the script:

File baseDir = file.parentFile

Set existingAntTargets = new HashSet(antProject.targets.keySet())
File oldBaseDir = antProject.baseDir
antProject.baseDir = baseDir

This cannot be overridden and forces the basedir to the script's dirctory.

One possible solution would be to add an optional parameter that for the basedir. This would require that the gradle script be aware of the ant script's basedir, but would be easy to implement.

A more complex solution would be probably involve loading a new AntBuilder and interrogating it or delegating to it. This would allow the ant script to determine its basedir, but would probably require a significant rewrite of the function or possibly significant overhead.

A workaround is to create an second ant script located in the first's basedir. This script would contain a single line that imports the first.

 Comments   
Comment by Carsten Lenz [ 22/Jul/14 ]

An additional workaround is to set the baseDir property on the created AntTarget gradle tasks

tasks.withType(AntTarget) { t ->
    t.baseDir = file('/my/custom/baseDir/path')
}
Comment by Scott Resnik [ 29/Jan/16 ]

This work around above doesn't work for me. Using Gradle 2.10.

The basedir of the ant build is still set to directory of the build.xml. The basedir attribute of the project element is ignored as well.

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