解決spring-security4.2.7 maven 報錯invalid LOC header(bad signature)
八月 08, 2018 11:42:52 上午 org.apache.catalina.startup.ContextConfig processAnnotationsJar
嚴重: Unable to process Jar entry [org/springframework/security/access/expression/method/PreInvocationExpressionAttribute.class] from Jar [jar:file:/C:/Users/Administrator/.m2/repository/org/springframework/security/spring-security-core/4.2 .7.RELEASE/spring-security-core-4.2.7.RELEASE.jar!/] for annotations
java.util.zip.ZipException: invalid LOC header (bad signature)
at java.util.zip.ZipFile.read(Native Method)
at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717 )
at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
at java.io .DataInputStream.readInt(DataInputStream.java:387)
at org.apache.tomcat.util.bcel.classfile.ClassParser.readID(ClassParser.java:237)
at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:114)
at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2134)
at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:2010)
at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1976)
at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1961)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1319)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:376)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
maven引入
<!--Spring-->
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-orm</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-web</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-webmvc</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-tx</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-test</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-jdbc</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-mock</artifactId>
<version>2.0.8</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-expression</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context-support</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<!-- Spring Security -->
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-web</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-core</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-config</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-taglibs</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-cas</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-acl</artifactId>
<version>4.2.7.RELEASE</version>
</dependency>
解決,最後發現是版本問題,切換到4.2.2版本就沒問題了
相關推薦
解決spring-security4.2.7 maven 報錯invalid LOC header(bad signature)
八月 08, 2018 11:42:52 上午 org.apache.catalina.startup.ContextConfig processAnnotationsJar 嚴重: Unable to process Jar entry [org/spring
maven 報錯invalid LOC header(bad signature)
在命令列中執行mvn package的時候報錯如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile)
【Maven】工程啟動報錯 invalid LOC header (bad signature)
錯誤日誌: 嚴重: A child container failed during start java.util.concu
啟動專案報錯:invalid LOC header (bad signature)
我試了網上的方法,先用 mvn test -X測試 執行的兩種方法: 1、在Eclipse中 run as => maven build
使用eclipse對maven項目打包時,報 invalid LOC header (bad signature)異常處理
http switch ati exception ogg 異常處理 name .org and 在eclipse上打包,報錯: [INFO] Including org.codehaus.groovy:groovy-all:jar:2.4.3 in the shade
執行maven專案遇到java.util.zip.ZipException: invalid LOC header (bad signature)高效解決辦法
事情是這樣的,本來我的本地maven倉庫是放在C盤的,而C盤是固態硬碟,而且隨著時間推移,本地maven倉庫變得越來越大,所以就想在本地E盤裡再建立一個本地倉庫,本來以為是很簡單的事情,配置一下就完事的。沒想到把自己的小 demo 放到 tomcat 上跑還報了這個錯誤,真實
運行Maven項目時出現invalid LOC header (bad signature)
spa article popu stand details 必須 standard eset org 為Maven小白,今天這問題困擾了我好久,經過多次在網上查詢,終於找到了原因。明明一個小問題卻耗費很多時間,著實不應該,所以必須記錄一下。 報錯信息如下: 對話框
invalid LOC header (bad signature)-Maven異常
異常異常信息: 錯誤: 讀取D:\dev-tool\maven-repository\org\springframework\boot\spring-boot\1.4.2.RELEASE\spring-boot-1.4.2.RELEASE.jar時出錯; invalid LOC header (bad si
運行Maven項目時出現invalid LOC header (bad signature)錯誤,Tomcat不能正常啟動
argument 不能 sig 嚴重 對話 toc cau ebr tom 作為Maven小白,今天這問題困擾了我好久,經過多次在網上查詢,終於找到了原因。明明一個小問題卻耗費很多時間,著實不應該,所以必須記錄一下。 報錯信息如下: 對話框: 控制臺:
maven 錯誤:讀取 xxx.jar 時出錯;invalid LOC header (bad signature) 1 錯誤
reqHeader:{Accept=text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8, Upgrade-Insecure-Requests=1, Connection=keep-alive, User-Agen
Maven-invalid LOC header (bad signature)
用maven打包的war部署到tomcat中啟動報錯 Caused by: java.util.zip.ZipException: invalid block type at java.util.zip.InflaterInputStream.read(InflaterI
invalid LOC header (bad signature) 錯誤解決辦法
錯誤情況 maven工程時,一直提示junit錯誤,仔細檢視,發現有junit包,但是仍然沒起作用,pom.xml加上了版本資訊,還是不行,感覺為包錯誤,瀏覽包類,開啟提示 “invalid LOC header (bad signature)”,感覺下載的junit包出問題。 解決
Spring boot 2.0 配置報錯java.lang.NoClassDefFoundError: org/springframework/boot/bind/RelaxedPropertyRes
springboot2.0使用的druid版本過低 org.springframework.boot.bind 包已經刪掉了,導致RelaxedPropertyResolver這個方法已經不可用了. API中寫到,不再可用了,因為環境會自動處理,去找到這個配置檔案 改為
spring 3.2+mybatis 整合報錯問題
2015-7-17 17:44:09 org.springframework.context.support.AbstractApplicationContext prepareRefresh 資訊: Refreshing org[email protected]
pyspark報錯: invalid stream header
當我對rdd進行map操作的時候,就是新增一個欄位,表示其中的兩個欄位是否相等,然後報這個錯誤。 Google後也沒找到確切的解決方案,因為是用python程式設計,對java不熟悉,估計是java物件讀寫資料的時候發生的問題
vue-cli將127.0.0.1只指向www.***.com 報錯Invalid Host header
在window系統下 C:\Windows\System32\drivers\etc 修改hosts檔案 將127.0.0.1指向了一個域名 然後執行得時候就報了一個錯誤Invalid Host header 出現這個得原因是因為新版的webpack-dev-server出於安全考慮
[轉]JSTL 自定義方法報錯Invalid syntax for function signature in TLD.
Apache Tomcat/6.0.18 ${my:splitApply(apply)} <function> <name>splitApply</name> <function-class>org.darkness.oa.web.UtilFunction<
angular-cli6使用ng serve --o 控制臺報錯Invalid Host Header
font image src devkit 控制 cli 項目 .com nod angular-cli6使用ng serve --o 運行創建的項目,能正常訪問,但是控制臺一直在報錯,點擊報錯能看到是因為webpack的webpack-dev-server裏報的錯, 看
解決了異常java.util.zip.ZipException: invalid CEN header (bad signature)心路歷程
前言 過完年來,我被安排做一個比較小的查詢功能增加到先有的.net系統中,其實就是增加個二級選單,點選選單之後輸入賬號可以從資料庫查詢到相關的資訊。正常來說,這個小功能一個下午不到就可以完成,但是因為涉及到一些很小的細節問題不能及時解決,所以花了我幾天的時間,我都開始崩潰和懷疑人生了。所
centos7.2編譯安裝mysql5.7.21報錯解決
initial mem ext ava gin onf 改密 依賴 document 編譯安裝mysql 安裝環境安裝包[root@ecs-adfa ~]# ls /root/tools/app.tar.gz mysql-5.7.21 mysql-5.7.21.tar.