RubyGems - sometsome - Versions diffs - 1.0.2 → 3.10.42 - Mend

sometsome 1.0.2 → 3.10.42

Files changed (732) hide show

data/lib/proguard4.7/docs/drop1.gif ADDED

Binary file

data/lib/proguard4.7/docs/drop2.gif ADDED

Binary file

data/lib/proguard4.7/docs/drop3.gif ADDED

Binary file

data/lib/proguard4.7/docs/favicon.ico ADDED

Binary file

data/lib/proguard4.7/docs/feedback.html ADDED

@@ -0,0 +1,120 @@
+<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="content-script-type" content="text/javascript">
+<meta http-equiv="content-style-type" content="text/css">
+<link rel="stylesheet" type="text/css" href="style.css">
+<title>ProGuard Feedback</title>
+<script type="text/javascript" language="JavaScript">
+<!--
+if (window.self==window.top)
+  window.top.location.replace("index.html#"+window.location.pathname+window.location.hash);
+else {
+  var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
+  if (window.top.location.hash!=hash)
+    window.top.location.hash=hash;
+}
+//-->
+</script>
+</head>
+<body>
+<h2>Feedback</h2>
+By now, I've invested a fair amount of time in <b>ProGuard</b>. You can help
+by providing feedback! If you have problems, bugs, bug fixes, ideas,
+encouragements, etc., please get in touch:
+<p>
+<ul class="spacious">
+<li>Through
+    <a href="http://www.saikoa.com/proguard/support" target="_top">Saikoa</a>,
+    we provide professional support for ProGuard. If you find ProGuard useful
+    and you would like to have some professional backing, this is the place to
+    go.</li>
+<li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182456"
+    target="other">help forum</a> (at SourceForge) is the right place to ask
+    questions about any problems you might have configuring and running
+    ProGuard. At this time, I can generally only assist other open source
+    projects though. If you're working on commercial software, please consider
+    our professional support above.</li>
+<li>The <a href="https://sourceforge.net/projects/proguard/forums/forum/182455"
+    target="other">open discussion forum</a> (at SourceForge) offers a place
+    to share your thoughts and discuss new ideas.</li>
+<li>The <a
+    href="http://sourceforge.net/tracker/?atid=474704&group_id=54750&func=browse"
+    target="other">bug tracking page</a> (at SourceForge) allows you to submit
+    and consult bug reports. Please make sure the reports are complete and
+    concise. If I can't reproduce the problem, I most likely can't fix it
+    either.</li>
+<li>The <a
+    href="http://sourceforge.net/tracker/?atid=474707&group_id=54750&func=browse"
+    target="other">feature request page</a> (at SourceForge) allows you to
+    submit and consult feature requests. I generally have my own road map in
+    mind, but this is the place express your interest in new and existing
+    ideas.</li>
+<li>The <a href="https://sourceforge.net/projects/proguard/files/"
+    target="other">download section</a> at SourceForge and the <a
+    href="http://software.freshmeat.net/projects/proguard/"
+    target="other">project page</a> at FreshMeat offer the possibility to
+    subscribe to the announcements of new releases. They are the most
+    efficient way to stay abreast of the latest developments.</li>
+<li>For anything that doesn't fall in the above categories, you can mail me
+    directly at
+<script type="text/javascript" language="JavaScript">
+<!--
+document.write("<a href=\"ma");
+document.write("ilto:");
+document.write("lafortune");
+document.write("&#64;");
+document.write("users.sourceforge.net\">");
+document.write("lafortune");
+document.write("&#64;");
+document.write("users.sourceforge.net");
+document.write("</a>");
+document.write(" <em>or</em> at ");
+document.write("<a href=\"ma");
+document.write("ilto:");
+document.write("eric");
+document.write("&#64;");
+document.write("graphics.cornell.edu\">");
+document.write("eric");
+document.write("&#64;");
+document.write("graphics.cornell.edu");
+document.write("</a>");
+//-->
+</script>
+<noscript>
+&lt;&nbsp;lafortune&nbsp;&#64;&nbsp;users&nbsp;.&nbsp;sourceforge&nbsp;.&nbsp;net&nbsp;&gt;
+<em>or</em> at
+&lt;&nbsp;eric&nbsp;&#64;&nbsp;graphics&nbsp;.&nbsp;cornell&nbsp;.&nbsp;edu&nbsp;&gt; (please remove the spaces)
+</noscript>
+.</li>
+</ul>
+<p>
+I can't promise a swift answer, or any answer at all, for that matter, but I
+like seeing any constructive comments.
+<p>
+<b>ProGuard</b> isn't a typical open source project, in the sense that I am
+<em>not</em> looking for code contributions. Developing on my own allows me to
+do things my way, without the overhead and compromises associated with larger
+projects.
+<hr />
+<noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript>
+<address>
+Copyright &copy; 2002-2011
+<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
+</address>
+</body>
+</html>

data/lib/proguard4.7/docs/index.html ADDED

@@ -0,0 +1,92 @@
+<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="content-script-type" content="text/javascript">
+<meta http-equiv="content-style-type" content="text/css">
+<meta name="author" content="Eric Lafortune">
+<meta name="description" content="ProGuard: java shrinker, optimizer, obfuscator, and preverifier">
+<meta name="keywords" content="java obfuscator, optimizer, shrinker, preverfier">
+<link rel="stylesheet" type="text/css" href="style.css">
+<link rel="shortcut icon" type="image/x-icon" href="favicon.ico">
+<title>ProGuard</title>
+</head>
+<script type="text/javascript" language="JavaScript">
+<!--
+var main="main.html";
+if (window.location.hash.length > 1)
+  main=window.location.hash.substr(1);
+var sections="sections.html";
+if (main.search(/manual\//) >= 0)
+  sections="manual/sections.html";
+document.write("<frameset rows=\"50,*\" framespacing=\"0\" frameborder=\"no\"><frame id=\"title\" name=\"title\" src=\"title.html\" scrolling=\"no\" marginwidth=\"0\" marginheight=\"0\" noresize /><frameset cols=\"120,*\" framespacing=\"0\" frameborder=\"no\"><frame id=\"sections\" name=\"sections\" src=\""+sections+"\" scrolling=\"no\" marginwidth=\"0\" marginheight=\"0\" noresize /><frame id=\"main\" name=\"main\" src=\""+main+"\" scrolling=\"auto\" marginwidth=\"10\" marginheight=\"10\" noresize /></frameset></frameset>");
+//-->
+</script>
+<noscript>
+<frameset
+ rows="50,*"
+ framespacing="0"
+ frameborder="no">
+<frame
+ id="title"
+ name="title"
+ src="title.html"
+ scrolling="no"
+ marginwidth="0"
+ marginheight="0"
+ noresize />
+<frameset
+ cols="120,*"
+ framespacing="0"
+ frameborder="no">
+<frame
+ id="sections"
+ name="sections"
+ src="sections.html"
+ scrolling="no"
+ marginwidth="0"
+ marginheight="0"
+ noresize />
+<frame
+ id="main"
+ name="main"
+ src="main.html"
+ scrolling="auto"
+ marginwidth="10"
+ marginheight="10"
+ noresize />
+</frameset>
+</frameset>
+</noscript>
+<noframes>
+<body>
+<p class="intro">
+<b>ProGuard</b> is a free Java class file shrinker, optimizer, obfuscator, and
+preverifier. It detects and removes unused classes, fields, methods, and
+attributes. It optimizes bytecode and removes unused instructions. It renames
+the remaining classes, fields, and methods using short meaningless names.
+Finally, it preverifies the processed code for Java 6 or for Java Micro
+Edition.
+</p>
+<p>
+Your browser doesn't support frames, but that's cool.
+<p>
+You can go straight to the <a href="main.html">main page</a>.
+<hr />
+<address>
+Copyright &copy; 2002-2011
+<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
+</address>
+</body>
+</noframes>
+</html>

data/lib/proguard4.7/docs/license.html ADDED

@@ -0,0 +1,60 @@
+<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="content-style-type" content="text/css">
+<link rel="stylesheet" type="text/css" href="style.css">
+<title>ProGuard License</title>
+<script type="text/javascript" language="JavaScript">
+<!--
+if (window.self==window.top)
+  window.top.location.replace("index.html#"+window.location.pathname+window.location.hash);
+else {
+  var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
+  if (window.top.location.hash!=hash)
+    window.top.location.hash=hash;
+}
+//-->
+</script>
+</head>
+<body>
+<h2>License</h2>
+<b>ProGuard</b> is free. You can use it freely for processing your
+applications, commercial or not. Your code obviously remains yours after
+having been processed, and its license can remain the same.
+<p>
+<b>ProGuard</b> itself is copyrighted, but its distribution license provides
+you with some rights for modifying and redistributing its code and its
+documentation. More specifically, <b>ProGuard</b> is distributed under the
+terms of the <a href="GPL.html">GNU General Public License</a> (GPL), version
+2, as published by the <a href="http://www.fsf.org/" target="other">Free
+Software Foundation</a> (FSF). In short, this means that you may freely
+redistribute the program, modified or as is, on the condition that you make
+the complete source code available as well. If you develop a program that is
+linked with
+<b>ProGuard</b>, the program as a whole has to be distributed at no charge
+under the GPL. I am granting a <a href="GPL_exception.html">special
+exception</a> to the latter clause (in wording suggested by
+the <a href="http://www.gnu.org/copyleft/gpl-faq.html#GPLIncompatibleLibs"
+target="other">FSF</a>), for combinations with the following stand-alone
+applications: Apache Ant, Apache Maven, the Google Android SDK, the Eclipse
+ProGuardDT GUI, the EclipseME JME IDE, the Oracle NetBeans Java IDE, the Oracle
+JME Wireless Toolkit, the Simple Build Tool for Scala, the NeoMAD Tools by
+Neomades, the Javaground Tools, and the Sanaware Tools.
+<p>
+The <b>ProGuard user documentation</b> represents an important part of this
+work. It may only be redistributed without changes, along with the unmodified
+version of the code.
+<hr />
+<noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript>
+<address>
+Copyright &copy; 2002-2011
+<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
+</address>
+</body>
+</html>

data/lib/proguard4.7/docs/main.html ADDED

@@ -0,0 +1,102 @@
+<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="content-style-type" content="text/css">
+<meta name="author" content="Eric Lafortune">
+<meta name="description" content="ProGuard: java shrinker, optimizer, obfuscator, and preverifier">
+<meta name="keywords" content="java obfuscator, optimizer, shrinker, preverfier">
+<link rel="stylesheet" type="text/css" href="style.css">
+<title>ProGuard Main</title>
+<script type="text/javascript" language="JavaScript">
+<!--
+if (window.self==window.top)
+  window.top.location.replace("index.html#"+window.location.pathname+window.location.hash);
+else {
+  if (window.top.location.hash!="")
+    window.top.location.hash="";
+}
+//-->
+</script>
+</head>
+<body>
+<h2>Main</h2>
+<p class="intro">
+<b>ProGuard</b> is a free Java class file shrinker, optimizer, obfuscator, and
+preverifier. It detects and removes unused classes, fields, methods, and
+attributes. It optimizes bytecode and removes unused instructions. It renames
+the remaining classes, fields, and methods using short meaningless names.
+Finally, it preverifies the processed code for Java 6 or for Java Micro
+Edition.
+</p>
+Some uses of <b>ProGuard</b> are:
+<ul>
+<li>Creating more compact code, for smaller code archives, faster transfer
+    across networks, faster loading, and smaller memory footprints.</li>
+<li>Making programs and libraries harder to reverse-engineer.</li>
+<li>Listing dead code, so it can be removed from the source code.</li>
+<li>Retargeting and preverifying existing class files for Java 6, to take full
+    advantage of Java 6's faster class loading.</li>
+</ul>
+<p>
+<b>ProGuard</b>'s main advantage compared to other Java obfuscators is
+probably its compact template-based configuration. A few intuitive command
+line options or a simple configuration file are usually sufficient.
+The user manual explains all available options and shows examples of this
+powerful configuration style.
+<p>
+<b>ProGuard</b> is fast. It only takes seconds to process programs and
+libraries of several megabytes. The results section presents actual figures
+for a number of applications.
+<p>
+<b>ProGuard</b> is a command-line tool with an optional graphical user
+interface. It also comes with plugins for Ant and for the JME Wireless
+Toolkit.
+<p>
+<p class="intro">
+<b>ProGuard</b> is being used in various development contexts, ranging from
+small Android apps to large Java applications and libraries. Its user base is
+continuing to grow at a fast pace. In order to better manage the many
+questions and requests, we are now providing professional support at
+<a target="_top" href="http://www.saikoa.com/proguard/support">Saikoa</a>.
+</p>
+The following sections provide more detailed information:
+<ul>
+<li><a href="main.html">Main</a>: this overview page.</li>
+<li><a href="results.html">Results</a>: some results obtained with
+    <b>ProGuard</b>, including timings and memory usage.</li>
+<li><a href="FAQ.html">FAQ</a>: answers to some Frequently Asked Questions.</li>
+<li><a href="manual/index.html">Manual</a>: the complete <b>ProGuard</b> user
+    manual, with examples and troubleshooting tips.</li>
+<li><a href="quality.html">Quality</a>: a discussion of the (excellent) quality
+    of <b>ProGuard</b>'s code.</li>
+<li><a href="screenshots.html">Screenshots</a>: some impressions of what            <b>ProGuard</b> looks like.</li>
+<li><a href="testimonials.html">Testimonials</a>: what users think of
+    <b>ProGuard</b>.</li>
+<li><a href="license.html">License</a>: <b>ProGuard</b> is free, under a GPL
+    license.</li>
+<li><a href="downloads.html">Downloads</a>: download the <b>ProGuard</b>
+    package yourself.</li>
+<li><a href="feedback.html">Feedback</a>: tell me about your experiences, or
+    learn from others on our forums.</li>
+<li><a href="acknowledgements.html">Acknowledgements</a>: people who have been
+    helpful.</li>
+<li><a href="alternatives.html">Alternatives</a>: other Java obfuscators,
+    optimizers, and shrinkers.</li>
+</ul>
+<hr />
+<noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript>
+<address>
+Copyright &copy; 2002-2011
+<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
+</address>
+</body>
+</html>

data/lib/proguard4.7/docs/manual/ant.html ADDED

@@ -0,0 +1,634 @@
+<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
+<meta http-equiv="content-style-type" content="text/css">
+<link rel="stylesheet" type="text/css" href="style.css">
+<title>Ant Task</title>
+<script type="text/javascript" language="JavaScript">
+<!--
+if (window.self==window.top)
+  window.top.location.replace("../index.html#"+window.location.pathname+window.location.hash);
+else {
+  var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
+  if (window.top.location.hash!=hash)
+    window.top.location.hash=hash;
+}
+//-->
+</script>
+</head>
+<body>
+<h2>Ant Task</h2>
+<b>ProGuard</b> can be run as a task in the Java-based build tool Ant (version
+1.6.0 or higher).
+<p>
+Before you can use the <code>proguard</code> task, you have to tell Ant about
+this new task. The easiest way is to add the following line to your
+<code>build.xml</code> file:
+<p>
+<pre>
+&lt;taskdef resource="proguard/ant/task.properties"
+         classpath="/usr/local/java/proguard/lib/proguard.jar" /&gt;
+</pre>
+<p>
+Please make sure the class path is set correctly for your system.
+<p>
+There are three ways to configure the ProGuard task: using an external
+configuration file, using embedded ProGuard configuration options, or using
+the equivalent XML configuration tags. These three ways can be combined,
+depending on practical circumstances and personal preference.
+<p>
+<h3>1. An external ProGuard configuration file</h3>
+The simplest way to use the ProGuard task in an Ant build file is to keep your
+ProGuard configuration file, and include it from Ant. You can include your
+ProGuard configuration file by setting
+the <a href="#configuration_attribute"><code>configuration</code></a>
+attribute of your
+<code>proguard</code> task. Your ant build file will then look like this:
+<p>
+<pre>
+&lt;taskdef resource="proguard/ant/task.properties"
+         classpath="/usr/local/java/proguard/lib/proguard.jar" /&gt;
+&lt;proguard configuration="myconfigfile.pro"/&gt;
+</pre>
+<p>
+This is a convenient option if you prefer ProGuard's configuration style over
+XML, if you want to keep your build file small, or if you have to share your
+configuration with developers who don't use Ant.
+<p>
+<h3>2. Embedded ProGuard configuration options</h3>
+Instead of keeping an external ProGuard configuration file, you can also copy
+the contents of the file into the nested text of the <code>proguard</code> task
+(the PCDATA area). Your Ant build file will then look like this:
+<p>
+<pre>
+&lt;taskdef resource="proguard/ant/task.properties"
+         classpath="/usr/local/java/proguard/lib/proguard.jar" /&gt;
+&lt;proguard&gt;
+  -libraryjars ${java.home}/lib/rt.jar
+  -injars      in.jar
+  -outjars     out.jar
+  -keepclasseswithmembers public class * {
+      public static void main(java.lang.String[]);
+  }
+&lt;/proguard&gt;
+</pre>
+<p>
+Some minor syntactical changes are required in order to conform with the XML
+standard.
+<p>
+Firstly, the <code>#</code> character cannot be used for comments in an XML
+file. Comments must be enclosed by an opening <code>&lt;!--</code> and a
+closing <code>--&gt;</code>. All occurrences of the <code>#</code> character
+can be removed.
+<p>
+Secondly, the use of <code>&lt;</code> and <code>&gt;</code> characters would
+upset the structure of the XML build file. Environment variables are now
+enclosed by an opening <code>${</code> and a closing <code>}</code>. This
+syntax also allows you to use Ant properties within the ProGuard
+configuration. Other occurrences of <code>&lt;</code> and <code>&gt;</code>
+have to be encoded as <code>&amp;lt;</code> and <code>&amp;gt;</code>.
+<p>
+<h3>3. XML configuration tags</h3>
+If you really prefer a full-blown XML configuration, you can replace the
+ProGuard configuration options by XML configuration tags. The resulting
+configuration will be equivalent, but much more verbose and difficult to read,
+as XML goes. The remainder of this page presents the supported tags. For a
+more extensive discussion of their meaning, please consult the traditional <a
+href="usage.html">Usage</a> section. You can find some sample configuration
+files in the <code>examples/ant</code> directory of the ProGuard distribution.
+<p>
+<h2><a name="proguard">Task Attributes and Nested Elements</a></h2>
+The <code><b>&lt;proguard&gt;</b></code> task and the
+<code><b>&lt;proguardconfiguration&gt;</b></code> task can have the following
+attributes (only for <code>&lt;proguard&gt;</code>) and nested
+elements:
+<dl>
+<dt><a name="configuration_attribute"><code><b>configuration</b></code></a>
+    = "<i>filename</i>"</dt>
+<dd>Read and merge options from the given ProGuard-style configuration
+    file. Note: for reading XML-style configurations, use the <a
+    href="#configuration_element"><code>configuration</code></a>
+    <i>element</i>.</dd>
+<dt><a href="usage.html#skipnonpubliclibraryclasses"><code><b>skipnonpubliclibraryclasses</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Ignore non-public library classes.</dd>
+<dt><a href="usage.html#dontskipnonpubliclibraryclassmembers"><code><b>skipnonpubliclibraryclassmembers</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Ignore package visible library class members.</dd>
+<dt><a href="usage.html#target"><code><b>target</b></code></a>
+    = "<i>version</i>"
+    (default = none)</dt>
+<dd>Set the given version number in the processed classes.</dd>
+<dt><a href="usage.html#forceprocessing"><code><b>forceprocessing</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Process the input, even if the output seems up to date.</dd>
+<dt><a href="usage.html#printseeds"><code><b>printseeds</b></code></a>
+    = "<i>boolean or filename</i>"
+    (default = false)</dt>
+<dd>List classes and class members matched by the various <code>keep</code>
+    commands, to the standard output or to the given file.</dd>
+<dt><a href="usage.html#dontshrink"><code><b>shrink</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Shrink the input class files.</dd>
+<dt><a href="usage.html#printusage"><code><b>printusage</b></code></a>
+    = "<i>boolean or filename</i>"
+    (default = false)</dt>
+<dd>List dead code of the input class files, to the standard output or to the
+    given file.</dd>
+<dt><a href="usage.html#dontoptimize"><code><b>optimize</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Optimize the input class files.</dd>
+<dt><a href="usage.html#optimizationpasses"><code><b>optimizationpasses</b></code></a>
+    = "<i>n</i>"
+    (default = 1)</dt>
+<dd>The number of optimization passes to be performed.</dd>
+<dt><a href="usage.html#allowaccessmodification"><code><b>allowaccessmodification</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Allow the access modifiers of classes and class members to be modified,
+    while optimizing.</dd>
+<dt><a href="usage.html#mergeinterfacesaggressively"><code><b>mergeinterfacesaggressively</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Allow any interfaces to be merged, while optimizing.</dd>
+<dt><a href="usage.html#dontobfuscate"><code><b>obfuscate</b></code></a>
+    = "<i>boolean</i>"
+   (default = true)</dt>
+<dd>Obfuscate the input class files.</dd>
+<dt><a href="usage.html#printmapping"><code><b>printmapping</b></code></a>
+    = "<i>boolean or filename</i>"
+    (default = false)</dt>
+<dd>Print the mapping from old names to new names for classes and class members
+    that have been renamed, to the standard output or to the given file.</dd>
+<dt><a href="usage.html#applymapping"><code><b>applymapping</b></code></a>
+    = "<i>filename</i>"
+    (default = none)</dt>
+<dd>Reuse the given mapping, for incremental obfuscation.</dd>
+<dt><a href="usage.html#obfuscationdictionary"><code><b>obfuscationdictionary</b></code></a>
+    = "<i>filename</i>"
+    (default = none)</dt>
+<dd>Use the words in the given text file as obfuscated field names and method
+    names.</dd>
+<dt><a href="usage.html#classobfuscationdictionary"><code><b>classobfuscationdictionary</b></code></a>
+    = "<i>filename</i>"
+    (default = none)</dt>
+<dd>Use the words in the given text file as obfuscated class names.</dd>
+<dt><a href="usage.html#packageobfuscationdictionary"><code><b>packageobfuscationdictionary</b></code></a>
+    = "<i>filename</i>"
+    (default = none)</dt>
+<dd>Use the words in the given text file as obfuscated package names.</dd>
+<dt><a href="usage.html#overloadaggressively"><code><b>overloadaggressively</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Apply aggressive overloading while obfuscating.</dd>
+<dt><a href="usage.html#useuniqueclassmembernames"><code><b>useuniqueclassmembernames</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Ensure uniform obfuscated class member names for subsequent incremental
+    obfuscation.</dd>
+<dt><a href="usage.html#dontusemixedcaseclassnames"><code><b>usemixedcaseclassnames</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Generate mixed-case class names while obfuscating.</dd>
+<dt><a href="usage.html#flattenpackagehierarchy"><code><b>flattenpackagehierarchy</b></code></a>
+    = "<i>package_name</i>"
+    (default = none)</dt>
+<dd>Repackage all packages that are renamed into the single given parent
+    package.</dd>
+<dt><a href="usage.html#repackageclasses"><code><b>repackageclasses</b></code></a>
+    = "<i>package_name</i>"
+    (default = none)</dt>
+<dd>Repackage all class files that are renamed into the single given
+    package.</dd>
+<dt><a href="usage.html#keepparameternames"><code><b>keepparameternames</b></code></a>
+    = "<i>boolean</i>"
+   (default = false)</dt>
+<dd>Keep the parameter names and types of methods that are kept.</dd>
+<dt><a href="usage.html#renamesourcefileattribute"><code><b>renamesourcefileattribute</b></code></a>
+    = "<i>string</i>"
+    (default = none)</dt>
+<dd>Put the given constant string in the <code>SourceFile</code>
+    attributes.</dd>
+<dt><a href="usage.html#dontpreverify"><code><b>preverify</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Preverify the processed class files if they are targeted at Java Micro
+    Edition or at Java 6 or higher.</dd>
+<dt><a href="usage.html#microedition"><code><b>microedition</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Targets the processed class files at Java Micro Edition.</dd>
+<dt><a href="usage.html#verbose"><code><b>verbose</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Write out some more information during processing.</dd>
+<dt><a href="usage.html#dontnote"><code><b>note</b></code></a>
+    = "<i>boolean</i>"
+   (default = true)</dt>
+<dd>Print notes about potential mistakes or omissions in the configuration.
+    Use the nested element <a href="#dontnote">dontnote</a> for more
+    fine-grained control.</dd>
+<dt><a href="usage.html#dontwarn"><code><b>warn</b></code></a>
+    = "<i>boolean</i>"
+    (default = true)</dt>
+<dd>Print warnings about unresolved references. Use the nested
+    element <a href="#dontwarn">dontwarn</a> for more fine-grained
+    control. <i>Only use this option if you know what you're doing!</i></dd>
+<dt><a href="usage.html#ignorewarnings"><code><b>ignorewarnings</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Print warnings about unresolved references, but continue processing
+    anyhow. <i>Only use this option if you know what you're doing!</i></dd>
+<dt><a href="usage.html#printconfiguration"><code><b>printconfiguration</b></code></a>
+    = "<i>boolean or filename</i>"
+    (default = false)</dt>
+<dd>Write out the entire configuration in traditional ProGuard style, to the
+    standard output or to the given file. Useful to replace unreadable
+    XML configurations.</dd>
+<dt><a href="usage.html#dump"><code><b>dump</b></code></a>
+    = "<i>boolean or filename</i>"
+    (default = false)</dt>
+<dd>Write out the internal structure of the processed class files, to the
+    standard output or to the given file.</dd>
+<dt><a href="usage.html#injars"><code><b>&lt;injar</b></code></a>
+    <a href="#classpath"><i>class_path</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies the program jars (or wars, ears, zips, or directories).</dd>
+<dt><a href="usage.html#outjars"><code><b>&lt;outjar</b></code></a>
+    <a href="#classpath"><i>class_path</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies the name of the output jars (or wars, ears, zips, or
+    directories).</dd>
+<dt><a href="usage.html#libraryjars"><code><b>&lt;libraryjar</b></code></a>
+    <a href="#classpath"><i>class_path</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies the library jars (or wars, ears, zips, or directories).</dd>
+<dt><a href="usage.html#keepdirectories"><code><b>&lt;keepdirectory name = </b></code></a>"<i>directory_name</i>"
+    <code><b>/&gt;</b></code><br/>
+    <a href="usage.html#keepdirectories"><code><b>&lt;keepdirectories filter = </b></code></a>"<a href="usage.html#filefilters"><i>directory_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Keep the specified directories in the output jars (or wars, ears, zips, or
+    directories).</dd>
+<dt><a href="usage.html#keep"><code><b>&lt;keep</b></code></a>
+    <a href="#keepmodifier"><i>modifiers</i></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keep&gt;</b></code></dt>
+<dd>Preserve the specified classes <i>and</i> class members.</dd>
+<dt><a href="usage.html#keepclassmembers"><code><b>&lt;keepclassmembers</b></code></a>
+    <a href="#keepmodifier"><i>modifiers</i></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keepclassmembers&gt;</b></code></dt>
+<dd>Preserve the specified class members, if their classes are preserved as
+    well.</dd>
+<dt><a href="usage.html#keepclasseswithmembers"><code><b>&lt;keepclasseswithmembers</b></code></a>
+    <a href="#keepmodifier"><i>modifiers</i></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keepclasseswithmembers&gt;</b></code></dt>
+<dd>Preserve the specified classes <i>and</i> class members, if all of the
+    specified class members are present.</dd>
+<dt><a href="usage.html#keepnames"><code><b>&lt;keepnames</b></code></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keepnames&gt;</b></code></dt>
+<dd>Preserve the names of the specified classes <i>and</i> class members (if
+    they aren't removed in the shrinking step).</dd>
+<dt><a href="usage.html#keepclassmembernames"><code><b>&lt;keepclassmembernames</b></code></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keepclassmembernames&gt;</b></code></dt>
+<dd>Preserve the names of the specified class members (if they aren't removed
+    in the shrinking step).</dd>
+<dt><a href="usage.html#keepclasseswithmembernames"><code><b>&lt;keepclasseswithmembernames</b></code></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/keepclasseswithmembernames&gt;</b></code></dt>
+<dd>Preserve the names of the specified classes <i>and</i> class members, if
+    all of the specified class members are present (after the shrinking
+    step).</dd>
+<dt><a href="usage.html#whyareyoukeeping"><code><b>&lt;whyareyoukeeping</b></code></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/whyareyoukeeping&gt;</b></code></dt>
+<dd>Print details on why the given classes and class members are being kept in
+    the shrinking step.</dd>
+<dt><a href="usage.html#assumenosideeffects"><code><b>&lt;assumenosideeffects</b></code></a>
+    <a href="#classspecification"><i>class_specification</i></a>
+    <code><b>&gt;</b></code>
+    <a href="#classmemberspecification"><i>class_member_specifications</i></a>
+    <code><b>&lt;/assumenosideeffects&gt;</b></code></dt>
+<dd>Assume that the specified methods don't have any side effects, while
+    optimizing. <i>Only use this option if you know what you're
+    doing!</i></dd>
+<dt><a href="usage.html#optimizations"><code><b>&lt;optimization name = </b></code></a>"<a href="optimizations.html"><i>optimization_name</i></a>"
+    <code><b>/&gt;</b></code><br/>
+    <a href="usage.html#optimizations"><code><b>&lt;optimizations filter = </b></code></a>""<a href="optimizations.html"><i>optimization_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Perform only the specified optimizations.</dd>
+<dt><a href="usage.html#keeppackagenames"><code><b>&lt;keeppackagename name = </b></code></a>"<i>package_name</i>"
+    <code><b>/&gt;</b></code><br/>
+    <a href="usage.html#keeppackagenames"><code><b>&lt;keeppackagenames filter = </b></code></a>"<a href="usage.html#filters"><i>package_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Keep the specified package names from being obfuscated. If no name is
+    given, all package names are preserved.</dd>
+<dt><a href="usage.html#keepattributes"><code><b>&lt;keepattribute name = </b></code></a>"<i>attribute_name</i>"
+    <code><b>/&gt;</b></code><br/>
+    <a href="usage.html#keepattributes"><code><b>&lt;keepattributes filter = </b></code></a>"<a href="usage.html#filters"><i>attribute_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Preserve the specified optional Java bytecode attributes, with optional
+    wildcards. If no name is given, all attributes are preserved.</dd>
+<dt><a href="usage.html#adaptclassstrings"><code><b>&lt;adaptclassstrings filter = </b></code></a>"<a href="usage.html#filters"><i>class_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Adapt string constants in the specified classes, based on the obfuscated
+    names of any corresponding classes.</dd>
+<dt><a href="usage.html#adaptresourcefilenames"><code><b>&lt;adaptresourcefilenames filter = </b></code></a>"<a href="usage.html#filefilters"><i>file_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Rename the specified resource files, based on the obfuscated names of the
+    corresponding class files.</dd>
+<dt><a href="usage.html#adaptresourcefilecontents"><code><b>&lt;adaptresourcefilecontents filter = </b></code></a>"<a href="usage.html#filefilters"><i>file_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Update the contents of the specified resource files, based on the
+    obfuscated names of the processed classes.</dd>
+<dt><a name="dontnote" />
+    <a href="usage.html#dontnote"><code><b>&lt;dontnote filter = </b></code></a>"<a href="usage.html#filters"><i>class_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Don't print notes about classes matching the specified class name
+    filter.</dd>
+<dt><a name="dontwarn" />
+    <a href="usage.html#dontwarn"><code><b>&lt;dontwarn filter = </b></code></a>"<a href="usage.html#filters"><i>class_filter</i></a>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Don't print warnings about classes matching the specified class name
+    filter. <i>Only use this option if you know what you're doing!</i></dd>
+<dt><a name="configuration_element"><code><b>&lt;configuration refid = </b></code></a>"<i>ref_id</i>"
+    <code><b>/&gt;</b></code></dt>
+<dd>Includes the configuration specified in the
+    <code>&lt;proguardconfiguration&gt;</code> task (or
+    <code>&lt;proguard&gt;</code> task) with the attribute <code>id</code> =
+    "<i>ref_id</i>". Note that only the nested elements of this configuration
+    are considered, not the attributes. Also note: for reading ProGuard-style
+    configuration files, use the <a
+    href="#configuration_attribute"><code>configuration</code></a>
+    <i>attribute</i>.</dd>
+</dl>
+<h2><a name="classpath">Class Path Attributes and Nested Elements</a></h2>
+The jar tags are path tags, so they can have any of the path attributes (or
+nested elements). The most common attributes are:
+<dl>
+<dt><code><b>path</b></code> = "<i>path</i>"</dt>
+<dd>The names of the jars (or wars, ears, zips, or directories), separated by
+    the path separator.</dd>
+<dt><code><b>location</b></code> = "<i>name</i>" (or <code><b>file</b></code>
+    = "<i>name</i>", or <code><b>dir</b></code> = "<i>name</i>", or
+    <code><b>name</b></code> = "<i>name</i>")</dt>
+<dd>Alternatively, the name of a single jar (or war, ear, zip, or
+    directory).</dd>
+<dt><code><b>refid</b></code> = "<i>ref_id</i>"</dt>
+<dd>Alternatively, a reference to the path or file set with the attribute
+    <code>id</code> = "<i>ref_id</i>".</dd>
+</dl>
+In addition, the jar tags can have ProGuard-style filter attributes:
+<dl>
+<dt><code><b>filter</b></code> =
+    "<a href="usage.html#filefilters"><i>file_filter</i></a>"</dt>
+<dd>An optional filter for all class file names and resource file names that
+    are encountered.</dd>
+<dt><code><b>jarfilter</b></code> =
+    "<a href="usage.html#filefilters"><i>file_filter</i></a>"</dt>
+<dd>An optional filter for all jar names that are encountered.</dd>
+<dt><code><b>warfilter</b></code> =
+    "<a href="usage.html#filefilters"><i>file_filter</i></a>"</dt>
+<dd>An optional filter for all war names that are encountered.</dd>
+<dt><code><b>earfilter</b></code> =
+    "<a href="usage.html#filefilters"><i>file_filter</i></a>"</dt>
+<dd>An optional filter for all ear names that are encountered.</dd>
+<dt><code><b>zipfilter</b></code> =
+    "<a href="usage.html#filefilters"><i>file_filter</i></a>"</dt>
+<dd>An optional filter for all zip names that are encountered.</dd>
+</dl>
+<h2><a name="keepmodifier">Keep Modifier Attributes</a></h2>
+The keep tags can have the following <i>modifier</i> attributes:
+<dl>
+<dt><a href="usage.html#allowshrinking"><code><b>allowshrinking</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Specifies whether the entry points specified in the keep tag may be
+    shrunk.</dd>
+<dt><a href="usage.html#allowoptimization"><code><b>allowoptimization</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Specifies whether the entry points specified in the keep tag may be
+    optimized.</dd>
+<dt><a href="usage.html#allowobfuscation"><code><b>allowobfuscation</b></code></a>
+    = "<i>boolean</i>"
+    (default = false)</dt>
+<dd>Specifies whether the entry points specified in the keep tag may be
+    obfuscated.</dd>
+</dl>
+<h2><a name="classspecification">Class Specification Attributes and Nested Elements</a></h2>
+The keep tags can have the following <i>class_specification</i> attributes and
+<i>class_member_specifications</i> nested elements:
+<dl>
+<dt><code><b>access</b></code> = "<i>access_modifiers</i>"</dt>
+<dd>The optional access modifiers of the class. Any space-separated list of
+    "public", "final", and "abstract", with optional negators "!".</dd>
+<dt><code><b>annotation</b></code> = "<i>annotation_name</i>"</dt>
+<dd>The optional fully qualified name of an annotation of the class, with
+    optional wildcards.</dd>
+<dt><code><b>type</b></code> = "<i>type</i>"</dt>
+<dd>The optional type of the class: one of "class", "interface", or
+    "!interface".</dd>
+<dt><code><b>name</b></code> = "<i>class_name</i>"</dt>
+<dd>The optional fully qualified name of the class, with optional
+    wildcards.</dd>
+<dt><code><b>extendsannotation</b></code> = "<i>annotation_name</i>"</dt>
+<dd>The optional fully qualified name of an annotation of the the class that
+    the specified classes must extend, with optional wildcards.</dd>
+<dt><code><b>extends</b></code> = "<i>class_name</i>"</dt>
+<dd>The optional fully qualified name of the class the specified classes
+    must extend, with optional wildcards.</dd>
+<dt><code><b>implements</b></code> = "<i>class_name</i>"</dt>
+<dd>The optional fully qualified name of the class the specified classes
+    must implement, with optional wildcards.</dd>
+<dt><code><b>&lt;field</b></code>
+    <a href="#classmemberspecification"><i>class_member_specification</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies a field.</dd>
+<dt><code><b>&lt;method</b></code>
+    <a href="#classmemberspecification"><i>class_member_specification</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies a method.</dd>
+<dt><code><b>&lt;constructor</b></code>
+    <a href="#classmemberspecification"><i>class_member_specification</i></a>
+    <code><b>/&gt;</b></code></dt>
+<dd>Specifies a constructor.</dd>
+</dl>
+<h2><a name="classmemberspecification">Class Member Specification Attributes</a></h2>
+The class member tags can have the following <i>class_member_specification</i>
+attributes:
+<dl>
+<dt><code><b>access</b></code> = "<i>access_modifiers</i>"</dt>
+<dd>The optional access modifiers of the class. Any space-separated list of
+    "public", "protected", "private", "static", etc., with optional negators
+    "!".</dd>
+<dt><code><b>annotation</b></code> = "<i>annotation_name</i>"</dt>
+<dd>The optional fully qualified name of an annotation of the class member,
+    with optional wildcards.</dd>
+<dt><code><b>type</b></code> = "<i>type</i>"</dt>
+<dd>The optional fully qualified type of the class member, with optional
+    wildcards. Not applicable for constructors, but required for methods for
+    which the <code>parameters</code> attribute is specified.</dd>
+<dt><code><b>name</b></code> = "<i>name</i>"</dt>
+<dd>The optional name of the class member, with optional wildcards. Not
+    applicable for constructors.</dd>
+<dt><code><b>parameters</b></code> = "<i>parameters</i>"</dt>
+<dd>The optional comma-separated list of fully qualified method parameters,
+    with optional wildcards. Not applicable for fields, but required for
+    constructors, and for methods for which the <code>type</code> attribute is
+    specified.</dd>
+</dl>
+<hr />
+<noscript><div><a target="_top" href="../index.html" class="button">Show menu</a></div></noscript>
+<address>
+Copyright &copy; 2002-2011
+<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
+</address>
+</body>
+</html>