Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub-project can't specify individual properties #115

Open
enaess opened this issue Jun 12, 2024 · 1 comment
Open

Sub-project can't specify individual properties #115

enaess opened this issue Jun 12, 2024 · 1 comment
Labels
question Further information is requested

Comments

@enaess
Copy link

enaess commented Jun 12, 2024

How can we help?

This question was asked previously on stackoverflow.com: https://stackoverflow.com/questions/48007689/artifactory-gradle-and-properties-mutation-by-artifactorypublish-task-dsl

And a GIST: was put out on GitHub here:
https://github.com/lavcraft/gradle-artifactory-build-info-extractor-problems/tree/master

Essentially, i have the root project per documentation configuring access to artifactory:

artifactory {
  contextUrl = project.findProperty('artifactory_contextUrl')
  publish {
      repository {
        repoKey = 'libs-snapshot-local'
        username = project.findProperty('artifactory_user')
        password = project.findProperty('artifactory_password')
      }

      defaults {
        publications('nebula')
        publishConfigs('archives')
        publishIvy = false
        properties {
          nebula '*:*:*:*@*', 'want_to_add':'but not' // add only to *.pom artifacts. Why?
          mavenJava commonProperties, '*:*:*:*@*'
        }
      }
    }
 }

A sub-project adds a configuration and then tries to configure the properties closure:

artifactoryPublish {
  properties = ['aa':'aaa']
  properties {
    nebula '*:*:*:*@*', 'not_added_prop':'sub0'
  }
}

I can't seem to use the

artifactoryPublish { 
    properties {
        all '*:*:*:*@*', prop1: "value1"
    }
} 

Would someone please have a look to see if I completely miss-understood how this would work here?

@enaess enaess added the question Further information is requested label Jun 12, 2024
@enaess
Copy link
Author

enaess commented Jun 12, 2024

@yahavi You have any insights here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant