You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/04/10 11:34:32 UTC

[jira] Updated: (WICKET-455) mvn jetty:run; maven-jetty-plugin not configured

     [ https://issues.apache.org/jira/browse/WICKET-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Quenot updated WICKET-455:
----------------------------------------

    Attachment: quickstart-pom.txt

With this patch, you can use jetty:run but Jetty is removed from the dependencies so you won't be able to run Jetty from Eclipse anymore.  The problem lies in the Jetty6 Maven plugin that makes use of a Jetty's custom WebappClassLoader.  It is possible to fix that, but Wicket is not to blame here, unless we can come up with another idea of providing the Quickstart project.  Quickstart is meant to be run from within Eclipse with the Start class.

> mvn jetty:run; maven-jetty-plugin not configured
> ------------------------------------------------
>
>                 Key: WICKET-455
>                 URL: https://issues.apache.org/jira/browse/WICKET-455
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-quickstart
>    Affects Versions: 1.3
>            Reporter: Martin Funk
>         Assigned To: Jean-Baptiste Quenot
>         Attachments: quickstart-pom.txt
>
>
> maven-jetty-plugin not configured for wicket-quickstart.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.