[
https://issues.apache.org/jira/browse/MTOMCAT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157185#comment-13157185
]
Konstantin Kolinko commented on MTOMCAT-107:
--------------------------------------------
Do you always configure deploy URL explicitly?
(There is difference between Tomcat 6 and Tomcat 7 in those URLs:
"/manager/deploy" vs "/manager/text/deploy").
There might be differences in supported parameters and features as well.
Well, if there is a demand for this feature then I have no objections. Caveat
emptor.
We do not have this versioning problem in Tomcat itself, because deployer JARs
are part of certain Tomcat release.
> restore a simple tomcat plugin with version scheme in for operations non
> dependent on the tomcat version
> --------------------------------------------------------------------------------------------------------
>
> Key: MTOMCAT-107
> URL: https://issues.apache.org/jira/browse/MTOMCAT-107
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: commons-lib
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
>
> some remote operations (deploy/undeploy etc...) doesn't depend on the tomcat
> api.
> so having back a tomcat mojo can ease here instead of having tomcat6:deploy
> or tomcat7:deploy having a simple tomcat:deploy (the deploy url will be
> adjust by the user)
--
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
