'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester

Details

Type: Bug
Status: Closed
Priority: Blocker
Resolution: Fixed
Affects Version/s: 3.0-beta-3
Fix Version/s: 3.0
Component/s: None
Labels:
None
Environment:
Linux 2.6.27.48-0.6-pae #1 SMP 686 athlon i386 GNU/Linux - SUSE Linux Enterprise Server 11.
Java 1.6.0_21 Sun

Complexity:
Intermediate
Number of attachments :
0

Description

This error doesn't show up on Windows with maven 3 beta-3, Java 1.6.0_21 !!!
This error also doesn't show up with maven 3 beta-2 on Linux and Windows, both Java 1.6.0_21.

I switched from maven 3 beta-2 to beta-3 and got this error.
I deleted the complete .m2/repository/ but nothing changed.

Only on Linux with maven 3 beta-3 I can reproduce this error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) on project nivadis: Execution default-install of goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install failed: Unable to load the mojo 'install' in the plugin 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester
-----------------------------------------------------
realm = plugin>org.apache.maven.plugins:maven-install-plugin:2.3.1
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
urls[0] = file:/home/vbs/.m2/repository/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar
urls[1] = file:/home/vbs/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Number of foreign imports: 4
import: Entry[import org.codehaus.plexus.util.xml.pull.XmlSerializer from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParserException from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.util.xml.pull.XmlPullParser from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.util.xml.Xpp3Dom from realm ClassRealm[plexus.core, parent: null]]

realm = maven.api
strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
Number of foreign imports: 21
import: Entry[import org.sonatype.aether from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.personality from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.logging from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.lifecycle from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.context from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.container from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.configuration from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.component from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.classworlds from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.PlexusContainerException from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.PlexusContainer from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.PlexusConstants from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.MutablePlexusContainer from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.DuplicateChildContainerException from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.DefaultPlexusContainer from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.DefaultContainerConfiguration from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.DefaultComponentRegistry from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.ContainerConfiguration from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.plexus.ComponentRegistry from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.codehaus.classworlds from realm ClassRealm[plexus.core, parent: null]]
import: Entry[import org.apache.maven from realm ClassRealm[plexus.core, parent: null]]

-----------------------------------------------------
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException

Issue Links

is duplicated by

MNG-4798 NullPointerException at NearestVersionConflictResolver.selectVersion()

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Benjamin Bentmann added a comment - 03/Sep/10 6:15 AM

The plugin class path is incomplete, which is usually caused by bad POM, in this case the maven-install-plugin-2.3.1.pom. I'm not able reproduce this from the information given. So please verify your local copy of the mentioned POM actually matches the remote copy on central or attach a full debug log from Maven which would reveal why it didn't properly parse the POM.

Show

Benjamin Bentmann added a comment - 03/Sep/10 6:15 AM The plugin class path is incomplete, which is usually caused by bad POM, in this case the maven-install-plugin-2.3.1.pom. I'm not able reproduce this from the information given. So please verify your local copy of the mentioned POM actually matches the remote copy on central or attach a full debug log from Maven which would reveal why it didn't properly parse the POM.

Hide

Permalink

Jochen Stiepel added a comment - 08/Sep/10 2:47 AM - edited

I checked the pom with different tools in different ways (checksum, differ, bytes-size) - they all say the pom's on this computer and on my windows computer are the same.

Steps's I already did:
1.) deleted .m2/repository/
2.) run Maven 3 Beta-2 mvn clean install - all jar's are downloaded, no failure.
3.) change to Maven 3 Beta-3.
4.) run Maven 3 Beta-3 mvn clean install (with the same files inside the repository) it throws this error ~~MNG-4794~~
5.) run Maven 3 Beta-3 mvn clean package it throws the error ~~MNG-4798~~
Environment: Suse Linux Enterprise (SLES) 11, Sun Java 1.6.0_21

I tried using Ubuntu (10.10 beta) on my Notebook, with Sun Java 1.6.0_21 it works.

Summary:
On my SLES Server it works with Maven 3 Beta-2 but it doesn't work with Beta-3.
Maven 3 Beta-3 works fine on my WinXP and Ubuntu Installation. All used the same Java Version.

Possibly causes:

SLES Server 11 - because until now it only happens there.
Changes inside Maven - because it works fine with Beta-2 but not Beta-3.

I'll try to provide debug output from the Beta-2 and Beta-3 run.

Show

Jochen Stiepel added a comment - 08/Sep/10 2:47 AM - edited I checked the pom with different tools in different ways (checksum, differ, bytes-size) - they all say the pom's on this computer and on my windows computer are the same. Steps's I already did: 1.) deleted .m2/repository/ 2.) run Maven 3 Beta-2 mvn clean install - all jar's are downloaded, no failure. 3.) change to Maven 3 Beta-3. 4.) run Maven 3 Beta-3 mvn clean install (with the same files inside the repository) it throws this error MNG-4794 5.) run Maven 3 Beta-3 mvn clean package it throws the error MNG-4798 Environment: Suse Linux Enterprise (SLES) 11, Sun Java 1.6.0_21 I tried using Ubuntu (10.10 beta) on my Notebook, with Sun Java 1.6.0_21 it works. Summary: On my SLES Server it works with Maven 3 Beta-2 but it doesn't work with Beta-3. Maven 3 Beta-3 works fine on my WinXP and Ubuntu Installation. All used the same Java Version. Possibly causes: SLES Server 11 - because until now it only happens there. Changes inside Maven - because it works fine with Beta-2 but not Beta-3. I'll try to provide debug output from the Beta-2 and Beta-3 run.

Hide

Permalink

Jochen Stiepel added a comment - 08/Sep/10 8:03 AM

I found the cause of this problem!
On the SLES Server there were two JDK's installed. The Sun JDK and an IBM JDK.

JAVA_HOME was pointing to the IBM-JDK and in the PATH the Sun JDK was first:
output of: mvn -version
Apache Maven 3.0-beta-3 (r990787; 2010-08-30 14:44:03+0200)
Java version: 1.6.0
Java home: /usr/lib/jvm/java-1_6_0-ibm-1.6.0/jre
Default locale: de_DE, platform encoding: ISO-8859-1
OS name: "linux" version: "2.6.27.48-0.6-pae" arch: "x86" Family: "unix"

output of (Sun JDK): java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing)

output of (IBM-JDK): /usr/lib/jvm/java-1_6_0-ibm-1.6.0/jre/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr8-20100409_01(SR8))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr8-20100401_55940 (JIT enabled, AOT enabled)
J9VM - 20100401_055940
JIT - r9_20100401_15339
GC - 20100308_AA)
JCL - 20100408_01

Then I changed the JAVA_HOME to the Sun-JDK and it works. Afterwards I changed the JAVA_HOME and the PATH to the IBM-JDK and I'm getting the exception again.

Show

Jochen Stiepel added a comment - 08/Sep/10 8:03 AM I found the cause of this problem! On the SLES Server there were two JDK's installed. The Sun JDK and an IBM JDK. JAVA_HOME was pointing to the IBM-JDK and in the PATH the Sun JDK was first: output of: mvn -version Apache Maven 3.0-beta-3 (r990787; 2010-08-30 14:44:03+0200) Java version: 1.6.0 Java home: /usr/lib/jvm/java-1_6_0-ibm-1.6.0/jre Default locale: de_DE, platform encoding: ISO-8859-1 OS name: "linux" version: "2.6.27.48-0.6-pae" arch: "x86" Family: "unix" output of (Sun JDK): java -version java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing) output of (IBM-JDK): /usr/lib/jvm/java-1_6_0-ibm-1.6.0/jre/java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pxi3260sr8-20100409_01(SR8)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr8-20100401_55940 (JIT enabled, AOT enabled) J9VM - 20100401_055940 JIT - r9_20100401_15339 GC - 20100308_AA) JCL - 20100408_01 Then I changed the JAVA_HOME to the Sun-JDK and it works. Afterwards I changed the JAVA_HOME and the PATH to the IBM-JDK and I'm getting the exception again.

Hide

Permalink

Benjamin Bentmann added a comment - 08/Sep/10 8:07 AM

I would still appreciate a debug log to see how exactly the JDK affects the overall build process.

Show

Benjamin Bentmann added a comment - 08/Sep/10 8:07 AM I would still appreciate a debug log to see how exactly the JDK affects the overall build process.

Hide

Permalink

Benjamin Bentmann added a comment - 26/Sep/10 10:50 AM

Installed workaround for JRE bug in r1001459.

Show

Benjamin Bentmann added a comment - 26/Sep/10 10:50 AM Installed workaround for JRE bug in r1001459 .

People

Assignee:

Benjamin Bentmann

Reporter:

Jochen Stiepel

Vote (0)

Watch (2)

Dates

Created:

03/Sep/10 5:57 AM

Updated:

26/Sep/10 10:51 AM

Resolved:

26/Sep/10 10:50 AM