[GRADLE-756] Conditional artifact publication Created: 27/Nov/09  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Ross Black Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

Is there a way to conditionally add an artifact to a configuration, where the condition is evaluated at runtime?
eg. I only want to add an artifact if a specific directory exists.

I was hoping the following would work (but it does not):
—
project.configurations

{ api }

Task apiTask = project.task('apiJar', type: Jar, dependsOn: 'classes')

{ fileSet(dir: project.apiClassesDir) }

apiTask.onlyIf

{project.apiClassesDir.exists()}

project.artifacts

{ api apiTask }

—

The apiJar task correctly only generates the jar if the directory exists, but the artifact handler always expects that the file specified by the apiJar task exists even if the task has not run.

 Comments   
Comment by Ross Black [ 27/Nov/09 ]

There is a work around, not a good one though.

// This action only executes if apiTask is not skipped
apiTask << {
project.artifacts

{ api apiTask }

}

uploadApi {
// As we add the apiTask to the api configuration at execution time, Gradle can't autowire this at configuration time. So we have to create the dependsOn manually
dependsOn apiJar
repositories.flatDir(dirs: "$buildDir/repo")
}

Comment by Ross Black [ 27/Nov/09 ]

This seems to be related to GRADLE-755 - Don't create jar if it has no input-files.

Comment by Hans Dockter [ 22/Apr/10 ]

Not creating an empty jar would be a work around. We probably won't fix this for 0.9. But there is an easy way to achieve this functionality:

doLast {
   // if the jar just contains the manifest
   if (inputs.files.files.size() == 1) { delete(archivePath) } 
}

What we will provide in 1.0 is a way to express your requirement explicitly.

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