Actually, I have to take back what I said: it does happen with Cargo as well. Here's the weird thing:
I can remotely deploy using Maven from my Windows desktop to the server, but it fails when I deploy from Hudson, which resides on the same server, but is on a different JVM. leojhartiv wrote: > > My tomcat-users looks like this: > > <role rolename="manager"/> > <role rolename="admin"/> > > <user username="adminUser" password="adminPassword" > roles="admin,manager"/> > > I am able to sign in via the HTML manager and I am able to deploy remotely > via the Maven Cargo plugin, so the problem seems to reside in the Tomcat > plugin. > > > > > mgenov wrote: >> >> Hello, I think that your problem is in tomcat's configuration. >> >> Here is the configuration that I'm using in one of my projects ( note: >> conf/tomcat-users.xml ): >> <role rolename="standard"/> >> <role rolename="manager"/> >> <user username="myuser" password="mypass" roles="standard,manager"/> >> >> >> >> >> On Tue, Sep 16, 2008 at 10:00 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: >> >>> HTTP 401 is "unauthorized". I would assume your name or password are >>> incorrect, or some other similar reason. >>> >>> Check the Tomcat logs too. >>> >>> Wayne >>> >>> On Tue, Sep 16, 2008 at 10:47 AM, leojhartiv <[EMAIL PROTECTED]> wrote: >>> > >>> > Hello, >>> > >>> > I was wondering if there was anything special I need to do in order to >>> > deploy my Maven-generated WAR file to a remote tomcat instance (on >>> another >>> > server). The following config (substiture remote URL with >>> > http://localhost:8080/manager) works fine on my local desktop with a >>> local >>> > tomcat instance: >>> > >>> > mvn tomcat:deploy >>> > >>> > <build> >>> > <plugins> >>> > <plugin> >>> > <groupId>org.codehaus.mojo</groupId> >>> > <artifactId>tomcat-maven-plugin</artifactId> >>> > <configuration> >>> > <warFile> >>> > ${project.build.directory}/${project.build.finalName}.war >>> > </warFile> >>> > <update>true</update> >>> > <path>/appPath</path> >>> > <url>http://server:38080/manager</url> >>> > <username>adminUser</username> >>> > <password>adminPassword</password> >>> > </configuration> >>> > </plugin> >>> > </plugins> >>> > </build> >>> > But fails when I try to deploy remotely with the following error: >>> > [INFO] Deploying war to http://server:38080/appPath >>> > [TASKS] Scipping maven reporter: there is already a result available. >>> > [HUDSON] Archiving ...pom.xml to .../pom.xml >>> > [HUDSON] Archiving ....war to ....war >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [ERROR] BUILD ERROR >>> > [INFO] >>> > >>> ------------------------------------------------------------------------ >>> > [INFO] Cannot invoke Tomcat manager >>> > >>> > Embedded error: Server returned HTTP response code: 401 for URL: >>> > http://server:38080/manager/deploy?path=%2FappPath&war=&update=true >>> > Any ideas? Is there an additional configuration step I have to >>> incorporate? >>> > >>> > Thanks, >>> > Leo >>> > -- >>> > View this message in context: >>> http://www.nabble.com/Deploy-to-Remote-Tomcat-Instance-tp19516536p19516536.html >>> > Sent from the mojo - user mailing list archive at Nabble.com. >>> > >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe from this list, please visit: >>> > >>> > http://xircles.codehaus.org/manage_email >>> > >>> > >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> -- >> The human knowledge belongs to the world. >> >> > > -- View this message in context: http://www.nabble.com/Deploy-to-Remote-Tomcat-Instance-tp19516536p19535831.html Sent from the mojo - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
