You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by clt <ph...@gmail.com> on 2011/03/04 15:42:48 UTC
How can I specify jetty version or use maven3 with latest jetty ?
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 ?
Re: How can I specify jetty version or use maven3 with latest jetty ?
Posted by clt <ph...@gmail.com>.
I added http://download.java.net/maven/glassfish to my nexus's public group
( maven2 proxy, maven1 proxy, maven2 virtual) with three types. I didn't
know which type worked.
May be the nexus need some time to index the
java.net/maven/glassfishrepositories. So after some time , mvn
jetty:run can download the required
jars.
2011/3/5 Anders Hammar <an...@hammar.net>
> You would simplify things by grouping the repos (in the repo manager,
> Artifactory) instead of handling them one by one. I think it's called
> virtual repos in Artifactory terms.
> If you ask on the Artifactory users list, they could probably help you.
>
> /Anders
>
> On Fri, Mar 4, 2011 at 17:05, <sh...@accenture.com> wrote:
>
> > I think I'm running afoul of this but am not sure what the right solution
> > is (I'm the SysAdmin for some deva switching to maven3).
> >
> > A plugin that builds fine under maven2 can't find a dependency under
> > maven3, yet I see it deployed/cached under repo1-cache where it's always
> > been. It only appears to look in:
> >
> > plugins-release
> > plugins-snapshot
> > plugins-release-local
> > plugins-snapshot-local
> >
> > Are you saying that I have to define repo1-cache as a plugin repository?
> Am
> > I likely going to wind up listing all the caches as plugin repositories?
> My
> > apologies for being clueless - I never had to use Artifactory (2.3.2) or
> > Maven (3.0.2) before about four days ago. :-)
> >
> > -ste
> >
> > On Mar 4, 2011, at 10:13 AM, "Anders Hammar" <an...@hammar.net> wrote:
> >
> > > 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 <ph...@gmail.com> 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 ?
> > >>
> >
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise private information. If you have
> > received it in error, please notify the sender immediately and delete the
> > original. Any other use of the email by you is prohibited.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
Re: How can I specify jetty version or use maven3 with latest jetty ?
Posted by Anders Hammar <an...@hammar.net>.
You would simplify things by grouping the repos (in the repo manager,
Artifactory) instead of handling them one by one. I think it's called
virtual repos in Artifactory terms.
If you ask on the Artifactory users list, they could probably help you.
/Anders
On Fri, Mar 4, 2011 at 17:05, <sh...@accenture.com> wrote:
> I think I'm running afoul of this but am not sure what the right solution
> is (I'm the SysAdmin for some deva switching to maven3).
>
> A plugin that builds fine under maven2 can't find a dependency under
> maven3, yet I see it deployed/cached under repo1-cache where it's always
> been. It only appears to look in:
>
> plugins-release
> plugins-snapshot
> plugins-release-local
> plugins-snapshot-local
>
> Are you saying that I have to define repo1-cache as a plugin repository? Am
> I likely going to wind up listing all the caches as plugin repositories? My
> apologies for being clueless - I never had to use Artifactory (2.3.2) or
> Maven (3.0.2) before about four days ago. :-)
>
> -ste
>
> On Mar 4, 2011, at 10:13 AM, "Anders Hammar" <an...@hammar.net> wrote:
>
> > 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 <ph...@gmail.com> 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 ?
> >>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: How can I specify jetty version or use maven3 with latest jetty
?
Posted by sh...@accenture.com.
I think I'm running afoul of this but am not sure what the right solution is (I'm the SysAdmin for some deva switching to maven3).
A plugin that builds fine under maven2 can't find a dependency under maven3, yet I see it deployed/cached under repo1-cache where it's always been. It only appears to look in:
plugins-release
plugins-snapshot
plugins-release-local
plugins-snapshot-local
Are you saying that I have to define repo1-cache as a plugin repository? Am I likely going to wind up listing all the caches as plugin repositories? My apologies for being clueless - I never had to use Artifactory (2.3.2) or Maven (3.0.2) before about four days ago. :-)
-ste
On Mar 4, 2011, at 10:13 AM, "Anders Hammar" <an...@hammar.net> wrote:
> 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 <ph...@gmail.com> 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 ?
>>
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: How can I specify jetty version or use maven3 with latest jetty ?
Posted by Anders Hammar <an...@hammar.net>.
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 <ph...@gmail.com> 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 ?
>