public final class JettyHelper {

    private JettyHelper() {
        throw new IllegalAccessError("Utility class");
    }

    public static Server createServer(int port, File warFile, String
contextRoot) throws Exception {

        Server server = new Server();
        Connector connector = new SelectChannelConnector();
        connector.setPort(port);
        server.addConnector(connector);

        WebAppContext context = new WebAppContext(warFile.getAbsolutePath(),
contextRoot);

        context.setConfigurationClasses(new String[]{
                "org.mortbay.jetty.webapp.WebInfConfiguration",
                "org.mortbay.jetty.plus.webapp.EnvConfiguration",
                "org.mortbay.jetty.annotations.Configuration",
                "org.mortbay.jetty.webapp.JettyWebXmlConfiguration",
                "org.mortbay.jetty.webapp.TagLibConfiguration"
        });

        context.setExtractWAR(false);
        context.setCopyWebDir(false);
        context.setParentLoaderPriority(true);

        server.setHandler(context);

        server.start();

        return server;
    }

    public static void destroyServer(Server server) throws Exception {
        if (server == null) return;
        if (!server.isStopped()) {
            server.stop();
            server.join();
        }
    }
}


On 4 March 2010 11:58, Douglas Ferguson <doug...@douglasferguson.us> wrote:

> I've been experimenting with this and have come to find out that the mvn
> jetty plugin is not compatible with projects that include jetty in their pom
> dependencies.
>
> Now I need to figure out a different way to start up jetty. I have a
> Start.java class that could start up jetty but i would need to figure out
> how to stop it.
>
> Also, I'm found some information online about a version cobertura plugin
> that had a seperate generate-report goal. Anybody know where I could locate
> this?
>
> D/
>
> On Mar 4, 2010, at 4:05 AM, Brett Porter wrote:
>
> > On 04/03/2010, at 8:49 PM, Douglas Ferguson wrote:
> >
> >> Is there a clean way to start up jetty for the testing and then stopping
> git afterwards?
> >>
> >> I'd like to include my integration tests for my code coverage.
> >>
> >> I'd like to set my code coverage profile to only start up jetty after
> cobertura has instrumented the classes
> >> then shut it down after the tests complete.
> >>
> >> Could I just start up the jetty in process-test-classes and shut it down
> in prepare-package?
> >
> > Yep.
> >
> >
> http://github.com/brettporter/centrepoint/blob/master/centrepoint/modules/selenium-tests/pom.xml
> >
> > Bear in mind that if the tests fail, the "stop" won't be run, but
> normally they will shut down properly when Maven does anyway.
> >
> > - Brett
> >
> > --
> > Brett Porter
> > br...@apache.org
> > http://brettporter.wordpress.com/
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to