Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] fork the JVM in jetty-maven-plugin?

the general idea, I like

if you were to come up with a patch for the plugin I would like it even more! :)

I saw someone mention this not long ago, either in a jira issue or on
the codehaus dev list but have been too busy to give it a look see

cheers
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Wed, Apr 22, 2009 at 03:40, Aleksander Adamowski <jetty@xxxxxxxxxx> wrote:
> Hi!
>
> I think it would be beneficial to be able to fork the JVM in which
> jetty-maven-plugin
> (http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin) runs, just
> like Maven Surefire plugin currently allows
> (http://maven.apache.org/plugins/maven-surefire-plugin/examples/forking.html).
>
> Sometimes forking is necessary. E.g. when a web application loads a
> native library through JNI - starting a Jetty container more than once
> in such a build causes an UnsatisfiedLinkError (e.g.
> java.lang.UnsatisfiedLinkError: Native Library /usr/lib/libfoo.so
> already loaded in another classloader).
>
> What do you think about the general idea?
>
> --
> Best Regards,
>  Aleksander Adamowski
>  http://olo.org.pl
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>


Back to the top