Hi, I've completed the work, based on Ryan's initial implementation.
https://github.com/jenkinsci/maven-hpi-plugin/pull/12 Vincent 2014-09-25 23:09 GMT+02:00 Kohsuke Kawaguchi <k...@kohsuke.org>: > > This is great! > > I don't have cycles right now but it seems like you are almost there. > > This would be needed before we can start taking advantages of servlet 3.0. > > > On 09/23/2014 08:17 AM, Ryan Campbell wrote: > >> I took a crack <https://github.com/jenkinsci/maven-hpi-plugin/pull/11> >> >> at porting hpi:run to Jetty 8. However, when I integrate it into a >> plugin's build like so: >> >> <build> >> <plugins> >> <plugin> >> <groupId>org.jenkins-ci.tools</groupId> >> <artifactId>maven-hpi-plugin</artifactId> >> <version>1.110-SNAPSHOT</version> >> <extensions>true</extensions> >> <configuration> >> <showDeprecation>true</showDeprecation> >> <contextPath>/jenkins</contextPath> >> <!-- TODO specify ${java.level} when JENKINS-20679 >> implemented --> >> </configuration> >> </plugin> >> </plugins> >> </build> >> >> It fails on boot: >> >> 2014-09-23 10:12:40.802:INFO:oejs.Server:jetty-8.1.14.v20131031 >> 2014-09-23 10:12:42.616:WARN:oejw.WebAppContext:Failed startup of >> context >> >> o.m.j.p.JettyWebAppContext{/,file:/Users/recampbell/plugin/target/tmp/webapp/},/Users/recampbell/.m2/repository/org/jenkins-ci/main/jenkins-war/1.532.1/jenkins-war-1.532.1.war >> javax.naming.NoInitialContextException: Need to specify class name in >> environment or system property, or as an applet parameter, or in an >> application resource file: java.naming.factory.initial >> at >> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) >> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) >> at >> >> javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344) >> at javax.naming.InitialContext.lookup(InitialContext.java:411) >> at >> >> org.eclipse.jetty.plus.webapp.EnvConfiguration.createEnvContext(EnvConfiguration.java:257) >> >> https://gist.github.com/recampbell/90ab897c495253fd76e0 >> >> I tried adding jetty-jndi to the classpath, but this didn't resolve the >> issue: >> >> <dependency> >> <groupId>org.eclipse.jetty</groupId> >> <artifactId>jetty-jndi</artifactId> >> <version>8.1.14.v20131031</version> >> <scope>test</scope> >> </dependency> >> >> I appreciate any insight. I plan to come back to this, but thought I'd >> document the state in case someone else would like to complete it or >> provide insight. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to jenkinsci-dev+unsubscr...@googlegroups.com >> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Kohsuke Kawaguchi http://kohsuke.org/ > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCjvtAULfBJN7LA6ekGspXd9rFrdKZ%2B1uACtneQFDVzxUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
