Problem
I faced the same issue. It was due to maven 3.6.3 being incompatible with jdk17.
Sadly I couldn’t update to 3.8.3 via the Ubuntu package manager so I installed it manually.
Steps to install on ubuntu are below:
Solution
Requirements
Maven 3.3+ requires JDK 1.7 or above to be installed.
(Might be obsolete, hence you encountered this problem because you used a too novel JDK)
Step-by-step
Download Apache Maven. I installed 3.8.4, you can check for the newest version here: https://maven.apache.org/download.cgi
We save the archive to /tmp
$ TMP_MAVEN_VERSION=3.8.4
$ wget https://apache.org/dist/maven/maven-3/$TMP_MAVEN_VERSION/binaries/apache-maven-$TMP_MAVEN_VERSION-bin.tar.gz -P /tmp
Then unzip it to /opt
and remove the archive
$ sudo tar xf /tmp/apache-maven-*.tar.gz -C /opt
$ sudo rm /tmp/apache-maven-*-bin.tar.gz
Next we create a sym-link
$ sudo ln -s /opt/apache-maven-$TMP_MAVEN_VERSION /opt/maven
Lastly we set up the env
$ sudo touch /etc/profile.d/maven.sh
$ sudo chown ubuntu /etc/profile.d/maven.sh
$ > /etc/profile.d/maven.sh echo "export JAVA_HOME=/usr/lib/jvm/default-java"
$ >> /etc/profile.d/maven.sh echo "export M2_HOME=/opt/maven"
$ >> /etc/profile.d/maven.sh echo "export MAVEN_HOME=/opt/maven"
$ >> /etc/profile.d/maven.sh echo "export PATH=$M2_HOME/bin:$PATH"
To use it without restarting the shell we make it executable and run it
$ sudo chmod +x /etc/profile.d/maven.sh
$ source /etc/profile.d/maven.sh
Now you can verify that it is properly installed
$ mvn -v
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/maven
Java version: 11.0.13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.11.0-1022-aws", arch: "amd64", family: "unix"
All in one solution
For convenience I added a public Gist with a bash script which prepares your system, you either reboot or run one additional command to be able to use it:
source /etc/profile.d/maven.sh
https://gist.github.com/Illutax/683483a4f50a749ea77bff0cb9637dea
This script takes one optional argument to install an alternative version.
Run it like that: sh maven-install.sh 3.8.4 && source /etc/profile.d/maven.sh
and you’re good to go
Source
Derived by a post on linuxize.com.
Содержание
- Maven 3.6.3-1 fails to run with OpenJDK 16 and 17
- Bug Description
- Debian Bug report logs — #980467 maven: Fails to run with OpenJDK 16 (Unable to load cache item)
- Error executing maven java lang illegalstateexception unable to load cache item
- Вопрос:
- Комментарии:
- Spring Boot 2.1.1: java.lang.IllegalStateException: невозможно получить ошибку базовых пакетов @EnableAutoConfiguration при запуске модульного теста
Maven 3.6.3-1 fails to run with OpenJDK 16 and 17
Affects | Status | Importance | Assigned to | Milestone |
---|---|---|---|---|
maven (Ubuntu) |
Bug Description
*System info*:
«`
$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
$ apt-cache policy maven
maven:
Installed: 3.6.3-1
Candidate: 3.6.3-1
Version table:
*** 3.6.3-1 500
500 http:// ch.archive. ubuntu. com/ubuntu focal/universe amd64 Packages
500 http:// ch.archive. ubuntu. com/ubuntu focal/universe i386 Packages
100 /var/lib/ dpkg/status
$ apt-cache policy openjdk-16-jdk
openjdk-16-jdk:
Installed: 16.0.1+9-1
20.04
Candidate: 16.0.1+9-1
20.04
Version table:
*** 16.0.1+9-1
20.04 500
500 http:// ch.archive. ubuntu. com/ubuntu focal-updates/ universe amd64 Packages
500 http:// security. ubuntu. com/ubuntu focal-security/ universe amd64 Packages
500 http:// ppa.launchpad. net/openjdk- r/ppa/ubuntu focal/main amd64 Packages
100 /var/lib/ dpkg/status
«`
*Summary*
Maven 3.6.3-1 apparently fails to run with OpenJDK 16. It seems to be a bug and was fixed in Maven 3.6.3-2 (and above) according to https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 980467.
*Expected behaviour*
I expect to be able to use maven with all currently supported General Availability Java versions.
Источник
Debian Bug report logs — #980467
maven: Fails to run with OpenJDK 16 (Unable to load cache item)
Date: Tue, 19 Jan 2021 13:57:01 UTC
Found in version maven/3.6.3-1
Fixed in version maven/3.6.3-2
Done: Emmanuel Bourg
Bug is archived. No further changes may be made.
Report forwarded to debian-bugs-dist@lists.debian.org, ebourg@apache.org, Debian Java Maintainers
:
Bug#980467 ; Package maven . (Tue, 19 Jan 2021 13:57:03 GMT) (full text, mbox, link).
—> Acknowledgement sent to Emmanuel Bourg :
New Bug report received and forwarded. Copy sent to ebourg@apache.org, Debian Java Maintainers
—> Message sent on to Emmanuel Bourg :
Bug#980467. (Tue, 19 Jan 2021 21:15:09 GMT) (full text, mbox, link).
Message #8 received at 980467-submitter@bugs.debian.org (full text, mbox, reply):
—> ‘pending’ >; —> » >; —> Added tag(s) pending. Request was from Emmanuel Bourg to 980467-submitter@bugs.debian.org . (Tue, 19 Jan 2021 21:15:09 GMT) (full text, mbox, link).
—> Reply sent to Emmanuel Bourg :
You have taken responsibility. (Tue, 19 Jan 2021 21:39:12 GMT) (full text, mbox, link).
—> Notification sent to Emmanuel Bourg :
Bug acknowledged by developer. (Tue, 19 Jan 2021 21:39:12 GMT) (full text, mbox, link).
—> Bug archived. Request was from Debbugs Internal Request to internal_control@bugs.debian.org . (Wed, 17 Feb 2021 07:29:39 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.
Источник
Error executing maven java lang illegalstateexception unable to load cache item
#java #maven #java-8 #maven-3 #java-16
Вопрос:
Я пытаюсь создать свой java-проект с помощью maven с помощью mvn package или mvn clean install , но я получаю эту ошибку:
Проект представляет собой простой java-проект, в котором используется java 8.
Кроме того, у меня есть несколько версий java на моем компьютере. Если я запускаюсь mvn -X , когда maven использует java 16, я получаю эту ошибку:
Если я изменю версию java, используемую maven, на версию 1.8, я получу это:
Также,
Может кто — нибудь объяснить мне причину.
Комментарии:
1. Я полагаю, что это на платформе на базе Linux, где вы установили maven через менеджер пакетов ОС? Если это так, пожалуйста, удалите установку операционной системы и установите ее отсюда: maven.apache.org/download.cgi (Просто для уверенности, можете ли вы перепроверить: mvn —version что именно распечатано?
2. …кроме того, «Для этой сборки не было указано никаких целей», где вы в основном не указали их в командной строке, поэтому было бы здорово, если бы вы могли поделиться, какую команду вы выполнили, когда увидели эти журналы? Что-то вроде mvn -X package и не только mvn -X .
3. @Naman Это на самом деле не проблема, потому что даже если вы не укажете цель / жизненный цикл, он не должен потерпеть неудачу с таким исполнением.
4. @khmarbaise Просто для уточнения, я говорил о второй трассировке стека(требуется прокрутка сегмента кода), которую OP получил с Java-8 🙂 Я почти уверен, что, не указывая цель, которой будет этот опыт, я готов немедленно сообщить об ошибке в проекте JIRA maven 😛
5. @khmarbaise использует maven уже довольно давно, и я хорошо это знаю/благодарен за это 🙂
Источник
Spring Boot 2.1.1: java.lang.IllegalStateException: невозможно получить ошибку базовых пакетов @EnableAutoConfiguration при запуске модульного теста
При выполнении модульного теста будет выдана следующая ошибка. Пожалуйста, сообщите, не упустил ли я что-то. Я использую Spring Boot 2.1.1.RELEASE. Спасибо!
java.lang.IllegalStateException: Unable to retrieve @EnableAutoConfiguration base packages
приложение-test.yml
AppRepository.java
AppRepositoryTest.java
Структура пакета
Я попробовал решение от Zaccus, но у меня это не сработало. Я использую Spring Boot 2.3.2.RELEASE и JUnit 5. В моей ситуации мне нужно было переместить мою модель и репозиторий в отдельную библиотеку, потому что они должны были совместно использоваться моим веб-приложением и инструментом.
Вот что у меня получилось поработать:
Spring Boot JPA Test без основного приложения или SpringApplication
Начиная с Spring Boot 2.1, при использовании @DataJpaTest больше не нужно указывать
В моей ситуации basePackages = <«com.example. *»>Не нужен, поскольку PlaceRepository и PlaceRepositoryTest находятся в одном пакете. Я добавил его сюда только на тот случай, если у кого-то есть тесты, которые включают репозитории, найденные в разных пакетах. Без «basePackages» @EnableJpaRepositories будет сканировать пакет аннотированного класса конфигурации для репозиториев Spring Data по умолчанию.
Изначально у меня были только следующие аннотации:
На найденных мной веб-сайтах говорилось, что мне понадобятся только @DataJpaTest и @EnableJpaRepositories, однако, только с указанным выше, я получил следующую ошибку:
Мне потребовалось время, чтобы понять это. С «Неуправляемым типом» я подумал, что что-то не так с моим классом Place:
Основная причина в том, что место не было просканировано как объект. Чтобы исправить это, мне нужно было добавить
Я нашел «@EntityScan» из другого решения в stackoverflow: Spring boot — не управляемый тип
Источник
I faced the same issue. Sadly I just could update to 3.6.3 via the package manager so I installed it manually. Steps to install on ubuntu below:
Maven 3.3+ requires JDK 1.7 or above to be installed.
Download Apache Maven. I installed 3.8.6, you can check for the newest version here: https://maven.apache.org/download.cgi
We save the archive to /tmp
$ TMP_MAVEN_VERSION=3.8.6
$ wget https://apache.org/dist/maven/maven-3/$TMP_MAVEN_VERSION/binaries/apache-maven-$TMP_MAVEN_VERSION-bin.tar.gz -P /tmp
Then unzip it to /opt
and remove the archive
$ sudo tar xf /tmp/apache-maven-*.tar.gz -C /opt
$ sudo rm /tmp/apache-maven-*-bin.tar.gz
Next we create a sym-link
$ sudo ln -s /opt/apache-maven-$TMP_MAVEN_VERSION /opt/maven
Lastly we set up the env
$ sudo echo "export JAVA_HOME=/usr/lib/jvm/default-java
export M2_HOME=/opt/maven
export MAVEN_HOME=/opt/maven
export PATH=${M2_HOME}/bin:${PATH}" >> /etc/profile.d/maven.sh
To use it without restarting we make it executable and run in
$ sudo chmod +x /etc/profile.d/maven.sh
$ source /etc/profile.d/maven.sh
Now you can verify that it is properly installed
$ mvn -v
Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
Maven home: /opt/maven
Java version: 11.0.13, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.11.0-1022-aws", arch: "amd64", family: "unix"
derived by
1) Introduction
We will demonstrate some workaround for the this IllegalStateException: Unable to load cache item
2) Workaround
Caused by: java.lang.NoClassDefFoundError: javax/servlet/Filter
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
at java.lang.Class.getDeclaredConstructors(Class.java:2020)
Caused by: java.lang.ClassNotFoundException: javax.servlet.Filter
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
Caused by: java.lang.IllegalStateException: Unable to load cache item
at org.springframework.cglib.core.internal.LoadingCache.createEntry(LoadingCache.java:79)
Caused by: java.lang.NullPointerException
at org.springframework.test.context.web.socket.MockServerContainerContextCustomizer.customizeContext(MockServerContainerContextCustomizer.java:38)
Case 1:
When ClassNotFoundException occurs along with Unable to load cache item, then upgrade your spring boot version dependency to the latest one and remove the spring-core dependency if any and try again.
Case 2:
When NullPointerException occurs along with Unable to load cache item, then a particular class is initialized by spring container, but it can not happen. In this case, check for the class level variables which are not initialized during boot run.
3) Summary
This article illustrated the quick workaround for Spring boot Unable to load cache item exception
*System info*:
«`
$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
$ apt-cache policy maven
maven:
Installed: 3.6.3-1
Candidate: 3.6.3-1
Version table:
*** 3.6.3-1 500
500 http://ch.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://ch.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status
$ apt-cache policy openjdk-16-jdk
openjdk-16-jdk:
Installed: 16.0.1+9-1~20.04
Candidate: 16.0.1+9-1~20.04
Version table:
*** 16.0.1+9-1~20.04 500
500 http://ch.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
500 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
«`
*Summary*
Maven 3.6.3-1 apparently fails to run with OpenJDK 16. It seems to be a bug and was fixed in Maven 3.6.3-2 (and above) according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980467.
*Expected behaviour*
I expect to be able to use maven with all currently supported General Availability Java versions.
*Observed behaviour*
I installed OpenJDK 16 (via PPA, see version above) and tried to compile a Maven project, producing the following output:
«`
$ mvn compile
[ERROR] Error executing Maven.
[ERROR] java.lang.IllegalStateException: Unable to load cache item
[ERROR] Caused by: Unable to load cache item
[ERROR] Caused by: Could not initialize class com.google.inject.internal.cglib.core.$MethodWrapper
$ echo $?
1
«`
Thanks and kind regards,
-Manu
Reported by: Emmanuel Bourg <ebourg@apache.org>
Date: Tue, 19 Jan 2021 13:57:01 UTC
Severity: important
Found in version maven/3.6.3-1
Fixed in version maven/3.6.3-2
Done: Emmanuel Bourg <ebourg@apache.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, ebourg@apache.org, Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
:
Bug#980467
; Package maven
.
(Tue, 19 Jan 2021 13:57:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Emmanuel Bourg <ebourg@apache.org>
:
New Bug report received and forwarded. Copy sent to ebourg@apache.org, Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
.
(Tue, 19 Jan 2021 13:57:03 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: maven Version: 3.6.3-1 Severity: important maven/3.6.3-1 fails to run with OpenJDK 16, the following error is displayed: [ERROR] Error executing Maven. [ERROR] java.lang.IllegalStateException: Unable to load cache item [ERROR] Caused by: Unable to load cache item [ERROR] Caused by: Could not initialize class com.google.inject.internal.cglib.core.$MethodWrapper Replacing the guice symlink is /usr/share/maven/lib with the guice-4.2.1-no_aop.jar library from the upstream distribution solves the issue.
Message sent on
to Emmanuel Bourg <ebourg@apache.org>
:
Bug#980467.
(Tue, 19 Jan 2021 21:15:09 GMT) (full text, mbox, link).
Message #8 received at 980467-submitter@bugs.debian.org (full text, mbox, reply):
Control: tag -1 pending Hello, Bug #980467 in maven reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven/-/commit/48fb5b2ae0dcd860d61e4b258d60fcee03d2713c ------------------------------------------------------------------------ Depend on Guice no_aop (Closes: #948310, #980467) ------------------------------------------------------------------------ (this message was generated automatically) -- Greetings https://bugs.debian.org/980467
Added tag(s) pending.
Request was from Emmanuel Bourg <noreply@salsa.debian.org>
to 980467-submitter@bugs.debian.org
.
(Tue, 19 Jan 2021 21:15:09 GMT) (full text, mbox, link).
Reply sent
to Emmanuel Bourg <ebourg@apache.org>
:
You have taken responsibility.
(Tue, 19 Jan 2021 21:39:12 GMT) (full text, mbox, link).
Notification sent
to Emmanuel Bourg <ebourg@apache.org>
:
Bug acknowledged by developer.
(Tue, 19 Jan 2021 21:39:12 GMT) (full text, mbox, link).
Message #15 received at 980467-close@bugs.debian.org (full text, mbox, reply):
Source: maven Source-Version: 3.6.3-2 Done: Emmanuel Bourg <ebourg@apache.org> We believe that the bug you reported is fixed in the latest version of maven, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 980467@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg <ebourg@apache.org> (supplier of updated maven package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 19 Jan 2021 18:58:13 +0100 Source: maven Architecture: source Version: 3.6.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org> Changed-By: Emmanuel Bourg <ebourg@apache.org> Closes: 677989 948286 948310 980467 Changes: maven (3.6.3-2) unstable; urgency=medium . * Depend on Guice no_aop (Closes: #948310, #980467) * Fixed the name of the bash completion script * Fixed the bash completion of the dependency plugin (Closes: #677989) * Fixed the versioned dependency on libplexus-utils2-java (Closes: #948286) * Tightened the dependency on libsisu-plexus-java (>= 0.3.4) * Standards-Version updated to 4.5.1 * Switch to debhelper level 13 Checksums-Sha1: 53a1f074c4c4c7f3b3e931094b107961a679ce42 2869 maven_3.6.3-2.dsc 914ca5886f62db324bd787632aef68440cc68afe 15616 maven_3.6.3-2.debian.tar.xz 82d568988023a413117f83fcc5afae96470e20a8 15192 maven_3.6.3-2_source.buildinfo Checksums-Sha256: 48717d7afa12b13cbb3d4b45fd5d5efa2ed44ff11f1032862ba8b5f09b77c9c4 2869 maven_3.6.3-2.dsc 6eed51987d500b0e0d74c570177858b703f55ab18bdd8cc222e7af05e9ba604d 15616 maven_3.6.3-2.debian.tar.xz 94edd60b0002870de6c9e8bb240eadfdfd01988459aa5eb05009067ddc4fe5bb 15192 maven_3.6.3-2_source.buildinfo Files: 98b8a0c28b5516ef8a9cb4370d586c97 2869 java optional maven_3.6.3-2.dsc 70a0c379b6a7964f3dd8661c9f4102b0 15616 java optional maven_3.6.3-2.debian.tar.xz fd427ab6437d3970f32fbd20e98f4b3c 15192 java optional maven_3.6.3-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAHS4oSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs8O0P+wSHFQCMn95BJ3kXTMlFLyYrzcMewyuf 5VtoNTWuwnXhAJ7ZdNVK9a6cIwaO4A75VODz2SGxDrgmMRCR0OeeQ0WhhXEi0EOl BxNZ9+p9IQwib9rBfF5Vm8nOBEsalLy0mVun/GBp2psRpI2LZFTNJlZhc/1Te4xg iiZ86LE23no9aJZgt23HerGPDRqWi6QThQAoofVDftNmR+WGUrJXocv9+8US0aUE t+lMtQffR8d5y/uIv//GPSSZHKXsTUVVc6edc+c+HFK4SIfNMJbNHDi7nr0s73MR tsV0S5By/SwM9GX0n4b/WdGSNmzvv+qWlj+/PhgRS2JyT7PB9RGS/D42sE3XFipW FlRuCbOrfbOsCnm2wOcN/vcpRfWvjB9trzZpuZyD0N/zRzYtMG5+kwd6pWJrLVYP IdPOFJ2pXbfprokbNdYHjNEiLuF3FSgeJaA2JZEA+NNVs/aN8kio5TRCj767mM/5 MvkuF/YQm3Qgz/R/A7YPbN0HkVIE0QOx7vohkMSIaAlDzpBFn3O9HaOuJSqa/jfX cm0m5Gu4WrRi4LK48tb72u2G9R7Y/YKhi/EIdkmXOYq5qYC53PlatrwSi8RVQApI TdROqx3MFHOSALSNHDAcX2MeakbtaPI5n/kXeSJfKPBjy2tqS0+mlNtjNtKQOZj3 WosmcmRWO64G =72O/ -----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org
.
(Wed, 17 Feb 2021 07:29:39 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 13:33:37 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.