maven sakai:deploy does not respect finalName in build

Description

Currently in the maven2 build if you set a finalName tag, the sakai:deploy phase doesn't respect finalName.

Example:

I have in my POM:

<artifactId>smartsite-guest-extapp</artifactId>
...
<build>
<finalName>RegisterGuest</finalName>
...
</build>

When deploying, it ends up:

[INFO] Copy /home/sakai/ucd-src/sakai/dev_work/trunk.guest/ucd-guest/ucd-guest-extapp/target/RegisterGuest.war to /home/sakai/tomcat-staging/webapps/smartsite-guest-extapp.war

It seems like it should respect that finalName has been changed and use that as its deployment name as opposed to overriding it...

Activity

Matthew Jones October 6, 2009 at 1:54 PM

You can use deployId as described in to accomplish this.

kohlja December 12, 2008 at 9:07 AM

I had the same problem, looks like the latest version of the tomcat-maven-plugin
no longer respects the config form:

<build>
<finalName>foo</finalName>
</build>

But, the alternate context path config works, as specified in the doc at:

http://mojo.codehaus.org/tomcat-maven-plugin/configuration.html

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>tomcat-maven-plugin</artifactId>
<configuration>
<path>/foo</path>
</configuration>
</plugin>

Note: the preceding "/" before the "foo" is important and necessary.

Enjoy!
Jeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeem

Duplicate

Details

Assignee

Reporter

Components

Affects versions

Priority

Created April 2, 2008 at 4:16 PM
Updated January 6, 2010 at 4:25 PM
Resolved October 6, 2009 at 1:54 PM