FYI, the plexus-component-metadata exception should be fixed by:  

https://github.com/sonatype/plexus-containers/pull/2

basically ClassLoader.getResourceAsStream returns null for 
“java/lang/Object.class” in jigsaw - so this skips gleaning java/lang/Object
( an alternative solution would be to return null from “readClass2” when the 
inputStream is null, but that could have wider implications )  

--  
Cheers, Stuart


On Wednesday, 9 September 2015 at 22:47, Robert Scholte wrote:

> Hi,
>  
> My first results when building Apache Maven 3.3.7-SNAPSHOT
> Without extra configuration it fails with the message:
> No compiler is provided in this environment. Perhaps you are running on a  
> JRE rather than a JDK?
>  
> However, if I add the following arguments it at least continues:
> -Dmaven.compiler.executable=D:\jdk1.9.0\bin\javac.exe -Dmaven.compiler.fork
>  
> So this is something we need to fix on our side. If I recall correctly we  
> do a tools.jar check somewhere, will require some extra investigation.
>  
> The build doesn't complete, it fails with the exception below, but  
> according to the message we need an improved version from ASM first.
>  
> best,
> Robert
>  
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute  
> goal org.codehaus.plexus:plexus-component-metadata:1.5.5:generate-metadata  
> (default) on project maven-model-builder: Error generating metadata:
> at  
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at  
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at  
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at  
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at  
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at  
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at  
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at  
> sun.reflect.NativeMethodAccessorImpl.invoke0([email protected] 
> (mailto:[email protected])/Native Method)
> at  
> sun.reflect.NativeMethodAccessorImpl.invoke([email protected] 
> (mailto:[email protected])/NativeMethodAccessorImpl.java:62)
> at  
> sun.reflect.DelegatingMethodAccessorImpl.invoke([email protected] 
> (mailto:[email protected])/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke([email protected] 
> (mailto:[email protected])/Method.java:517)
> 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:415)
> at  
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error  
> generating metadata:
> at  
> org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:86)
> at  
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at  
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.Exception: Failed to extract descriptors
> at  
> org.codehaus.plexus.metadata.DefaultMetadataGenerator.generateDescriptor(DefaultMetadataGenerator.java:86)
> at  
> org.codehaus.plexus.maven.plugin.PlexusDescriptorMojo.execute(PlexusDescriptorMojo.java:82)
> ... 22 more
> Caused by: org.codehaus.plexus.metadata.gleaner.ComponentGleanerException:  
> Can't read class java/lang/Object
> at  
> org.codehaus.plexus.metadata.gleaner.AnnotationComponentGleaner.readClass2(AnnotationComponentGleaner.java:161)
> at  
> org.codehaus.plexus.metadata.gleaner.AnnotationComponentGleaner.getClasses(AnnotationComponentGleaner.java:180)
> at  
> org.codehaus.plexus.metadata.gleaner.AnnotationComponentGleaner.glean(AnnotationComponentGleaner.java:100)
> at  
> org.codehaus.plexus.metadata.ClassComponentDescriptorExtractor.extract(ClassComponentDescriptorExtractor.java:145)
> at  
> org.codehaus.plexus.metadata.ClassComponentDescriptorExtractor.extract(ClassComponentDescriptorExtractor.java:79)
> at  
> org.codehaus.plexus.metadata.DefaultMetadataGenerator.generateDescriptor(DefaultMetadataGenerator.java:78)
> ... 23 more
> Caused by: java.io.IOException: Class not found
> at org.objectweb.asm.ClassReader.a (http://web.asm.ClassReader.a)(Unknown 
> Source)
> at org.objectweb.asm.ClassReader (http://web.asm.ClassReader).<init>(Unknown 
> Source)
> at  
> org.codehaus.plexus.metadata.ann.AnnReader.read(AnnReader.java:45)
> at  
> org.codehaus.plexus.metadata.gleaner.AnnotationComponentGleaner.readClass2(AnnotationComponentGleaner.java:157)
> ... 28 more
>  
>  
>  
> Op Wed, 09 Sep 2015 19:16:13 +0200 schreef Rory O'Donnell  
> <[email protected] (mailto:[email protected])>:
>  
> >  
> > Hi Robert & Kristian,
> >  
> > Early-access builds of JDK 9 with Project Jigsaw are available for
> > download at jdk9.java.net/jigsaw <http://jdk9.java.net/jigsaw>.
> >  
> > The EA builds contain the latest prototype implementation of JSR 376
> > <http://openjdk.java.net/projects/jigsaw/spec>, the Java Platform Module
> > System,
> > as well as that of the JDK-specific APIs and tools described in JEP 261
> > <http://openjdk.java.net/jeps/261>.
> >  
> > If you'd like to try out the EA builds, by far the most helpful things
> > you can do are:
> >  
> > *
> >  
> > Try to run existing applications, without change, on these builds to
> > see whether the module system, or the modularization of the
> > platform, breaks your code or identifies code that depends upon
> > JDK-internal APIs or other unspecified aspects of the platform.
> >  
> > *
> >  
> > Experiment with the module system itself, perhaps by following the
> > quick start guide
> > <http://openjdk.java.net/projects/jigsaw/quick-start>, and start
> > thinking about how to migrate existing libraries and application
> > components to modules. We hope to publish some specific migration
> > tips shortly.
> >  
> > Please send usage questions and experience reports to the jigsaw-dev
> > <http://mail.openjdk.java.net/mailman/listinfo/jigsaw-dev> list.
> > Specific suggestions about the design of the module system should be
> > sent to the JSR 376 Expert Group's comments list
> > <mailto:[email protected]>.
> >  
> > For more information please seen Mark Reinhold's mail [1]
> >  
> > Rgds,Rory
> >  
> > [1]http://mail.openjdk.java.net/pipermail/jigsaw-dev/2015-September/004480.html
>  
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] 
> (mailto:[email protected])
> For additional commands, e-mail: [email protected] 
> (mailto:[email protected])
>  
>  


Reply via email to