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

nexus: 3.70.1-02 -> 3.71.0-06 #372472

Closed
wants to merge 3 commits into from

Conversation

lukas-mertens
Copy link
Contributor

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Following the migration guide between nexus versions 3.69 to 3.71+, requires changing the java version inbetween. You first have to go to 3.70 on java 8, then switch to java 17 and switch the database to a h2 database, then you can upgrade to 3.71+

That's why this non-latest version should be in nixpkgs as well imho.

An even better way would probably be to split up nexus into something like nexus-3-69, nexus-3-70, nexus-3-71 packages or something like that to prevent breaking changes simply by doing a normal update on a stable release. But I am not familiar enough with the best practices in Nixpkgs regarding such changes and would request some help by someone more experienced to not fuck stuff up and break peoples installation without notification.

After 3.71.0-06 it seems as if updates are easy and such complicated migration paths are not necessary anymore.

You can find the nexus docs regarding updates here: https://help.sonatype.com/en/installation-and-upgrades.html


Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 8.has: module (update) This PR changes an existing module in `nixos/` 10.rebuild-darwin: 1-10 10.rebuild-linux: 1-10 labels Jan 9, 2025
@lukas-mertens lukas-mertens deleted the nexus-3-70-java-17 branch January 9, 2025 20:51
@lukas-mertens
Copy link
Contributor Author

Renaming of branch caused recreation of the PR, sorry, see #372484

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 8.has: module (update) This PR changes an existing module in `nixos/` 10.rebuild-darwin: 1-10 10.rebuild-linux: 1-10
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant