You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** <<<libs>>> JVM libraries usually not in dependency list
20
20
@@ -25,19 +25,19 @@ proguard-maven-plugin
25
25
</libs>
26
26
---
27
27
28
-
** You can use <<<inFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry Filters}} to input jar
28
+
** You can use <<<inFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry filters}} to input jar
** You can use <<<inLibsFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry Filters}} to all input lib jars
34
+
** You can use <<<inLibsFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry filters}} to all input lib jars
** You can use <<<outFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry Filters}} to output jar
40
+
** You can use <<<outFilter>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry filters}} to output jar
41
41
42
42
---
43
43
<outFilter>!**ECLIPSEF.*</outFilter>
@@ -58,10 +58,10 @@ proguard-maven-plugin
58
58
---
59
59
60
60
** <<<assembly>>> allows to bundle project dependency to resulting jar with different options e.g. -injars ProGuard args.
61
-
Some flagged as <<<library>>> doesn`t need to be processed by ProGuard are added as -libraryjars and added to resulting jar by plugin after ProGuard is finished.
61
+
Some flagged as <<<library>>> doesn't need to be processed by ProGuard are added as -libraryjars and added to resulting jar by plugin after ProGuard is finished.
62
62
For clarity param <<<includeDependency>>> will just add -libraryjars arg to ProGuard and Dependency is not included in resulting jar.
63
63
64
-
You can use <<<assembly>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry Filters}} to dependency jars
64
+
You can use <<<assembly>>> to apply ProGuard {{{https://www.guardsquare.com/manual/configuration/usage#filters}classpathentry filters}} to dependency jars:
65
65
66
66
---
67
67
<assembly>
@@ -72,7 +72,7 @@ proguard-maven-plugin
72
72
<!-- filter will not apply -->
73
73
</inclusion>
74
74
<inclusion>
75
-
<!-- filter out some classes see ProGuard classpathentry Filters -->
75
+
<!-- filter out some classes see ProGuard classpathentry filters -->
* <<<-printmapping>>> is based on the <<<mappingFileName>>> set in the configuration, defaults to '${project.build.directory}/<\<mappingFileName\>>', while <<<-printseeds>>> is based on <<<seedFileName>>> and defaults to '${project.build.directory}/<\<seedFileName\>>'
116
+
* <<<-printmapping>>> is based on the <<<mappingFileName>>> set in the configuration, defaults to '$\{project.build.directory\}/<\<mappingFileName\>>', while <<<-printseeds>>> is based on <<<seedFileName>>> and defaults to '$\{project.build.directory\}/<\<seedFileName\>>'
117
117
118
118
[]
119
119
120
-
Additional ProGuard configuration can be added using {{{proguard-mojo.html#options}options}} or {{{proguard-mojo.html#proguardInclude}proguardInclude}}
120
+
Additional ProGuard configuration can be added using {{{./proguard-mojo.html#options}options}} or {{{./proguard-mojo.html#proguardInclude}proguardInclude}}
121
121
122
122
123
123
** Command line length workaround
124
124
125
-
If you have a huge list of dependencies the list of <<<-libraryjars>>> the resulting command line to execute ProGaurd could become too long. On Windows the error message could look like <<<CreateProcess error=206, The filename or extension is too long>>>.
125
+
If you have a huge list of dependencies the list of <<<-libraryjars>>> the resulting command line to execute ProGuard could become too long. On Windows the error message could look like <<<CreateProcess error=206, The filename or extension is too long>>>.
126
126
127
127
* <<< <generateTemporaryConfigurationFile>true</generateTemporaryConfigurationFile> >>> makes the plugin pass the configuration by a temporary file instead of over the command line. Build performance should not be impacted by this.
128
128
129
129
130
130
* Usage
131
131
132
-
Replace project artifact with obfuscated one. Original jar would be preserved in file project.build.finalName.jar_proguard_base.jar
132
+
Replace project artifact with obfuscated one. Original jar would be preserved in file '<\<artifact-name\>>_proguard_base.jar'.
133
133
134
134
---
135
135
<build>
@@ -157,7 +157,7 @@ proguard-maven-plugin
157
157
</build>
158
158
---
159
159
160
-
Create new file ${project.build.finalName}-small.jar
160
+
Create new file '$\{project.build.finalName\}-small.jar':
161
161
162
162
---
163
163
<build>
@@ -187,7 +187,7 @@ proguard-maven-plugin
187
187
</build>
188
188
---
189
189
190
-
Complex Applet creation example. See full {{{http://www.microemu.org/}MicroEmulator}} project sources for more details
190
+
Complex Applet creation example. See full {{{http://www.microemu.org/}MicroEmulator}} project sources for more details.
191
191
192
192
---
193
193
@@ -261,7 +261,7 @@ proguard-maven-plugin
261
261
</build>
262
262
---
263
263
264
-
Use different version of {{{https://www.guardsquare.com/proguard}ProGuard}}
264
+
Use different version of {{{https://www.guardsquare.com/proguard}ProGuard}}:
0 commit comments