[java] Make CommentDefaultAccessModifier work for top-level classes, enums and annotations
@Nikita Karpukhin - thank you for the suggestion, it works on my side!
[6.1.0] Method must be overridden in [proguard.optimize.evaluation.SimpleEnumUseChecker] if ever called
Thanks, Eric, you're the best!
Thanks for the response! I'm not sure what you mean by "configuration without the quotes"? What I pasted was Gradle configuration. I also have other settings: overloadaggressively allowaccessmodification mergeinterfacesaggressively keepparameternames optimizationpasses 5 dontshrink dontusemixedcaseclassnames repackageclasses 'com.company' optimizations '!code/allocation/variable' This didn't help: keep allowobfuscation: true, 'public class com.company.SomeService' Only with this configuration it...
ProGuard does not adapt WebInitParam values
Yes, you are right, this issue can be closed. I was using the filters in Gradle in the wrong way. For anyone reading this in the future, in Gradle somethng like this should be written: libraryjars 'path-to-some-file.jar', filter: '!META-INF/versions/**' Instead of what I was doing until now: libraryjars 'path-to-some-file.jar(!META-INF/versions/**)'
Cannot add filters to lucene-core.jar
This issue has been resolved, thanks!
Thank you so much for the support!
Unfortunately the same problem also happens in 6.0.2 and as Hendrik says, this renders ProGuard unusable as the project cannot be built after that.
[6.0.1] Multiple "classes" directories when using Gradle plugin
Thank you so much for the support!
I'm using the Gradle plugin. I added -verbose but I'm not sure it did anything in a normal run. I tried addng --info to the gradle task and this is the output: Ignoring unused library classes... Original number of library classes: 105987 Final number of library classes: 2454 Backporting class files... Number of converted string concatenations: 0 Number of converted lambda expressions: 0 Number of converted static interface methods: 0 Number of converted default interface methods: 0 Number of replaced...
I'm using the Gradle plugin. I added -verbose but I'm not sure it did anything in a normal run. I tried addng --info to the gradle task and this is the output: Ignoring unused library classes... Original number of library classes: 105987 Final number of library classes: 2454 Backporting class files... Number of converted string concatenations: 0 Number of converted lambda expressions: 0 Number of converted static interface methods: 0 Number of converted default interface methods: 0 Number of replaced...
I'm using the Gradle plugin. I added -verbose but I'm not sure it did anything in a normal run. I tried addng --info to the gradle task and this is the output: Ignoring unused library classes... Original number of library classes: 105987 Final number of library classes: 2454 Backporting class files... Number of converted string concatenations: 0 Number of converted lambda expressions: 0 Number of converted static interface methods: 0 Number of converted default interface methods: 0 Number of replaced...
Unexpected error while merging classes
Yes, the workaround worked for me also. We are using it via some build system but with some Gradle magic and hacks, I managed to make it work. :) Waiting for ProGuard 6 for the "real" fix as this problem will become ubiquitous in the next few weeks after Java 9 comes out!
This also bit me with the 2.9 release of Log4j: https://blogs.apache.org/logging/entry/log4j-2-9-released I think Java 9 support is the most pressing issue now as we cannot upgrade to it until ProGuard supports it. Is there any timeline on when this could be achieved?