Skip to content

Conversation

@fabiobrz
Copy link
Member

Description

Changing the distribution managment repositories to align with changes in the JBoss org Maven repository policies.

Resolves #269

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Checklist

  • Code contributed by me aligns with current project license: Apache 2.0
  • Pull Request contains a description of the changes
  • Pull Request does not include fixes for multiple issues/topics
  • Code is self-descriptive and/or documented
  • N/A - I have implemented unit tests to cover my changes
  • N/A - I tested my code in OpenShift

Copy link
Collaborator

@mchoma mchoma left a comment

Choose a reason for hiding this comment

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

Changes here are what I expect regarding Nexus 3 migration. I am ok with merging this.

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Aug 29, 2025
@fabiobrz fabiobrz force-pushed the issue-269.fix-repos branch from fca1923 to eaf0ffb Compare August 29, 2025 12:26
@mchoma mchoma merged commit 9491208 into Intersmash:main Aug 29, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update distribution managment configuration

2 participants