Maven 2.x Tomcat Plugin

Fix documentation as MTOMCAT-4 forces users to use the path configuration instead of just setting the finalName node in the pom

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-beta-1
  • Fix Version/s: 1.0
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

MTOMCAT-4 'breaks' what the documentation says in regards to overriding the finalName to set the war name:
http://mojo.codehaus.org/tomcat-maven-plugin/usage.html

section
Using a different context path

The only way to do this now is to override the path in configuration like this:
<configuration>
<path>/mycontext</path>
</configuration>

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Louis Letourneau added a comment -

The workaround is actually this:

<configuration>
<path>/${project.build.finalName}</path>
</configuration>

Show
Louis Letourneau added a comment - The workaround is actually this: <configuration> <path>/${project.build.finalName}</path> </configuration>
Hide
Permalink
Olivier Lamy added a comment -

Documentation fixed.

Show
Olivier Lamy added a comment - Documentation fixed.
Hide
Permalink
Dennis Lundberg added a comment -

The documentation is still not correct. I will fix it, once I hear more from Mark about the solution for TOMCAT-4.

Show
Dennis Lundberg added a comment - The documentation is still not correct. I will fix it, once I hear more from Mark about the solution for TOMCAT-4.
Hide
Permalink
Dennis Lundberg added a comment -

I made additional fixes to the documentation in r11994.

Show
Dennis Lundberg added a comment - I made additional fixes to the documentation in r11994.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.