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

When jboss-release is in effect, release to r.j.o #244

Merged
merged 1 commit into from
Dec 6, 2023

Conversation

dmlloyd
Copy link
Member

@dmlloyd dmlloyd commented Dec 4, 2023

This takes the place of specifying distributionManagement, which was removed in 0070843.

@@ -821,7 +821,8 @@
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<updateReleaseInfo>true</updateReleaseInfo>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was removed because this is no longer a valid configuration option for this plugin (since ???).

Comment on lines +824 to +825
<altReleaseDeploymentRepository>${jboss.releases.repo.id}::${jboss.releases.repo.url}</altReleaseDeploymentRepository>
<altSnapshotDeploymentRepository>${jboss.snapshots.repo.id}::${jboss.snapshots.repo.url}</altSnapshotDeploymentRepository>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine to me. It looks like you could just use altDeploymentRepository and it will use that if either of the other two are null.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fair, but since we have separate releases and snapshots this seemed to be more correct. That said: there would be different behaviors since if someone gives altDeploymentRepository (rather than altXxxxDeploymentRepository) on the command line or in their POM, I think it would be ignored with this configuration. I'm OK with either solution (specifically, leaving this as-is versus changing altReleaseDeploymentRepository to altDeploymentRepository). WDYT?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As Brian mentioned in chat, normally people should use the properties to customize the definition anyway... maybe.

@dmlloyd dmlloyd marked this pull request as ready for review December 5, 2023 16:49
@dmlloyd dmlloyd requested a review from jamezp December 5, 2023 17:28
@bstansberry
Copy link
Contributor

I said this in chat but I'll say it here too, as this may be a better historical record.

This changes the semantics of the jboss-release profile, but only for projects that are 1) using jboss-release and 2) using their own distributionManagement section instead of relying on this pom entirely or using the maven properties involved in this PR that used to drive the behavior of this pom's now-removed distributionManagement.

I think that's a corner case, perhaps non-existent, so I approved this.

@dmlloyd dmlloyd merged commit 5c4d665 into jboss:main Dec 6, 2023
1 check passed
@dmlloyd dmlloyd deleted the rjo-release branch December 6, 2023 15:27
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.

3 participants