I have successfully used the Deploy plugin (over a year ago) in a different environment, but am having some issues today... I'm using the most current build of Jenkins and all plugins up-to date, running on RHEL... This is a muli-module maven-based project... and the WAR is being deployed successfully to my Tomcat7 instance... The problem is -- it is not being deployed with the proper context...
Using the finalName tag, the WAR file is created with the proper name ( MyService.war for example) I would expect it to be deployed as http://host/MyService. Unfortunately, it appears to be picking up the name of the Maven sub-project's "artifact-id"... I have changed the artifact-id, to see if that was where it was coming from, but it seem to have no effect. I don't have that name specified in any context.xml files, etc... I looked in the plug-code, it looks like a change was made which allows the context path to be specified - but it does not appear to be exposed in any jelly files... Can anyone explain where this name is coming from.... or is the a plan to allow the context to be provided.... it seems like cargo does allow it... Thanks for any help. Phil
