Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, I have never used ProGuard from Maven, only from Ant.</p> <p>I compare your configuration file with one in <a href="https://stackoverflow.com/questions/10929236/proguard-maven-with-java-7">here</a></p> <pre><code> &lt;options&gt; &lt;option&gt;-allowaccessmodification&lt;/option&gt; &lt;option&gt;-keep public class com.degoo.ui.ClientBackendStarter { public *; public static *; }&lt;/option&gt; &lt;/options&gt; &lt;injar&gt;${project.build.finalName}.jar&lt;/injar&gt; &lt;outjar&gt;${project.build.finalName}-small.jar&lt;/outjar&gt; </code></pre> <p>In your case you configure <code>injars</code> and <code>outjar</code> in different manner which is strange to see.</p> <blockquote> <p>(I compile all my code in the one jar) and filter every other libs. I have a lot of warnings cause it seems that proguard tries to obfuscate every jar in WEB-INF/lib</p> </blockquote> <p>In that case warnings come not from the fact that ProGuard tries to compile all the libs, but because when it obfuscates your filtered code it wants to see reference to extarnal libs. <a href="http://proguard.sourceforge.net/index.html#manual/introduction.html" rel="nofollow noreferrer">See this.</a></p> <p>You would need to add for every external jar referenced in your code </p> <pre><code>&lt;lib&gt;path/lib.jar&lt;/lib&gt; </code></pre> <p>This would probably help you to avoid many warning, but the real art start when you configure <code>-keep</code> options. I would recommend to start with this configuration <a href="https://stackoverflow.com/a/7511926/1360074">https://stackoverflow.com/a/7511926/1360074</a> If that works eventually try to get more obfuscation.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload