[GRADLE-2194] Archive tasks require the BasePlugin to get useful defaults Created: 22/Mar/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Justin Ryan Assignee: Unassigned
Resolution: Won't Fix Votes: 0


As per the documentation, http://gradle.org/docs/current/userguide/userguide_single.html#archiveTasksNamingProperties, any archive task's baseName will default to project.name. This is apparently true iff the BasePlugin is applied somewhere, then it will run configureArchiveDefaults(). I can see that the archives are pulling actually pulling baseName from archivesBaseName, this is a fine config option, but the archive tasks need to work without the BasePlugin. Right now they'll just produce files named ".zip". There doesn't seem to be a compelling connection between project.name and the BasePlugin, it seems logical that archive tasks could default to project.name, since it's around and its immutable.

My users are looking for scripting replacements, and when I tell them they have to "apply plugin: 'java'" their knee jerk reaction is to say "oh this is a java build system, nevermind, I'll use something else."

This assumes that the BasePlugin is optional, if it's not, why isn't it just always applied then?

Example that should work:
task dist(type: Zip)

{ // produces file called ".zip" from 'tobezipped' }

println "Project name: ${project.name}"
println "Base Name: ${dist.baseName}" // prints as null

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