Thomas Neidhart

Yes, I understand, what you describe makes sense. Such cases are an exception of course, but they should be very limited, if you can add explicit rule for such classes...

@1: I dont know how JAX-RS endpoints are declared. Via annotations or config files? Does Proguard replace them properly? @2: you need to define the public API of your library...

no that does not help. You basically allow optimization of these classes, but prevent shrinking of them, so ending up with the same problem as using -dontshrink globally.

[proguard_bug.zip](https://github.com/Guardsquare/proguard/files/3868495/proguard_bug.zip)

Thanks for the report, I attached the reproducible sample from the sourceforge ticket here. It is clear what is going wrong, ProGuard does not obfuscate the respective interface methods in...

I checked the sample and inspected the resulting class files. The type erased methods from the interface are still there and are not obfuscated: ``` public final java.lang.Object getTypedSomething(); public...

So when modifying the Main class to include something like that: ``` MyPojo arg = inter.getTypedSomething(); ``` the resulting bytecode looks like that: ``` 22: invokeinterface #7, 1 // InterfaceMethod...

The problem description is clear, I can also see that result in the sample project: MyImplFail -> a: 14:14:MyPojo getTypedSomething() -> a 1:1:java.lang.Object getTypedSomething() -> getTypedSomething so the specialized method...

What are the target / source levels for the java plugin?

ok thanks, can you maybe share the snippet of code that loads / uses the obfuscated plugin which results in the crash I guess? Also what source / target level...