-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
rabbitmq-java-client: out of date #169644
Comments
I do not use rabbitmq, but I did upgrade this package just to learn how to do a Maven derivation, and I see no point in doing it. I can create the same amqp-client-5.15.0.jar artifact than the one in the download page (same list of classes at least), and that's all there is. A simple packaged library with no entry point for a command line application. The current, very old, derivation provides a single wrapped script to run some performance test as a binary, alongside the library and all its dependencies packaged together. But the up to date way to run test according to the README is through Maven inside the source directory. So, there is no such script to package in the output. There are no test classes in the output artifact. Just the library. I'd argue to remove this derivation. It has no use. No other package uses it as dependency (it's not something that happens with Java, dependencies are downloaded from Maven repos, otherwise Nix would have to package thousands of new Java packages for dependencies), and it's just a library, no CLI to run. |
It's used by the rabbitmq nixos test, so having a working version would be quite useful. Or we also remove it from the test. |
I'll take a look at this package tomorrow. Looks like the latest version is |
This isn't as simple as it appears. It now depends on a Python module; it is available in |
Lives here now. Out of date and depends on python2. Last touched July 2014.
Checklist
Project name
nix search
name:current version: 3.3.4
desired version: 5.14.2
Notify maintainers
maintainers: NONE!
Note for maintainers
Please tag this issue in your PR.
The text was updated successfully, but these errors were encountered: