[BAP-246] "Publish ivy descriptor" and "Publish maven descriptor" check-boxes don't always function Created: 11/Feb/15  Updated: 16/Jun/15  Resolved: 20/May/15

Status: Resolved
Project: Bamboo Artifactory Plug-in
Component/s: None
Affects Version/s: 1.7.7
Fix Version/s: 1.8.0

Type: Bug Priority: Normal
Reporter: Eyal Ben Moshe (Inactive) Assignee: Eyal Ben Moshe (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Trigger
was triggered by GAP-165 "publishPom" and "publishIvy" do not ... Resolved

 Description   

The check-boxes "Publish ivy descriptor" and "Publish maven description" (In Gradle builds) don't function
Ivy.xml and pom files are always published.



 Comments   
Comment by Eyal Ben Moshe (Inactive) [ 11/Feb/15 ]

Through the Artofactory Plugin UI, it is possible to configure whether to include the Maven and/or Ivy
descriptors (pom.xml or ivi.xml) as part of the deployed build artifacts to Artifactpry.
It is also possible to determine that behavior from within the gradle script itself, as part of the "artifactory" closure DSL by using the 2 properties:
publishPom = false
publishIvy = true
(this is to support this behavior by using the Gradle Artifactory Plugin without a CI server).
The desired behavior is that the plugin UI always overrides the DSL configuration, the same way it works for the configured Artifactory
repositories, meaning that if you do not check the "Publish Maven descriptors" or "Publish Ivy descriptors" check boxes in the UI, the descriptors
will not be published and vice versa.
The fix makes sure this behavior is implemented in all the following scenarios:
1. When the job is configured with "Project uses the Artifactory Gradle Plugin" checked and:
a. The gradle script uses publications.
b, The gradle script uses configurations.
2. When the job is configured with "Project uses the Artifactory Gradle Plugin" NOT checked.

Generated at Tue Jul 23 00:38:24 UTC 2019 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.