1.8.0_40, vendor: Oracle Corporation ??

That's not available yet.
http://www.oracle.com/technetwork/java/javase/downloads/index.html

Our build has NPN/ALPN dependencies that require bootclasspath
modifications of the SslEngine.
Those modifications are JVM specific, and there is no JVM specific version
for 1.8.0_40 (yet).

Downgrade to 1.8.0_31 and try again.

Note: NPN has been dropped in Jetty 9.3.x so that's one less problem on
that version of Jetty.
And when Java 9 comes out with its expected support for ALPN, then our
bootclasspath requirement will go away for that JVM.


--
Joakim Erdfelt <[email protected]>
webtide.com <http://www.webtide.com/> - intalio.com/jetty
Expert advice, services and support from from the Jetty & CometD experts
eclipse.org/jetty - cometd.org

On Fri, Feb 27, 2015 at 9:53 AM, <[email protected]> wrote:

> I'm trying a 1st build of jetty9 from source.
>
> git clone https://github.com/eclipse/jetty.project.git
> cd jetty.project
> git log | head
>         commit b533aa6ce514863b8c89f8dc64704f7a9cee0946
>         Author: Simone Bordet <[email protected]>
>         Date:   Fri Feb 27 12:30:42 2015 +0100
>
>             Made tests more stable.
>
>             Naked writes could throw WritePendingException.
>             Now we wait until the client has finished sending the reply to
> the
>             server SETTINGS frame, then we do the naked write.
>
> mvn -version
>         Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
> 2014-12-14T09:29:23-08:00)
>         Maven home: /usr/share/java/maven
>         Java version: 1.8.0_40, vendor: Oracle Corporation
>         Java home: /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre
>         Default locale: en_US, platform encoding: UTF-8
>         OS name: "linux", version: "3.19.0-2.g1133f88-desktop", arch:
> "amd64", family: "unix"
>
> mvn -e -U clean install
>         ...
>         [INFO] Jetty :: OSGi :: Test .............................. SKIPPED
>         [INFO]
> ------------------------------------------------------------------------
>         [INFO] BUILD FAILURE
>         [INFO]
> ------------------------------------------------------------------------
>         [INFO] Total time: 18:51 min
>         [INFO] Finished at: 2015-02-27T08:16:10-08:00
>         [INFO] Final Memory: 153M/1578M
>         [INFO]
> ------------------------------------------------------------------------
>         [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
> project jetty-start: There are test failures.
>         [ERROR]
>         [ERROR] Please refer to
> /home/hanl/projects/jetty.project/jetty-start/target/surefire-reports for
> the individual test results.
>         [ERROR] -> [Help 1]
>         org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test
> (default-test) on project jetty-start: There are test failures.
>
>         Please refer to
> /home/hanl/projects/jetty.project/jetty-start/target/surefire-reports for
> the individual test results.
>                 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>                 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:120)
>                 at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
>                 at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
>                 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
>                 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
>                 at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
>                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>                 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>                 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>                 at java.lang.reflect.Method.invoke(Method.java:497)
>                 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.MojoFailureException: There are
> test failures.
>
>         Please refer to
> /home/hanl/projects/jetty.project/jetty-start/target/surefire-reports for
> the individual test results.
>                 at
> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:82)
>                 at
> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:195)
>                 at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:861)
>                 at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:729)
>                 at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
>                 at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>                 ... 19 more
>         [ERROR]
>         [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/MojoFailureException
>         [ERROR]
>         [ERROR] After correcting the problems, you can resume the build
> with the command
>         [ERROR]   mvn <goals> -rf :jetty-start
>
>
> And in
>
> ls -1
> /home/hanl/projects/jetty.project/jetty-start/target/surefire-reports | sort
>         org.eclipse.jetty.start.BaseHomeTest.txt
>         org.eclipse.jetty.start.CommandLineBuilderTest.txt
>         org.eclipse.jetty.start.config.ConfigSourcesTest.txt
>         org.eclipse.jetty.start.DistTest.txt
>         org.eclipse.jetty.start.FileArgTest.txt
>
> org.eclipse.jetty.start.fileinits.MavenLocalRepoFileInitializerTest.txt
>         org.eclipse.jetty.start.FSTest.txt
>         org.eclipse.jetty.start.graph.NodeTest.txt
>         org.eclipse.jetty.start.IncludeJettyDirTest.txt
>         org.eclipse.jetty.start.JarVersionTest.txt
>         org.eclipse.jetty.start.LicensingTest.txt
>         org.eclipse.jetty.start.MainTest.txt
>         org.eclipse.jetty.start.ModuleGraphWriterTest.txt
>         org.eclipse.jetty.start.ModulesTest.txt
>         org.eclipse.jetty.start.ModuleTest.txt
>         org.eclipse.jetty.start.PathFinderTest.txt
>         org.eclipse.jetty.start.PathMatchersAbsoluteTest.txt
>         org.eclipse.jetty.start.PathMatchersSearchRootTest.txt
>         org.eclipse.jetty.start.PropertyPassingTest.txt
>         org.eclipse.jetty.start.PropsTest.txt
>         org.eclipse.jetty.start.TestBadUseCases.txt
>         org.eclipse.jetty.start.TestUseCases.txt
>         org.eclipse.jetty.start.VersionTest.txt
>         TEST-org.eclipse.jetty.start.BaseHomeTest.xml
>         TEST-org.eclipse.jetty.start.CommandLineBuilderTest.xml
>         TEST-org.eclipse.jetty.start.config.ConfigSourcesTest.xml
>         TEST-org.eclipse.jetty.start.DistTest.xml
>         TEST-org.eclipse.jetty.start.FileArgTest.xml
>
> TEST-org.eclipse.jetty.start.fileinits.MavenLocalRepoFileInitializerTest.xml
>         TEST-org.eclipse.jetty.start.FSTest.xml
>         TEST-org.eclipse.jetty.start.graph.NodeTest.xml
>         TEST-org.eclipse.jetty.start.IncludeJettyDirTest.xml
>         TEST-org.eclipse.jetty.start.JarVersionTest.xml
>         TEST-org.eclipse.jetty.start.LicensingTest.xml
>         TEST-org.eclipse.jetty.start.MainTest.xml
>         TEST-org.eclipse.jetty.start.ModuleGraphWriterTest.xml
>         TEST-org.eclipse.jetty.start.ModulesTest.xml
>         TEST-org.eclipse.jetty.start.ModuleTest.xml
>         TEST-org.eclipse.jetty.start.PathFinderTest.xml
>         TEST-org.eclipse.jetty.start.PathMatchersAbsoluteTest.xml
>         TEST-org.eclipse.jetty.start.PathMatchersSearchRootTest.xml
>         TEST-org.eclipse.jetty.start.PropertyPassingTest.xml
>         TEST-org.eclipse.jetty.start.PropsTest.xml
>         TEST-org.eclipse.jetty.start.TestBadUseCases.xml
>         TEST-org.eclipse.jetty.start.TestUseCases.xml
>         TEST-org.eclipse.jetty.start.VersionTest.xml
>
> I've perused
>
>  http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> but I'm not clear on what I'd do here.
>
> Is this a bug?  Or do I need additional or different steps?
>
> hanlon
> _______________________________________________
> jetty-users mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to