[
https://issues.apache.org/jira/browse/MTOMCAT-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MTOMCAT-163:
--------------------------------
Attachment: MTOMCAT-163__No_undeploy_goal.diff
Patch with undeploy mojo for tomcat7-m-p + usage of /manager/text in
AbstractCatalinaMojo (not the best way to do it FMHO).
> No undeploy goal
> ----------------
>
> Key: MTOMCAT-163
> URL: https://issues.apache.org/jira/browse/MTOMCAT-163
> Project: Apache Tomcat Maven Plugin
> Issue Type: New Feature
> Components: tomcat7
> Affects Versions: 2.0-beta-1
> Reporter: Tony Chemit
> Assignee: Olivier Lamy (*$^¨%`£)
> Attachments: MTOMCAT-163__No_undeploy_goal.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> in tomcat6-m-p there is a undeploy goal but no more in tomcat7 plugin.
> I understand that undeploy function is now no more accessible via the
> /manager/html but only via the /manager/text.
> I see one problem to fix this :
> - The manager url (via the AbstractCatalinaMojo#url field) is common to all
> mojo and by default is setted to /manager/html.
> Should we use instead two fields :
> - one for tomcat manager url (http://localhost:8080/manager) (common to all
> mojo)
> - one for type of manager to use html in some mojo case, text in other cases ?
--
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: [email protected]
For additional commands, e-mail: [email protected]
