You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/12/18 01:30:19 UTC

[jira] Updated: (MNG-3712) [regression] java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin

     [ http://jira.codehaus.org/browse/MNG-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3712:
------------------------------

    Affects Version/s:     (was: 2.x)
                           (was: 3.x)
                       3.0-alpha-1
        Fix Version/s: 3.0-alpha-3
              Summary: [regression] java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin  (was: java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin)

needs verification on latest builds

> [regression] java.lang.NoClassDefFoundError in maven-jaxb-schemagen-plugin
> --------------------------------------------------------------------------
>
>                 Key: MNG-3712
>                 URL: http://jira.codehaus.org/browse/MNG-3712
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 3.0-alpha-1
>            Reporter: Eugene Kuleshov
>            Priority: Blocker
>             Fix For: 3.0-alpha-3
>
>         Attachments: build.log, generate-schema.zip
>
>
> When running maven-jaxb-schemagen-plugin with Maven 2.1-SNAPSHOT and latest 3.0-SNAPSHOT from trunk it fails with java.lang.NoClassDefFoundError. See attached test project and debug log from the build.
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/mirror/apt/AnnotationProcessorFactory
> 	at com.sun.tools.jxc.maven2.SchemaGenMojo.execute(SchemaGenMojo.java:143)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:638)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:521)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:288)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:214)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:172)
> 	at org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
> 	at org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:303)
> 	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
> 	at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
> 	at org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:303)
> 	at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
> 	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
> 	at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> 	at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> {noformat}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira