-
Notifications
You must be signed in to change notification settings - Fork 441
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
brp-java-repack-jars still running despite setting rpmBrpJavaRepackJars to false #789
Comments
Awesome, thanks :)
A pull request would be the only thing left to do ;) |
I've tried using both the mentioned workaround (http://stackoverflow.com/a/36966909/1870803) and using Am I missing something?
|
Thanks for your report. Try the following to verify that this is an issue with native-packager
which gets inserted here ( source ) If this is all okay, can you add some information of your build system?
cheers, |
The problem is that the setting is actually inversed (as suggested here #199 (comment) ) Setting |
are there any plans to fix this issue? |
hi @mr-git
If you have the time to fix this, I'm happy to merge it :) |
…nstead of 'true')
* Fixed issue #789 where brpJavaRepack was negated (set to 'false' instead of 'true') * 1. Changed brpJavaRepack command to a supported flag on RPM 2. Changed the default of repack from true to false, which means repack will not run by default. * 1. Removed debug logs 2. Added a test to make sure java repack is ran when set to `true`. * Triggering rebuild. * Modified RPM names to avoid race conditions and failing tests. * Fixed broken tests (missing renaming in places, comments). * Updated RPM repacking description in the docs.
Hi,
This is related to this http://stackoverflow.com/questions/36940733/sbt-native-packager-rpm-brp-java-repack-jars-still-running-despite-setting-rpmbr question.
I was asked to open an issue referencing this https://github.com/sbt/sbt-native-packager/blob/master/src/main/scala/com/typesafe/sbt/packager/rpm/RpmPlugin.scala#L112.
Let me know if I can provide any more information.
The text was updated successfully, but these errors were encountered: