finalName doesn't seem to be used when using mvn tomcat:deploy or configuration
is ignored?
-------------------------------------------------------------------------------------------
Key: MTOMCAT-130
URL: https://issues.apache.org/jira/browse/MTOMCAT-130
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat6
Affects Versions: 2.0-beta-1
Environment: MacOSX, Java6
Reporter: Rick Reumann
Assignee: Olivier Lamy
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>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
