Apache Tomcat Maven Plugin
  1. Apache Tomcat Maven Plugin
  2. MTOMCAT-130

finalName doesn't seem to be used when using mvn tomcat:deploy or configuration is ignored?

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not a Problem
    • Affects Version/s: 2.0-beta-1
    • Fix Version/s: None
    • Component/s: tomcat6
    • Labels:
      None
    • Environment:
      MacOSX, Java6

      Description

      Maybe I'm missing something basic, so sorry if this is the wrong place to post this, but I have a finalName set that is defined and a typical mvn clean install builds the war file just fine using the finalName. However, when I run mvn tomcat:deploy, it seems to ignore the finalName that is set. I'm thinking the issue might be that the configuration seems to be ignored since I also have update set to true in the configuration and doing mvn tomcat:deploy isn't undeploying the old application even though I have update set to true.

      Here is the snippet of relevant info:

      <build>
      <finalName>my-app</finalName>
      <plugin>
      <groupId>org.apache.tomcat.maven</groupId>
      <artifactId>tomcat6-maven-plugin</artifactId>
      <version>2.0-beta-1</version>
      <configuration>
      <update>true</update>
      <warFile>$

      {project.build.directory}

      /$

      {project.build.finalName}

      .war</warFile>
      </configuration>
      </plugin>

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Olivier Lamy (*$^¨%`£)
            Reporter:
            Rick Reumann
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development