maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan E. Magen" <>
Subject maven crash on startup after safe-upgrade in debian squeeze
Date Thu, 20 Aug 2009 13:19:33 GMT

I just ran a safe-upgrade on my Debian Squeeze machine and,
unfortunately maven has now broken due to some Java packages being
upgraded. The list of changes which took place before maven broke is
as follows:

The following NEW packages will be installed:
  fop{a} groovy{a} ivy{a} java-wrappers{a} junit4{a} libasm2-java{a}
libasm3-java{a} libavalon-framework-java{a} libbatik-java{a}
libbsf-java{a} libcommons-beanutils-java{a}
  libcommons-configuration-java{a} libcommons-digester-java{a}
libcommons-io-java{a} libcommons-jxpath-java{a}
libgoogle-collections-java{a} libhamcrest-java{a} liblog4j1.2-java{a}
liblog4j1.2-java-gcj{a} libmockobjects-java{a}
  libplexus-containers-java{a} libplexus-i18n-java{a} libsaxon-java{a}
libservlet2.4-java{a} libxbean-java{a} libxml-commons-external-java{a}
libxmlgraphics-commons-java{a} libxstream-java{a}
The following packages will be REMOVED:
  ant{u} ant-gcj{u} ant-optional{u} ant-optional-gcj{u}
libbcel-java{u} libcommons-collections-java{u} libjdom0-java{u}
liblogkit-java{u} libplexus-velocity-java{u} libwerken.xpath-java{u}
The following packages will be upgraded:
  antlr apt apt-utils aptitude ca-certificates debianutils
libantlr-java libantlr-java-gcj libcommons-cli-java
libcommons-codec-java libcommons-httpclient-java libcommons-lang-java
libcommons-logging-java libdoxia-java libept0
  libjsch-java libjtidy-java liboro-java libplexus-classworlds-java
libplexus-component-api-java libplexus-container-default-java
libplexus-interactivity-api-java libplexus-interpolation-java
libplexus-utils-java libregexp-java
  libxerces2-java libxerces2-java-gcj

So, I tried to remove the maven2 package and reinstall it hoping to
pull in the required deps again but it did not help. I then thought it
might be ant, so I installed ant and still it did not help Perhaps
there is something identifiable in this list which needs to be
installed that I missed.

Upon starting maven, even with no params, I get the following trace:

Exception in thread "main" java.lang.NoClassDefFoundError:
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(
        at java.lang.Class.privateGetPublicMethods(
        at java.lang.Class.getMethods(
        at org.codehaus.classworlds.Launcher.getEnhancedMainMethod(
        at org.codehaus.classworlds.Launcher.launchEnhanced(
        at org.codehaus.classworlds.Launcher.launch(
        at org.codehaus.classworlds.Launcher.mainWithExitCode(
        at org.codehaus.classworlds.Launcher.main(
Caused by: java.lang.ClassNotFoundException:
        at Method)
        at java.lang.ClassLoader.loadClass(
        at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(
        at org.codehaus.classworlds.DefaultClassRealm.loadClass(
        at org.codehaus.classworlds.RealmClassLoader.loadClass(
        at java.lang.ClassLoader.loadClass(
        at java.lang.ClassLoader.loadClassInternal(
        ... 9 more

If this is an easily-fixable bug due to a package install or
something, then I will gladly file a bug report with Debian so that
the package might be fixed. Thank you very much!

Jonathan E. Magen
AIM: SuspectAshkenaz

View raw message