The key is that Xbootclasspath can only be set on JVM startup. It cannot be set after the JVM is initialized. So your exec-maven-plugin configuration must use "exec:exec", not "exec:java". Which means you'll have to find the jvm binary for the <executable><http://mojo.codehaus.org/exec-maven-plugin/exec-mojo.html#executable>and your <arguments><http://mojo.codehaus.org/exec-maven-plugin/exec-mojo.html#arguments>have to include the -Xbootclasspath you need to execute. Also, don't forget that the the npn jar is JVM dependant, so you'll likely want to configure the appropriate npn version based on your JVM. See the <profile> sections in the root pom.xml from jetty 9.x for examples on this<https://github.com/eclipse/jetty.project/blob/master/pom.xml#L744-L851> .
-- 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, Sep 27, 2013 at 5:50 PM, Nicholas Lun <[email protected]> wrote: > Hi all, > > I'm trying to use SPDY in Jetty 9 and I understand that I am supposed to > add > npn-boot to the bootclasspath when I start the server like this: java > -Xbootclasspath/p:<path_to_npn_boot_jar> > > However, I'm trying to do this in a maven project and cannot for the life > of > me figure out how to specify this using the exec-maven-plugin. Does anybody > have experience running embedded jetty inside a maven project that uses > SPDY? > > Regards, > Nick > > > > -- > View this message in context: > http://jetty.4.x6.nabble.com/Adding-npn-boot-to-the-bootclasspath-using-Maven-tp4961263.html > Sent from the Jetty User mailing list archive at Nabble.com. > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
