The problem is likely that you don't have all required repositories for the
dependencies of the plugin defined as plugin repositories.
Someone else had the exact same problem (different plugin though) earlier
this week.
In Maven 3, dependencies for plugins are only retrieved from
pluginRepositories. This was not the case in Maven 2.

/Anders

On Fri, Mar 4, 2011 at 15:42, clt <[email protected]> wrote:

> Hi  all
>
> I used to have a project run well with maven2 and jetty 6.
>
> Today I updated to maven3 today. There were an exception when I run my
> project with mvn jetty:run, says that: there's no plugin in found with name
> jetty. So I add <pluginGroup>org.mortbay.jetty</pluginGroup> to settins.xml
> . And it reported an other error:
>
> [INFO] <<< jetty-maven-plugin:8.0.0.M2:run (default-cli) @ learntest <<<
> [INFO]
> [INFO] --- jetty-maven-plugin:8.0.0.M2:run (default-cli) @ learntest ---
> [WARNING] The POM for javax.servlet.jsp.jstl:jstl-api:jar:1.2 is missing,
> no
> dependency information available
> [WARNING] The POM for org.glassfish.web:jstl-impl:jar:1.2 is missing, no
> dependency information available
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1.156s
> [INFO] Finished at: Fri Mar 04 14:25:01 GMT 2011
> [INFO] Final Memory: 4M/8M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.mortbay.jetty:jetty-maven-plugin:8.0.0.M2:run (default-cli) on project
> learntest: Execution default-cli of goal
> org.mortbay.jetty:jetty-maven-plugin:8.0.0.M2:run failed: Plugin
> org.mortbay.jetty:jetty-maven-plugin:8.0.0.M2 or one of its dependencies
> could not be resolved: The following artifacts could not be resolved:
> javax.servlet.jsp.jstl:jstl-api:jar:1.2,
> org.glassfish.web:jstl-impl:jar:1.2: Failure to find
> javax.servlet.jsp.jstl:jstl-api:jar:1.2 in
> http://localhost/nexus/content/groups/public was cached in the local
> repository, resolution will not be reattempted until the update interval of
> nexus has elapsed or updates are forced -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
>
> I have added java.net/glassfish to nexus repositories, but it seems
> doesn't
> work.
> How can I specify jetty version or solve the problem ?
>

Reply via email to