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

Sonar was relocated #290

Merged
merged 1 commit into from
May 7, 2024
Merged

Sonar was relocated #290

merged 1 commit into from
May 7, 2024

Conversation

dmlloyd
Copy link
Member

@dmlloyd dmlloyd commented May 7, 2024

No description provided.

@dmlloyd
Copy link
Member Author

dmlloyd commented May 7, 2024

One thing I'm not sure about here is whether we should also keep the old coordinates with a fixed version, so that we don't end up with two copies on the class path.

Copy link
Member

@jamezp jamezp left a comment

Choose a reason for hiding this comment

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

I think it's best to likely just use the new groupId. It's a simple thing to change when a consumer upgrades the parent.

@dmlloyd dmlloyd merged commit a473c8a into jboss:main May 7, 2024
1 check passed
@dmlloyd dmlloyd deleted the sonar branch May 7, 2024 19:12
dmlloyd added a commit to dmlloyd/jboss-parent-pom that referenced this pull request Jun 4, 2024
See jboss#290 for originall incorrect change
dmlloyd added a commit to dmlloyd/jboss-parent-pom that referenced this pull request Jun 4, 2024
See jboss#290 for original incorrect change
@dmlloyd dmlloyd mentioned this pull request Jun 4, 2024
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