Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.0-beta-1
-
None
-
None
-
pache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000)
Maven home: /usr/share/maven
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.3", arch: "x86_64", family: "mac"
Tomcat: 6.0.35pache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000) Maven home: /usr/share/maven Java version: 1.6.0_29, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.7.3", arch: "x86_64", family: "mac" Tomcat: 6.0.35
Description
I updated from 2.0-SNAPSHOT to 2.0-beta-1 and stopped being able to deploy war files to tomcat. No changes were made to tomcat. The tomcat manager application is configured to allow access using username 'admin' and no password. The plugin configuration is:
<plugin>
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat6-maven-plugin</artifactId>
<version>2.0-beta-1</version>
<configuration>
<path>/</path>
<warFile>${project.build.directory}/${project.build.finalName}.war</warFile>
<!-- Always undeploy before deploy -->
<update>true</update>
<mode>both</mode>
<tag>Britebill</tag>
<contextFile>${project.build.directory}/${project.build.finalName}/META-INF/context.xml</contextFile>
</configuration>
</plugin>
Attachments
Attachments
Issue Links
- duplicates
-
-
- Closed
-