Skip to content

Update paths due to Nexus 3 migration #250

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.

Sign up for GitHub

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

Merged
jbliznak merged 1 commit into from
Aug 29, 2025
Merged

Update paths due to Nexus 3 migration #250

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ repository like this:
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Maven Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
<url>https://repository.jboss.org/nexus/repository/public/</url>
</repository>
</repositories>

Expand Down
21 changes: 5 additions & 16 deletions RELEASE_PROCEDURE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,24 +32,13 @@ This text assumes that the version number for a release is X.Y.Z.

11. `mvn release:perform -Pwildfly10`

12. Go to `https://repository.jboss.org/nexus/index.html#stagingRepositories`
12. Create a GitHub Release.

13. Find the correct staging repository; it will be called
`wildfly_extras-NNNN`. Verify the owner name; it should be your
JBoss.org username. Also check the content of the repository.
13. Close the relevant GitHub Milestone. Optionally create a new Milestone.

14. Close the staging repository. Nexus will perform some validations.
If successful, Nexus will send a confirmation e-mail.

15. Release the repository. Nexus will send another confirmation e-mail.

16. Create a GitHub Release.

17. Close the relevant GitHub Milestone. Optionally create a new Milestone.

18. Add a new heading to the top of `CHANGELOG.md`.
14. Add a new heading to the top of `CHANGELOG.md`.
Its text should be: `X.Y.Z+1 (not yet released)`.

19. `git commit -m "add next version number to changelog"`
15. `git commit -m "add next version number to changelog"`

20. Send a release announcement.
16. Send a release announcement.
8 changes: 4 additions & 4 deletions pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,14 +45,14 @@
</issueManagement>
<distributionManagement>
<repository>
<id>jboss-releases-repository</id>
<name>JBoss Releases Repository</name>
<url>https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/</url>
<id>jbossqe-eap-releases-repository</id>
<name>JBoss QE EAP Releases Repository</name>
<url>https://repository.jboss.org/nexus/repository/jbossqe-eap/</url>
</repository>
<snapshotRepository>
<id>jboss-snapshots-repository</id>
<name>JBoss Snapshots Repository</name>
<url>https://repository.jboss.org/nexus/content/repositories/snapshots/</url>
<url>https://repository.jboss.org/nexus/repository/snapshots/</url>
</snapshotRepository>
</distributionManagement>

Expand Down
2 changes: 1 addition & 1 deletion settings.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Usage:
<repositories>
<repository>
<id>jboss-public</id>
<url>https://repository.jboss.org/nexus/content/groups/public-jboss</url>
<url>https://repository.jboss.org/nexus/repository/public/</url>
</repository>
</repositories>
</profile>
Expand Down