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

Do not add a dependencies block if it's already there #769

Merged
merged 1 commit into from
Jul 20, 2022

Conversation

desiderantes
Copy link
Contributor

Sometimes the publication already has a pom, so adding a node will result in a duplicated dependencies block

Sometimes the publication already has a pom, so adding a node will result in a duplicated dependencies block
@johnrengelman johnrengelman added this to the 7.1.3 milestone Jul 20, 2022
@johnrengelman johnrengelman merged commit 38566d5 into GradleUp:master Jul 20, 2022
@ind1go
Copy link

ind1go commented Jul 29, 2022

This is just what I was looking for! Do snapshots of the plugin get published that I can use pre-release?

@simPod
Copy link
Contributor

simPod commented Sep 11, 2022

Fixed in #791

@netomi
Copy link
Contributor

netomi commented Oct 11, 2022

Fixed in #791

This PR just reverts the behavior as it was prior to the conflicting commit.

@simPod
Copy link
Contributor

simPod commented Oct 11, 2022

Exactly. But since this PR broke the lib, it is better to revert rather than leave it as is.

@netomi
Copy link
Contributor

netomi commented Oct 11, 2022

PR #798 fixes the issue in a correct way by avoiding duplicate dependencies nodes.

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.

5 participants