Re: mvn tomcat:deploy fails with HTTP response 401

2012-05-01 Thread Pid
On 30/04/2012 11:26, Martin Gainty wrote:
> 
> 
> redirecting to maven users ..as this is a maven issue

Martin, FYI the Tomcat Maven Plugin community actually lives here.


p

> Thanks,
> Martin
> __ 
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>  
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich 
> dem Austausch von Informationen und entfaltet keine rechtliche 
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen 
> wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
> 
> 
>> Date: Sat, 28 Apr 2012 23:24:36 +0200
>> Subject: Re: mvn tomcat:deploy fails with HTTP response 401
>> From: hord...@gmail.com
>> To: users@tomcat.apache.org
>>
>> Awesome! I added the pluginGroup and it worked now.
>>
>> Thank you!
>>
>> 2012/4/28 Olivier Lamy 
>>
>>> Have a look here
>>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html
>>>
>>> there is a section regarding content to add in ~/.m2/settings.xml
>>>
>>> or add the plugin declaration in the pom section build>plugins>plugin
>>> (rather than pluginManagement)
>>>
>>> HTH
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> 2012/4/28 Henrique Ordine :
>>>> Thanks again for your help.
>>>>
>>>> I added  to my POM, but if I use tomcat6:deploy or
>>>> tomcat6:run, Maven says:
>>>>
>>>> The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
>>>> or no valid version could be found
>>>>
>>>> I'm using Maven, 2.2.0 by the way.
>>>>
>>>> 2012/4/27 Olivier Lamy 
>>>>
>>>>> Add
>>>>>  
>>>>>
>>>>>  apache.snapshots
>>>>>  Apache Snapshots
>>>>>  http://repository.apache.org/content/groups/snapshots-group/
>>>>> 
>>>>>  
>>>>>false
>>>>>  
>>>>>  
>>>>>true
>>>>>  
>>>>>
>>>>>  
>>>>>
>>>>> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
>>>>> version you want to use).
>>>>>
>>>>> I'd like to know the command line you are using ? It must be
>>>>> tomcat6:deploy or tomcat7:deploy
>>>>>
>>>>> 2012/4/27 Henrique Ordine :
>>>>>> Thanks for your reply.
>>>>>>
>>>>>> I made the changes that you suggested but tomcat:deploy still fails
>>> with
>>>>> the
>>>>>> same error.
>>>>>>
>>>>>> tomcat:run works, but it was already working before.
>>>>>>
>>>>>> My POM file is attached, if you could have a look at it, it would be
>>>>> great.
>>>>>> It's a small POM, I've only just started my App.
>>>>>>
>>>>>> Thanks in advance,
>>>>>>
>>>>>> Op 27 april 2012 12:14 schreef Olivier Lamy  het
>>>>> volgende:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> That's something which has been fixed in trunk (I will probably
>>>>>>> release a 2.0 next week).
>>>>>>>
>>>>>>>
>>>>>>> 2012/4/27 Henrique Ordine :
>>>>>>>> Hi everybody,
>>>>>>>>
>>>>>>>> I'm trying to deploy my Maven Web App o

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-30 Thread Olivier Lamy
Hi,
That's not an issue.
See documentation here:
http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html



2012/4/30 Martin Gainty :
>
>
> redirecting to maven users ..as this is a maven issue
>
> Thanks,
> Martin
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich 
> dem Austausch von Informationen und entfaltet keine rechtliche 
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen 
> wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
>
>
>> Date: Sat, 28 Apr 2012 23:24:36 +0200
>> Subject: Re: mvn tomcat:deploy fails with HTTP response 401
>> From: hord...@gmail.com
>> To: users@tomcat.apache.org
>>
>> Awesome! I added the pluginGroup and it worked now.
>>
>> Thank you!
>>
>> 2012/4/28 Olivier Lamy 
>>
>> > Have a look here
>> > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html
>> >
>> > there is a section regarding content to add in ~/.m2/settings.xml
>> >
>> > or add the plugin declaration in the pom section build>plugins>plugin
>> > (rather than pluginManagement)
>> >
>> > HTH
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >
>> > 2012/4/28 Henrique Ordine :
>> > > Thanks again for your help.
>> > >
>> > > I added  to my POM, but if I use tomcat6:deploy or
>> > > tomcat6:run, Maven says:
>> > >
>> > > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
>> > > or no valid version could be found
>> > >
>> > > I'm using Maven, 2.2.0 by the way.
>> > >
>> > > 2012/4/27 Olivier Lamy 
>> > >
>> > >> Add
>> > >>  
>> > >>    
>> > >>      apache.snapshots
>> > >>      Apache Snapshots
>> > >>      http://repository.apache.org/content/groups/snapshots-group/
>> > >> 
>> > >>      
>> > >>        false
>> > >>      
>> > >>      
>> > >>        true
>> > >>      
>> > >>    
>> > >>  
>> > >>
>> > >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
>> > >> version you want to use).
>> > >>
>> > >> I'd like to know the command line you are using ? It must be
>> > >> tomcat6:deploy or tomcat7:deploy
>> > >>
>> > >> 2012/4/27 Henrique Ordine :
>> > >> > Thanks for your reply.
>> > >> >
>> > >> > I made the changes that you suggested but tomcat:deploy still fails
>> > with
>> > >> the
>> > >> > same error.
>> > >> >
>> > >> > tomcat:run works, but it was already working before.
>> > >> >
>> > >> > My POM file is attached, if you could have a look at it, it would be
>> > >> great.
>> > >> > It's a small POM, I've only just started my App.
>> > >> >
>> > >> > Thanks in advance,
>> > >> >
>> > >> > Op 27 april 2012 12:14 schreef Olivier Lamy  het
>> > >> volgende:
>> > >> >>
>> > >> >> Hello,
>> > >> >>
>> > >> >> That's something which has been fixed in trunk (I will probably
>> > >> >> rele

RE: mvn tomcat:deploy fails with HTTP response 401

2012-04-30 Thread Martin Gainty


redirecting to maven users ..as this is a maven issue

Thanks,
Martin
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.


> Date: Sat, 28 Apr 2012 23:24:36 +0200
> Subject: Re: mvn tomcat:deploy fails with HTTP response 401
> From: hord...@gmail.com
> To: users@tomcat.apache.org
> 
> Awesome! I added the pluginGroup and it worked now.
> 
> Thank you!
> 
> 2012/4/28 Olivier Lamy 
> 
> > Have a look here
> > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html
> >
> > there is a section regarding content to add in ~/.m2/settings.xml
> >
> > or add the plugin declaration in the pom section build>plugins>plugin
> > (rather than pluginManagement)
> >
> > HTH
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
> > 2012/4/28 Henrique Ordine :
> > > Thanks again for your help.
> > >
> > > I added  to my POM, but if I use tomcat6:deploy or
> > > tomcat6:run, Maven says:
> > >
> > > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
> > > or no valid version could be found
> > >
> > > I'm using Maven, 2.2.0 by the way.
> > >
> > > 2012/4/27 Olivier Lamy 
> > >
> > >> Add
> > >>  
> > >>
> > >>  apache.snapshots
> > >>  Apache Snapshots
> > >>  http://repository.apache.org/content/groups/snapshots-group/
> > >> 
> > >>  
> > >>false
> > >>  
> > >>  
> > >>true
> > >>  
> > >>
> > >>  
> > >>
> > >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
> > >> version you want to use).
> > >>
> > >> I'd like to know the command line you are using ? It must be
> > >> tomcat6:deploy or tomcat7:deploy
> > >>
> > >> 2012/4/27 Henrique Ordine :
> > >> > Thanks for your reply.
> > >> >
> > >> > I made the changes that you suggested but tomcat:deploy still fails
> > with
> > >> the
> > >> > same error.
> > >> >
> > >> > tomcat:run works, but it was already working before.
> > >> >
> > >> > My POM file is attached, if you could have a look at it, it would be
> > >> great.
> > >> > It's a small POM, I've only just started my App.
> > >> >
> > >> > Thanks in advance,
> > >> >
> > >> > Op 27 april 2012 12:14 schreef Olivier Lamy  het
> > >> volgende:
> > >> >>
> > >> >> Hello,
> > >> >>
> > >> >> That's something which has been fixed in trunk (I will probably
> > >> >> release a 2.0 next week).
> > >> >>
> > >> >>
> > >> >> 2012/4/27 Henrique Ordine :
> > >> >> > Hi everybody,
> > >> >> >
> > >> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the
> > >> >> > tomcat:deploy maven plugin, but the Manager application fails with
> > a
> > >> >> > response code 401.
> > >> >> >
> > >> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I
> > manage
> > >> to
> > >> >> > access my Tomcat/manager app with the user "hordin

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-28 Thread Henrique Ordine
Awesome! I added the pluginGroup and it worked now.

Thank you!

2012/4/28 Olivier Lamy 

> Have a look here
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html
>
> there is a section regarding content to add in ~/.m2/settings.xml
>
> or add the plugin declaration in the pom section build>plugins>plugin
> (rather than pluginManagement)
>
> HTH
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> 2012/4/28 Henrique Ordine :
> > Thanks again for your help.
> >
> > I added  to my POM, but if I use tomcat6:deploy or
> > tomcat6:run, Maven says:
> >
> > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
> > or no valid version could be found
> >
> > I'm using Maven, 2.2.0 by the way.
> >
> > 2012/4/27 Olivier Lamy 
> >
> >> Add
> >>  
> >>
> >>  apache.snapshots
> >>  Apache Snapshots
> >>  http://repository.apache.org/content/groups/snapshots-group/
> >> 
> >>  
> >>false
> >>  
> >>  
> >>true
> >>  
> >>
> >>  
> >>
> >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
> >> version you want to use).
> >>
> >> I'd like to know the command line you are using ? It must be
> >> tomcat6:deploy or tomcat7:deploy
> >>
> >> 2012/4/27 Henrique Ordine :
> >> > Thanks for your reply.
> >> >
> >> > I made the changes that you suggested but tomcat:deploy still fails
> with
> >> the
> >> > same error.
> >> >
> >> > tomcat:run works, but it was already working before.
> >> >
> >> > My POM file is attached, if you could have a look at it, it would be
> >> great.
> >> > It's a small POM, I've only just started my App.
> >> >
> >> > Thanks in advance,
> >> >
> >> > Op 27 april 2012 12:14 schreef Olivier Lamy  het
> >> volgende:
> >> >>
> >> >> Hello,
> >> >>
> >> >> That's something which has been fixed in trunk (I will probably
> >> >> release a 2.0 next week).
> >> >>
> >> >>
> >> >> 2012/4/27 Henrique Ordine :
> >> >> > Hi everybody,
> >> >> >
> >> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the
> >> >> > tomcat:deploy maven plugin, but the Manager application fails with
> a
> >> >> > response code 401.
> >> >> >
> >> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I
> manage
> >> to
> >> >> > access my Tomcat/manager app with the user "hordine", that I
> >> configured
> >> >> > and
> >> >> > deploy
> >> >> >
> >> >> > I've configured my tomcat-users.xml, settings.xml, and POM files,
> like
> >> >> > this:
> >> >> >
> >> >> > I've added this user to my tomcat-users.xml:
> >> >> >  
> >> >> >  
> >> >> >  
> >> >> >  
> >> >> >   roles="manager"/>
> >> >> >  
> >> >> >
> >> >> >
> >> >> > I've added this server to my settings.xml:
> >> >> > 
> >> >> >
> >> >> >hordineLocalTomcat
> >> >> >hordine
> >> >> >hordine
> >> >> >
> >> >> > 
> >> >> >
> >> >> > And I've configured my POM like this:
> >> >> >
> >> >> > 
> >> >> >
> >> >> > hTask-web
> >> >> >
> >> >> >  
> >> >> >
> >> >> >  
> >> >> >
> >> >> >  
> >> >> >
> >> >> > org.apache.tomcat.maven
> >> >> >
> >> >> >   tomcat-maven-plugin
> >> >> >
> >> >> >   1.1
> >> >>
> >> >> Sure of that 
> >> >>
> >> >> But to test if your issue is fixed in trunk try
> >> >> 2.0-SNAPSHOT
> >> >>
> >> >> see mojo declaration and repositories here:
> >> >>
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
> >> >>
> >> >> >
> >> >> >   
> >> >> >
> >> >> >   http://localhost:8080/manager
> >> >> >
> >> >> >   hordineLocalTomcat
> >> >> >
> >> >> >   /hTask-web
> >> >> >
> >> >> >  
> >> >> >
> >> >> >  
> >> >> >
> >> >> >  
> >> >> >
> >> >> >  
> >> >> >
> >> >> > 
> >> >> >
> >> >> >
> >> >> > I'd appreciate any help.
> >> >> >
> >> >> > This is the entire error's stack trace:
> >> >> >
> >> >> > Embedded error: Server returned HTTP response code: 401 for URL:
> >> >> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> >> >> > [INFO]
> >> >> >
> >> 
> >> >> > [INFO] Trace
> >> >> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot
> invoke
> >> >> > Tomcat manager
> >> >> > at
> >> >> >
> >> >> >
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> >> >> > at
> >> >> >
> >> >> >
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> >> >> > at
> >> >> >
> >> >> >
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> >> >> > at
> >> >> >
> >> >> >
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> >> >> > at
> >> >> >
> >> >> >
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> >> >> > at
>

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-28 Thread Olivier Lamy
Have a look here http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html

there is a section regarding content to add in ~/.m2/settings.xml

or add the plugin declaration in the pom section build>plugins>plugin
(rather than pluginManagement)

HTH
-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

2012/4/28 Henrique Ordine :
> Thanks again for your help.
>
> I added  to my POM, but if I use tomcat6:deploy or
> tomcat6:run, Maven says:
>
> The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
> or no valid version could be found
>
> I'm using Maven, 2.2.0 by the way.
>
> 2012/4/27 Olivier Lamy 
>
>> Add
>>  
>>    
>>      apache.snapshots
>>      Apache Snapshots
>>      http://repository.apache.org/content/groups/snapshots-group/
>> 
>>      
>>        false
>>      
>>      
>>        true
>>      
>>    
>>  
>>
>> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
>> version you want to use).
>>
>> I'd like to know the command line you are using ? It must be
>> tomcat6:deploy or tomcat7:deploy
>>
>> 2012/4/27 Henrique Ordine :
>> > Thanks for your reply.
>> >
>> > I made the changes that you suggested but tomcat:deploy still fails with
>> the
>> > same error.
>> >
>> > tomcat:run works, but it was already working before.
>> >
>> > My POM file is attached, if you could have a look at it, it would be
>> great.
>> > It's a small POM, I've only just started my App.
>> >
>> > Thanks in advance,
>> >
>> > Op 27 april 2012 12:14 schreef Olivier Lamy  het
>> volgende:
>> >>
>> >> Hello,
>> >>
>> >> That's something which has been fixed in trunk (I will probably
>> >> release a 2.0 next week).
>> >>
>> >>
>> >> 2012/4/27 Henrique Ordine :
>> >> > Hi everybody,
>> >> >
>> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the
>> >> > tomcat:deploy maven plugin, but the Manager application fails with a
>> >> > response code 401.
>> >> >
>> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage
>> to
>> >> > access my Tomcat/manager app with the user "hordine", that I
>> configured
>> >> > and
>> >> > deploy
>> >> >
>> >> > I've configured my tomcat-users.xml, settings.xml, and POM files, like
>> >> > this:
>> >> >
>> >> > I've added this user to my tomcat-users.xml:
>> >> >  
>> >> >  
>> >> >  
>> >> >  
>> >> >  
>> >> >  
>> >> >
>> >> >
>> >> > I've added this server to my settings.xml:
>> >> > 
>> >> >    
>> >> >        hordineLocalTomcat
>> >> >        hordine
>> >> >        hordine
>> >> >    
>> >> > 
>> >> >
>> >> > And I've configured my POM like this:
>> >> >
>> >> > 
>> >> >
>> >> > hTask-web
>> >> >
>> >> >  
>> >> >
>> >> >  
>> >> >
>> >> >  
>> >> >
>> >> >         org.apache.tomcat.maven
>> >> >
>> >> >           tomcat-maven-plugin
>> >> >
>> >> >           1.1
>> >>
>> >> Sure of that 
>> >>
>> >> But to test if your issue is fixed in trunk try
>> >> 2.0-SNAPSHOT
>> >>
>> >> see mojo declaration and repositories here:
>> >> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
>> >>
>> >> >
>> >> >           
>> >> >
>> >> >   http://localhost:8080/manager
>> >> >
>> >> >   hordineLocalTomcat
>> >> >
>> >> >   /hTask-web
>> >> >
>> >> >  
>> >> >
>> >> >  
>> >> >
>> >> >  
>> >> >
>> >> >  
>> >> >
>> >> > 
>> >> >
>> >> >
>> >> > I'd appreciate any help.
>> >> >
>> >> > This is the entire error's stack trace:
>> >> >
>> >> > Embedded error: Server returned HTTP response code: 401 for URL:
>> >> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
>> >> > [INFO]
>> >> >
>> 
>> >> > [INFO] Trace
>> >> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke
>> >> > Tomcat manager
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>> >> > at
>> >> >
>> >> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>> >> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>> >> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>> >> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> >> > at
>> >> >
>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> > at

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-28 Thread Henrique Ordine
Thanks again for your help.

I added  to my POM, but if I use tomcat6:deploy or
tomcat6:run, Maven says:

The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist
or no valid version could be found

I'm using Maven, 2.2.0 by the way.

2012/4/27 Olivier Lamy 

> Add
>  
>
>  apache.snapshots
>  Apache Snapshots
>  http://repository.apache.org/content/groups/snapshots-group/
> 
>  
>false
>  
>  
>true
>  
>
>  
>
> Note now you must use tomcat6:run or tomcat7:run (depending tomcat
> version you want to use).
>
> I'd like to know the command line you are using ? It must be
> tomcat6:deploy or tomcat7:deploy
>
> 2012/4/27 Henrique Ordine :
> > Thanks for your reply.
> >
> > I made the changes that you suggested but tomcat:deploy still fails with
> the
> > same error.
> >
> > tomcat:run works, but it was already working before.
> >
> > My POM file is attached, if you could have a look at it, it would be
> great.
> > It's a small POM, I've only just started my App.
> >
> > Thanks in advance,
> >
> > Op 27 april 2012 12:14 schreef Olivier Lamy  het
> volgende:
> >>
> >> Hello,
> >>
> >> That's something which has been fixed in trunk (I will probably
> >> release a 2.0 next week).
> >>
> >>
> >> 2012/4/27 Henrique Ordine :
> >> > Hi everybody,
> >> >
> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the
> >> > tomcat:deploy maven plugin, but the Manager application fails with a
> >> > response code 401.
> >> >
> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage
> to
> >> > access my Tomcat/manager app with the user "hordine", that I
> configured
> >> > and
> >> > deploy
> >> >
> >> > I've configured my tomcat-users.xml, settings.xml, and POM files, like
> >> > this:
> >> >
> >> > I've added this user to my tomcat-users.xml:
> >> >  
> >> >  
> >> >  
> >> >  
> >> >  
> >> >  
> >> >
> >> >
> >> > I've added this server to my settings.xml:
> >> > 
> >> >
> >> >hordineLocalTomcat
> >> >hordine
> >> >hordine
> >> >
> >> > 
> >> >
> >> > And I've configured my POM like this:
> >> >
> >> > 
> >> >
> >> > hTask-web
> >> >
> >> >  
> >> >
> >> >  
> >> >
> >> >  
> >> >
> >> > org.apache.tomcat.maven
> >> >
> >> >   tomcat-maven-plugin
> >> >
> >> >   1.1
> >>
> >> Sure of that 
> >>
> >> But to test if your issue is fixed in trunk try
> >> 2.0-SNAPSHOT
> >>
> >> see mojo declaration and repositories here:
> >> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
> >>
> >> >
> >> >   
> >> >
> >> >   http://localhost:8080/manager
> >> >
> >> >   hordineLocalTomcat
> >> >
> >> >   /hTask-web
> >> >
> >> >  
> >> >
> >> >  
> >> >
> >> >  
> >> >
> >> >  
> >> >
> >> > 
> >> >
> >> >
> >> > I'd appreciate any help.
> >> >
> >> > This is the entire error's stack trace:
> >> >
> >> > Embedded error: Server returned HTTP response code: 401 for URL:
> >> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> >> > [INFO]
> >> >
> 
> >> > [INFO] Trace
> >> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke
> >> > Tomcat manager
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> >> > at
> >> >
> >> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> >> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> >> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> >> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >> > at
> >> >
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
> >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> > at
> >> >
> >> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> > at
> >> >
> >> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >> > at java.lang.reflect.Method.invoke(Method.java:592)
> >> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >> > at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> > Caused 

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-27 Thread Olivier Lamy
Add
  

  apache.snapshots
  Apache Snapshots
  http://repository.apache.org/content/groups/snapshots-group/
  
false
  
  
true
  

  

Note now you must use tomcat6:run or tomcat7:run (depending tomcat
version you want to use).

I'd like to know the command line you are using ? It must be
tomcat6:deploy or tomcat7:deploy

2012/4/27 Henrique Ordine :
> Thanks for your reply.
>
> I made the changes that you suggested but tomcat:deploy still fails with the
> same error.
>
> tomcat:run works, but it was already working before.
>
> My POM file is attached, if you could have a look at it, it would be great.
> It's a small POM, I've only just started my App.
>
> Thanks in advance,
>
> Op 27 april 2012 12:14 schreef Olivier Lamy  het volgende:
>>
>> Hello,
>>
>> That's something which has been fixed in trunk (I will probably
>> release a 2.0 next week).
>>
>>
>> 2012/4/27 Henrique Ordine :
>> > Hi everybody,
>> >
>> > I'm trying to deploy my Maven Web App on my local Tomcat using the
>> > tomcat:deploy maven plugin, but the Manager application fails with a
>> > response code 401.
>> >
>> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage to
>> > access my Tomcat/manager app with the user "hordine", that I configured
>> > and
>> > deploy
>> >
>> > I've configured my tomcat-users.xml, settings.xml, and POM files, like
>> > this:
>> >
>> > I've added this user to my tomcat-users.xml:
>> >  
>> >  
>> >  
>> >  
>> >  
>> >  
>> >
>> >
>> > I've added this server to my settings.xml:
>> > 
>> >    
>> >        hordineLocalTomcat
>> >        hordine
>> >        hordine
>> >    
>> > 
>> >
>> > And I've configured my POM like this:
>> >
>> > 
>> >
>> > hTask-web
>> >
>> >  
>> >
>> >  
>> >
>> >  
>> >
>> >         org.apache.tomcat.maven
>> >
>> >           tomcat-maven-plugin
>> >
>> >           1.1
>>
>> Sure of that 
>>
>> But to test if your issue is fixed in trunk try
>> 2.0-SNAPSHOT
>>
>> see mojo declaration and repositories here:
>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
>>
>> >
>> >           
>> >
>> >   http://localhost:8080/manager
>> >
>> >   hordineLocalTomcat
>> >
>> >   /hTask-web
>> >
>> >  
>> >
>> >  
>> >
>> >  
>> >
>> >  
>> >
>> > 
>> >
>> >
>> > I'd appreciate any help.
>> >
>> > This is the entire error's stack trace:
>> >
>> > Embedded error: Server returned HTTP response code: 401 for URL:
>> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
>> > [INFO]
>> > 
>> > [INFO] Trace
>> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke
>> > Tomcat manager
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>> > at
>> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
>> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> > at
>> >
>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> > at
>> >
>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> > at java.lang.reflect.Method.invoke(Method.java:592)
>> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> > Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke
>> > Tomcat manager
>> > at
>> >
>> > org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:149)
>> > at
>> >
>> > org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:70)
>> > at
>> >
>> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>> > at
>> >
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>> > ... 17 more
>> > Caused by: java.io.IOException: Server returned HTTP response code: 401
>> > for
>> > URL

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-27 Thread Henrique Ordine
Thanks for your reply.

I made the changes that you suggested but tomcat:deploy still fails with
the same error.

tomcat:run works, but it was already working before.

My POM file is attached, if you could have a look at it, it would be great.
It's a small POM, I've only just started my App.

Thanks in advance,

Op 27 april 2012 12:14 schreef Olivier Lamy  het volgende:

> Hello,
>
> That's something which has been fixed in trunk (I will probably
> release a 2.0 next week).
>
>
> 2012/4/27 Henrique Ordine :
> > Hi everybody,
> >
> > I'm trying to deploy my Maven Web App on my local Tomcat using the
> > tomcat:deploy maven plugin, but the Manager application fails with a
> > response code 401.
> >
> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage to
> > access my Tomcat/manager app with the user "hordine", that I configured
> and
> > deploy
> >
> > I've configured my tomcat-users.xml, settings.xml, and POM files, like
> this:
> >
> > I've added this user to my tomcat-users.xml:
> >  
> >  
> >  
> >  
> >  
> >  
> >
> >
> > I've added this server to my settings.xml:
> > 
> >
> >hordineLocalTomcat
> >hordine
> >hordine
> >
> > 
> >
> > And I've configured my POM like this:
> >
> > 
> >
> > hTask-web
> >
> >  
> >
> >  
> >
> >  
> >
> > org.apache.tomcat.maven
> >
> >   tomcat-maven-plugin
> >
> >   1.1
>
> Sure of that 
>
> But to test if your issue is fixed in trunk try
> 2.0-SNAPSHOT
>
> see mojo declaration and repositories here:
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
>
> >
> >   
> >
> >   http://localhost:8080/manager
> >
> >   hordineLocalTomcat
> >
> >   /hTask-web
> >
> >  
> >
> >  
> >
> >  
> >
> >  
> >
> > 
> >
> >
> > I'd appreciate any help.
> >
> > This is the entire error's stack trace:
> >
> > Embedded error: Server returned HTTP response code: 401 for URL:
> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> > [INFO]
> > 
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke
> > Tomcat manager
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> > at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:592)
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke
> > Tomcat manager
> > at
> >
> org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:149)
> > at
> >
> org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:70)
> > at
> >
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> > ... 17 more
> > Caused by: java.io.IOException: Server returned HTTP response code: 401
> for
> > URL: http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> > at
> >
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1196)
> > at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:604)
> > at
> org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java:662)
> > at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:295)
> > at
> >
> org.codehaus.mojo.tomcat.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:85)
> > at
> >
> org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:85)
> > at
> >

Re: mvn tomcat:deploy fails with HTTP response 401

2012-04-27 Thread Olivier Lamy
Hello,

That's something which has been fixed in trunk (I will probably
release a 2.0 next week).


2012/4/27 Henrique Ordine :
> Hi everybody,
>
> I'm trying to deploy my Maven Web App on my local Tomcat using the
> tomcat:deploy maven plugin, but the Manager application fails with a
> response code 401.
>
> I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage to
> access my Tomcat/manager app with the user "hordine", that I configured and
> deploy
>
> I've configured my tomcat-users.xml, settings.xml, and POM files, like this:
>
> I've added this user to my tomcat-users.xml:
>  
>  
>  
>  
>  
>  
>
>
> I've added this server to my settings.xml:
> 
>    
>        hordineLocalTomcat
>        hordine
>        hordine
>    
> 
>
> And I've configured my POM like this:
>
> 
>
> hTask-web
>
>  
>
>  
>
>  
>
>         org.apache.tomcat.maven
>
>           tomcat-maven-plugin
>
>           1.1

Sure of that 

But to test if your issue is fixed in trunk try 2.0-SNAPSHOT

see mojo declaration and repositories here:
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html

>
>           
>
>   http://localhost:8080/manager
>
>   hordineLocalTomcat
>
>   /hTask-web
>
>  
>
>  
>
>  
>
>  
>
> 
>
>
> I'd appreciate any help.
>
> This is the entire error's stack trace:
>
> Embedded error: Server returned HTTP response code: 401 for URL:
> http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> [INFO]
> 
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke
> Tomcat manager
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke
> Tomcat manager
> at
> org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:149)
> at
> org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:70)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> ... 17 more
> Caused by: java.io.IOException: Server returned HTTP response code: 401 for
> URL: http://localhost:8080/manager/deploy?path=%2FhTask-web&war=
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1196)
> at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:604)
> at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java:662)
> at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:295)
> at
> org.codehaus.mojo.tomcat.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:85)
> at
> org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:85)
> at
> org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:141)
> ... 20 more
>
>
> --
> Henrique Ordine
>
> http://hordine.wordpress.com/



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org