为了让 Proguard 与 Java 11 一起工作,我们需要:
最新的 Proguard beta 版本,在这种情况下适用于 Gradle。
修改构建 gradle 文件以包含 proguard 任务。
添加一个 proguard 配置文件,包括 Java 11 所需的更改。
构建.gradle
从 HelloFX示例开始,构建将被修改为:
// 1. Include proguard dependency
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'net.sf.proguard:proguard-gradle:6.1.0beta2'
}
}
plugins {
id 'application'
id 'org.openjfx.javafxplugin' version '0.0.7'
}
repositories {
mavenCentral()
}
dependencies {
}
javafx {
modules = [ 'javafx.controls', 'javafx.fxml' ]
}
mainClassName = 'org.openjfx.MainApp'
除了添加 proguard 任务之外,我将添加更多任务来用 proguarded 替换默认构建/类。这有助于检查结果。
// 2. Add tasks
// 2.1 Clean buildDir before running proguard
task cleanClasses(type: Delete) {
delete "${buildDir}/classes/java/main"
delete "${buildDir}/resources/java/main"
}
classes.dependsOn(cleanClasses)
// 2.2 Add proguard task
task proguard(type: proguard.gradle.ProGuardTask, dependsOn: classes) {
injars project.sourceSets.main.output
outjars "${buildDir}/proguard/output.jar"
libraryjars project.sourceSets.main.compileClasspath
configuration 'proguard.conf'
}
// 2.3 Clean after proguard task
task cleanAfterProguard(type: Delete, dependsOn: proguard) {
delete "${buildDir}/classes/java/main"
delete "${buildDir}/resources/java/main"
}
// 2.4 Extract output jar to buildDir
task unpackProguardOutput (type: Copy, dependsOn: cleanAfterProguard) {
from zipTree("${buildDir}/proguard/output.jar")
into file("${buildDir}/classes/java/main")
}
最后,添加一个任务来运行带有保护类的应用程序。
// 3. Create a task to run the app with the proguarded buildDir
task runProguard(type: JavaExec, dependsOn: unpackProguardOutput) {
classpath = sourceSets.main.runtimeClasspath
jvmArgs = ['--module-path', classpath.asPath,
'--add-modules', 'javafx.controls,javafx.fxml' ]
main = 'a.a.b' // <-- this name will depend on the proguard result
}
proguard.conf
可以在此评论中找到如何使其与 Java 9+ 一起使用的关键。如果您下载源代码,并检查示例文件夹,则有不同的配置文件。
检查applications.pro
,您可以阅读:
# Before Java 9, the runtime classes were packaged in a single jar file.
#-libraryjars <java.home>/lib/rt.jar
# As of Java 9, the runtime classes are packaged in modular jmod files.
-libraryjars <java.home>/jmods/java.base.jmod(!**.jar;!module-info.class)
就是这样了!
这是我在 HelloFX 示例中使用的配置文件(当然它可以使用其他许多选项进行扩展):
-dontoptimize
-dontshrink
#Java 9+
-libraryjars <java.home>/jmods/java.base.jmod(!**.jar;!module-info.class)
# Save meta-data for stack traces
-printmapping out.map
-renamesourcefileattribute SourceFile
-keepattributes SourceFile,LineNumberTable
# Rename FXML files together with related views
-adaptresourcefilenames **.fxml,**.png,**.css,**.properties
-adaptresourcefilecontents **.fxml
-adaptclassstrings
# Keep all annotations and meta-data
-keepattributes *Annotation*,Signature,EnclosingMethod
# Keep entry-point class
-keep class org.openfjx.MainApp {
public static void main(java.lang.String[]);
}
# Keep names of fields marked with @FXML, @Inject and @PostConstruct attributes
-keepclassmembers class * {
@javafx.fxml.FXML *;
@javax.inject.Inject *;
@javax.annotation.PostConstruct *;
}
结果
如果你跑./gradlew proguard
,你会得到output.jar
。
如果你运行./gradlew unpackProguardOutput
,你可以看到结果build/classes
:
main
|____a
| |____a
| | |____styles.css
| | |____scene.fxml
| | |____b.class
| | |____a.class
在这种情况下,b.class
是主类,所以这就是为什么在runProguard
我设置的任务中main = 'a.a.b'
。显然,这将取决于每种情况。
此外,您可以查看 out.map:
org.openjfx.FXMLController -> a.a.a:
javafx.scene.control.Label label -> label
10:10:void <init>() -> <init>
17:20:void initialize(java.net.URL,java.util.ResourceBundle) -> initialize
org.openjfx.MainApp -> a.a.b:
11:11:void <init>() -> <init>
15:23:void start(javafx.stage.Stage) -> start
26:27:void main(java.lang.String[]) -> a
最后,./gradlew runProguard
将成功运行应用程序。