SpringBoot?+?proguard+maven多模塊實(shí)現(xiàn)代碼混淆的方法
上文介紹了單個(gè)springboot的maven工程實(shí)現(xiàn)代碼混淆,本文將會(huì)介紹多maven工程實(shí)現(xiàn)代碼混淆。
多模塊跟單模塊一樣,在需要混淆模塊的pom文件中加入proguard依賴(lài)及配置。
演練版本
springboot:2.5.8
jdk:1.8
proguard: 7.1.0
新建springboot多Maven工程
新建springboot多maven工程,結(jié)構(gòu)如下圖,proguard-root 是頂級(jí)父工程,proguard-modu01、proguard-mudu02是兩個(gè)業(yè)務(wù)模塊,proguard-server是springboot啟動(dòng)服務(wù)類(lèi)模塊。
接下來(lái)會(huì)對(duì)proguard-modu01、proguard-mudu02兩個(gè)模塊實(shí)現(xiàn)proguard代碼混淆。

下面以proguard-modu01工程為例介紹。
proguard-modu01 工程結(jié)構(gòu)

proguard-modu01 的pom.xml配置代碼混淆
本次我將proguard配置項(xiàng)放入 <options> </options>內(nèi),也可以單獨(dú)配置在proguard.cfg文件內(nèi)。
特別注意避坑:多maven工程代碼混淆一定要配置:<option>-keepdirectories</option>,否則在以后訪問(wèn)代碼混淆子模塊的controller時(shí)會(huì)提示404錯(cuò)誤。
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.proguard</groupId>
<artifactId>proguard-root</artifactId>
<version>1.0</version>
</parent>
<artifactId>proguard-modu02</artifactId>
<dependencies>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<scope>runtime</scope>
<optional>true</optional>
</dependency>
</dependencies>
<!-- 配置代碼混淆 開(kāi)始-->
<build>
<plugins>
<plugin>
<groupId>com.github.wvengen</groupId>
<artifactId>proguard-maven-plugin</artifactId>
<version>2.6.0</version>
<executions>
<!-- 以下配置說(shuō)明執(zhí)行mvn的package命令時(shí)候,會(huì)執(zhí)行proguard-->
<execution>
<phase>package</phase>
<goals>
<goal>proguard</goal>
</goals>
</execution>
</executions>
<configuration>
<proguardVersion>7.1.0</proguardVersion>
<!-- 原始jar -->
<injar>${project.build.finalName}.jar</injar>
<!-- 混淆后的jar -->
<outjar>${project.build.finalName}.jar</outjar>
<!-- 是否混淆 默認(rèn)是true -->
<obfuscate>true</obfuscate>
<!-- 是否將生成的PG文件安裝部署 -->
<!-- <attach>true</attach> -->
<!--指定生成文件分類(lèi)-->
<!--<attachArtifactClassifier>pg</attachArtifactClassifier>-->
<!-- 將pom.xml打包至jar文件中 -->
<addMavenDescriptor>true</addMavenDescriptor>
<!-- 混淆配置文件proguard.cfg
<proguardInclude>${project.basedir}/proguard.cfg</proguardInclude>-->
<!-- 項(xiàng)目編譯所需要的jar -->
<libs>
<lib>${java.home}/lib/rt.jar</lib>
</libs>
<!-- 對(duì)輸入jar進(jìn)行過(guò)濾比如,如下配置就是對(duì)META-INFO文件不處理。
<inLibsFilter>!META-INF/**,!META-INF/versions/9/**.class</inLibsFilter>-->
<!-- 輸出路徑配置,但是要注意這個(gè)路徑必須要包括injar標(biāo)簽填寫(xiě)的jar -->
<outputDirectory>${project.basedir}/target</outputDirectory>
<!--配置混淆的一些細(xì)節(jié)選項(xiàng),可在proguard.cfg中配置-->
<options>
<!-- JDK目標(biāo)版本1.8-->
<option>-target 1.8</option>
<!-- 不做收縮(刪除注釋、未被引用代碼)-->
<option>-dontshrink</option>
<!-- 不做優(yōu)化(變更代碼實(shí)現(xiàn)邏輯)-->
<option>-dontoptimize</option>
<!-- 不混忽略非公用類(lèi)文件及成員-->
<option>-dontskipnonpubliclibraryclasses</option>
<option>-dontskipnonpubliclibraryclassmembers</option>
<!--不用大小寫(xiě)混合類(lèi)名機(jī)制-->
<option>-dontusemixedcaseclassnames</option>
<!-- 優(yōu)化時(shí)允許訪問(wèn)并修改有修飾符的類(lèi)和類(lèi)的成員 -->
<option>-allowaccessmodification</option>
<!-- 確定統(tǒng)一的混淆類(lèi)的成員名稱(chēng)來(lái)增加混淆-->
<option>-useuniqueclassmembernames</option>
<!-- 保持目錄結(jié)構(gòu)-->
<option>-keepdirectories</option>
<!-- 不混淆所有包名-->
<!--<option>-keeppackagenames</option>-->
<!-- 混淆類(lèi)名之后,對(duì)使用Class.forName('className')之類(lèi)的地方進(jìn)行相應(yīng)替代-->
<option>-adaptclassstrings</option>
<!-- 需要保持的屬性:異常,注解等-->
<option>-keepattributes Exceptions,InnerClasses,Signature,Deprecated,SourceFile,LocalVariable*Table,*Annotation*,Synthetic,EnclosingMethod</option>
<!-- 此選項(xiàng)將保存所有軟件包中的所有原始接口文件(不進(jìn)行混淆) -->
<option>-keepnames interface ** { *; }</option>
<!-- 此選項(xiàng)將保存所有軟件包中的所有原始接口文件(不進(jìn)行混淆) -->
<option>-keep interface * extends * { *; }</option>
<!-- 保留參數(shù)名,因?yàn)榭刂破?,或者M(jìn)ybatis等接口的參數(shù)如果混淆會(huì)導(dǎo)致無(wú)法接受參數(shù),xml文件找不到參數(shù) -->
<option>-keepparameternames</option>
<!-- 保留枚舉成員及方法 -->
<option>-keepclassmembers enum * { *; }</option>
<!-- 不混淆所有類(lèi),保存原始定義的注釋 -->
<option>
-keepclassmembers class * {
@org.springframework.context.annotation.Bean *;
@org.springframework.beans.factory.annotation.Autowired *;
@org.springframework.beans.factory.annotation.Value *;
@org.springframework.stereotype.Service *;
@org.springframework.stereotype.Component *;
@org.springframework.web.bind.annotation.RestController *;
}
</option>
<!-- 忽略warn消息 -->
<option>-ignorewarnings</option> -->
<!-- 忽略note消息 -->
<option>-dontnote</option> -->
<!-- 打印配置信息 -->
<option>-printconfiguration</option>
<!-- 不混淆controller入口類(lèi)
<option>-keep class com.platform.scamp.entity.** {*;}</option>
<option>-keep class com.platform.scamp.service.ScampVehicleTrackService {*;}</option>
<option>-keep class com.platform.scamp.controller.** {*;}</option>-->
</options>
<injarNotExistsSkip>true</injarNotExistsSkip>
<!-- 把jar包放到臨時(shí)目錄以便縮短命令行 -->
<putLibraryJarsInTempDir>true</putLibraryJarsInTempDir>
</configuration>
<dependencies>
<dependency>
<groupId>com.guardsquare</groupId>
<artifactId>proguard-base</artifactId>
<version>7.1.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>com.guardsquare</groupId>
<artifactId>proguard-core</artifactId>
<version>7.1.0</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
<!-- 配置代碼混淆 結(jié)束-->
</project>此時(shí),已完成proguard-modu01模塊的代碼混淆配置,proguard-modu02模塊同上配置即可。
proguard-server 啟動(dòng)服務(wù)模塊的啟動(dòng)類(lèi)配置
由于代碼混淆,會(huì)存在大量的類(lèi)名重名問(wèn)題,因此需要在springboot啟動(dòng)類(lèi)中修改 BeanName 生成策略。
方式一:
package com.proguard;
import org.springframework.beans.factory.config.BeanDefinition;
import org.springframework.beans.factory.support.BeanDefinitionRegistry;
import org.springframework.beans.factory.support.BeanNameGenerator;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.builder.SpringApplicationBuilder;
@SpringBootApplication
public class ProguardServerApplication {
public static class CustomGenerator implements BeanNameGenerator {
public String generateBeanName(BeanDefinition definition, BeanDefinitionRegistry registry) {
return definition.getBeanClassName();
}
}
public static void main(String[] args) {
new SpringApplicationBuilder(ProguardServerApplication.class)
.beanNameGenerator(new CustomGenerator())
.run(args);
}
}方式二:若是maven工程師引用了springfox-boot-starter組件、springfox-*.jar相關(guān)組件,會(huì)產(chǎn)生異常,重寫(xiě)springboot啟動(dòng)類(lèi),如下:
@SpringBootApplication
public class ProguardServerApplication {
public static void main(String[] args) {
new SpringApplicationBuilder(ProguardServerApplication .class)
.beanNameGenerator(new ProGuardBeanNameGenerator()).run();
}
/**
* 代碼混淆后,包名、類(lèi)名會(huì)存在重復(fù),重寫(xiě)buildDefaultBeanName方法,獲取全限定的類(lèi)名
*/
static class ProGuardBeanNameGenerator extends AnnotationBeanNameGenerator {
@Override
protected String buildDefaultBeanName(BeanDefinition definition) {
return definition.getBeanClassName();
}
}
}啟動(dòng),驗(yàn)證
通過(guò)Java反編譯工具 查看源代碼結(jié)果如下圖,包名、類(lèi)名已經(jīng)重新命名,代表代碼混淆已生效。
proguard-modu01:

proguard-modu02:

啟動(dòng)訪問(wèn)
訪問(wèn)proguard-modu01中接口:

訪問(wèn)proguard-modu02中接口:

踩過(guò)坑
1. proguard-modu01、proguard-modu02配置混淆后,訪問(wèn)接口提示404。去掉代碼混淆恢復(fù)正常訪問(wèn)。

解決:在proguard-modu01、proguard-modu02的pom.xml文件中配置保持目錄結(jié)構(gòu):<option>-keepdirectories</option>
2. 若是maven工程師引用了springfox-boot-starter組件、springfox-*.jar相關(guān)組件,會(huì)產(chǎn)生異常。
2023-06-05 17:07:38.322[0;39m [31mERROR[0;39m [35m19088[0;39m [2m---[0;39m [2m[ restartedMain][0;39m [36mo.s.boot.SpringApplication [0;39m [2m:[0;39m Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.spring.web.scanners.ApiDocumentationScanner' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-spring-web/3.0.0/springfox-spring-web-3.0.0.jar!/springfox/documentation/spring/web/scanners/ApiDocumentationScanner.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.spring.web.scanners.ApiListingScanner' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-spring-web/3.0.0/springfox-spring-web-3.0.0.jar!/springfox/documentation/spring/web/scanners/ApiListingScanner.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.spring.web.scanners.ApiModelReader' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-spring-web/3.0.0/springfox-spring-web-3.0.0.jar!/springfox/documentation/spring/web/scanners/ApiModelReader.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.schema.CachingModelProvider' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-schema/3.0.0/springfox-schema-3.0.0.jar!/springfox/documentation/schema/CachingModelProvider.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.schema.DefaultModelProvider' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-schema/3.0.0/springfox-schema-3.0.0.jar!/springfox/documentation/schema/DefaultModelProvider.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'springfox.documentation.schema.property.CachingModelPropertiesProvider' defined in URL [jar:file:/D:/maven/maven-repository/io/springfox/springfox-schema/3.0.0/springfox-schema-3.0.0.jar!/springfox/documentation/schema/property/CachingModelPropertiesProvider.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'springfox.documentation.schema.property.ModelPropertiesProvider' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=optimized)}
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:800) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:229) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1372) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1222) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953) ~[spring-beans-5.3.14.jar:5.3.14]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918) ~[spring-context-5.3.14.jar:5.3.14]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) ~[spring-context-5.3.14.jar:5.3.14]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[spring-boot-2.5.8.jar:2.5.8]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:765) ~[spring-boot-2.5.8.jar:2.5.8]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:445) ~[spring-boot-2.5.8.jar:2.5.8]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:338) ~[spring-boot-2.5.8.jar:2.5.8]
at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:143) [spring-boot-2.5.8.jar:2.5.8]
at com.proguard.ProguardServerApplication.main(ProguardServerApplication.java:22) [classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_192]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_192]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_192]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_192]
at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49) [spring-boot-devtools-2.5.8.jar:2.5.8]
解決方式:重寫(xiě)springboot啟動(dòng)類(lèi)
@SpringBootApplication
public class ProguardServerApplication {
public static void main(String[] args) {
new SpringApplicationBuilder(ProguardServerApplication .class)
.beanNameGenerator(new ProGuardBeanNameGenerator()).run();
}
/**
* 代碼混淆后,包名、類(lèi)名會(huì)存在重復(fù),重寫(xiě)buildDefaultBeanName方法,獲取全限定的類(lèi)名
*/
static class ProGuardBeanNameGenerator extends AnnotationBeanNameGenerator {
@Override
protected String buildDefaultBeanName(BeanDefinition definition) {
return definition.getBeanClassName();
}
}
}到此這篇關(guān)于SpringBoot + proguard+maven多模塊實(shí)現(xiàn)代碼混淆的文章就介紹到這了,更多相關(guān)SpringBoot maven多模塊代碼混淆內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
Java Thread之Sleep()使用方法及總結(jié)
這篇文章主要介紹了Java Thread之Sleep()使用方法及總結(jié),具有很好的參考價(jià)值,希望對(duì)大家有所幫助。如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2022-11-11
java、springboot?接口導(dǎo)出txt方式
這篇文章主要介紹了java、springboot?接口導(dǎo)出txt方式,具有很好的參考價(jià)值,希望對(duì)大家有所幫助。如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2022-01-01
SpringBoot?項(xiàng)目的創(chuàng)建與啟動(dòng)步驟詳解
這篇文章主要介紹了SpringBoot?項(xiàng)目的創(chuàng)建與啟動(dòng),本文分步驟給大家介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或工作具有一定的參考借鑒價(jià)值,需要的朋友可以參考下2023-03-03
Springboot基于BCrypt非對(duì)稱(chēng)加密字符串的實(shí)現(xiàn)
本文主要介紹了Springboot基于BCrypt非對(duì)稱(chēng)加密字符串的實(shí)現(xiàn),文中通過(guò)示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧2023-04-04
Java程序進(jìn)程起來(lái)了但是不打印日志的原因分析
這篇文章主要介紹了Java程序進(jìn)程起來(lái)了但是不打印日志的原因分析,具有很好的參考價(jià)值,希望對(duì)大家有所幫助,如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2025-04-04
Java開(kāi)發(fā)神器Lombok安裝與使用詳解
Lombok的安裝分兩部分:Idea插件的安裝和maven中pom文件的導(dǎo)入,本文重點(diǎn)給大家介紹Java開(kāi)發(fā)神器Lombok安裝與使用詳解,感興趣的朋友跟隨小編一起看看吧2022-02-02
SpringBoot整合ip2region獲取客戶(hù)端IP地理位置信息
在我們?nèi)粘EB開(kāi)發(fā)工作中,經(jīng)常會(huì)有需要獲取客戶(hù)端地理位置的需求,本文主要介紹了SpringBoot整合ip2region獲取客戶(hù)端IP地理位置信息,具有一定的參考價(jià)值,感興趣的可以了解一下2024-08-08
Mybatis-Plus的應(yīng)用場(chǎng)景描述及注入SQL原理分析
MyBatis-Plus是一個(gè) MyBatis 的增強(qiáng)工具,在 MyBatis 的基礎(chǔ)上只做增強(qiáng)不做改變,為簡(jiǎn)化開(kāi)發(fā)、提高效率而生,本文重點(diǎn)給大家介紹Mybatis-Plus的應(yīng)用場(chǎng)景及注入SQL原理分析,感興趣的朋友跟隨小編一起學(xué)習(xí)吧2021-05-05

