lasselindqvist
lasselindqvist
If I understood correctly, you would like to have an example where defining this plugin in module A only would be able to obfuscate some of its dependencies at the...
Have you tried specifying the outjars to be same as their respective injars?
I resolved the conflicts for this. @lexchou can you confirm that they went as intended?
Also needs conflicts to be fixed now.
I will not be supporting any Java 8 issues here, but if you have fix for this it can be merged.
Hi. Seems to open for me now. Maybe it was a Github pages outage? Although https://www.githubstatus.com/ shows nothing.
This should be straightforward to fix by changing https://github.com/wvengen/proguard-maven-plugin/blob/master/src/main/java/com/github/wvengen/maven/proguard/ProGuardMojo.java#L515 We could just add a call to https://maven.apache.org/ref/3.2.3/apidocs/org/apache/maven/project/MavenProject.html#getRuntimeArtifacts() but both that and the existing getCompileArtifacts have been deprecated a long time....
@newobj do you have a simple test project for this you could share?
Hi. This would need more information in order to be actionable. What kind of a class do you expect it to obfuscate and what is the end result you get?
Hi. The docs do contain some outdated links. The Proguard documentation itself is located in https://www.guardsquare.com/manual/home The Maven plugin parameter documentation is located in https://wvengen.github.io/proguard-maven-plugin/proguard-mojo.html but most of the parameters...