Skip to content

Conversation

@bclozel
Copy link
Contributor

@bclozel bclozel commented Sep 25, 2019

Prior to this change, the Gradle publication configuration would be
applied to the wrong level of projects (subprojects of subprojects!),
resulting in no artifacts being published to the repository.

This commit updates the JFrog artifactory Gradle plugin version and
fixes the application of the publication configuration to align with
what's been done with artifactory and bintray configurations.

Signed-off-by: Brian Clozel bclozel@pivotal.io

Prior to this change, the Gradle publication configuration would be
applied to the wrong level of projects (subprojects of subprojects!),
resulting in no artifacts being published to the repository.

This commit updates the JFrog artifactory Gradle plugin version and
fixes the application of the publication configuration to align with
what's been done with artifactory and bintray configurations.

Signed-off-by: Brian Clozel <bclozel@pivotal.io>
@smaldini smaldini merged commit 5bcbf30 into rsocket:develop Sep 25, 2019
@bclozel bclozel deleted the fixpublication branch September 25, 2019 17:30
OlegDokuka pushed a commit that referenced this pull request Mar 2, 2020
Prior to this change, the Gradle publication configuration would be
applied to the wrong level of projects (subprojects of subprojects!),
resulting in no artifacts being published to the repository.

This commit updates the JFrog artifactory Gradle plugin version and
fixes the application of the publication configuration to align with
what's been done with artifactory and bintray configurations.

Signed-off-by: Brian Clozel <bclozel@pivotal.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants