I found the cause why the plugin was not showing up in the post build actions list:
I'm doing the maven build in Eclipse and found a blog post that automatic builds must be disabled under Eclipse because it interferes with the manifest generation.

http://gis-blog.leonde.de/index.php/2012/02/19/debugging-jenkins-plugins/

The plugin is working now but I still have to adjust the Hostname / URL properties of Cargo for the Tomcat manager interface.
I thought the new Cargo version would automatically set the appropriate path based on GeneralPropertySet.HOSTNAME and Tomcat version, but seems so it doesn't (or I'm still missing something...).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to