-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
maven.buildMaven: drop #358562
base: master
Are you sure you want to change the base?
maven.buildMaven: drop #358562
Conversation
This was discouraged in NixOS#240553 Nobody is using it in-tree; the upstream repository provides the same builder in an output of its flake, for out-of-tree consumers: https://github.com/fzakaria/mvn2nix
Result of 1 package blacklisted:
1 package built:
|
Concerning the redirects, IIUC there's a place for parking deprecated attribute paths. Maintainers deprecate library functions and packages now and then, this should be similar, right? If not, it should be possible to create an anchor on the release note entry (not sure though, haven't tried that yet). This situation is exactly what the redirect guards are made for, and I strongly recommend using them. |
Yes, that seems logical. @GetPsyched (author of PR adding the redirects stuff), do you know how we could do this?
Definitely possible, we add anchors to list items all the time in the Nixpkgs manual:
I'm not sure |
That all release notes live in NixOS is a really unfortunate layer violation... The redirects system currently only supports relative paths, but this can be fixed quickly. |
|
||
You find this demo project at [https://github.com/fzakaria/nixos-maven-example](https://github.com/fzakaria/nixos-maven-example). | ||
|
||
### Solving for dependencies {#solving-for-dependencies} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this part not related to mvn2nix ?
I think you removed too much; (My attempt at mvn2nix is kind of a half-baked also; I ended up fighting so much enterprise pathalogical cases that it became unsurmountable as a side-effort) Either way PR looks ok. |
│ ├── avalon-framework-4.1.3.jar -> /nix/store/iv5fp3955w3nq28ff9xfz86wvxbiw6n9-avalon-framework-4.1.3.jar | ||
``` | ||
|
||
#### Double Invocation {#double-invocation} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I wrote this explanation section; I think it's all pretty good advice still on learning lessons on how to integrate java with Nix.
Maybe we can retitle these sections and just remove the top.
This was discouraged in #240553
Nobody is using it in-tree; the upstream repository provides the same builder in an output of its flake, for out-of-tree consumers: https://github.com/fzakaria/mvn2nix
Closes #11546
I'm not a fan of removing the entries from
doc/redirects.json
; I would love to redirect the anchors to the related changelog entry, but I'm not sure that's possible.Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.