You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Olivier Lamy (Created) (JIRA)" <ji...@apache.org> on 2011/11/25 15:57:40 UTC
[jira] [Created] (MTOMCAT-107) restore a simple tomcat plugin with
version scheme in for operations non dependent on the tomcat version
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin
with version scheme in for operations non dependent on the tomcat version
Posted by "Konstantin Kolinko (Commented) (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin
with version scheme in for operations non dependent on the tomcat version
Posted by "Olivier Lamy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157186#comment-13157186 ]
Olivier Lamy commented on MTOMCAT-107:
--------------------------------------
is there any way to ask tomcat in a standard url (non version dependent) to get back the version ?
http://ip:port/manager/version return tomcat version ?
> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin
with version scheme in for operations non dependent on the tomcat version
Posted by "Glen Mazza (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157201#comment-13157201 ]
Glen Mazza commented on MTOMCAT-107:
------------------------------------
For the Mavenized tomcat-deployed samples I work on, the Maven Tomcat plugin is nice because you don't have to tell users to keep manually copying-and-pasting the WAR to the webapps directory, just use mvn tomcat:redeploy, etc. However, at any given point in time there's usually two versions of Tomcat in use--the "common one" (presently Tomcat 6) and the "new one" (Tomcat 7). It's helpful for users if (a) the poms can easily support either version, and also (b) from a documentation maintenance persepective, if the instructions can be written in a manner independent of the version of tomcat in use (e.g., "run tomcat:deploy" instead of "run either tomcat6:deploy or tomcat7:deploy", the latter instruction needing further updating when the docs need to switch from TC6&7 to TC7&8.
With the Codehaus plugin, (a) is handled by telling people up-front to configure the correct URL (based on the version of Tomcat in use and also the correct hostname, etc.), such as here:
http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samples/wsdl_first/pom.xml?revision=1196705&view=markup#l57
Alternatively, defaulting to a specific Tomcat version but allowing users having users specify a "-PTomcatX" profile for the lesser-used (non-default) Tomcat version, like so:
https://github.com/Talend/tsf/blob/master/examples/jaxws-cxf-sts/war/pom.xml#L26
Once done, system documentation just needs to tell users to run tomcat:deploy, tomcat:undeploy, etc., and won't need changing regardless of Tomcat version.
With the new Apache Tomcat plugin I can still do (a) similar to above but a little bit more complex (will just need to explicitly list two plugins and tell users to update per their specific version of Tomcat accordingly), but no real solution for (b). Still survivable without (b), but for users doing nothing more than tomcat:deploy/undeploy/redeploy, a generic tomcat mojo makes system and tutorial documentation easier to read and less to maintain.
> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin
with version scheme in for operations non dependent on the tomcat version
Posted by "Konstantin Kolinko (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MTOMCAT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157192#comment-13157192 ]
Konstantin Kolinko commented on MTOMCAT-107:
--------------------------------------------
Version is something that can be configured by Administrator, or by a vendor. It is not reliable.
> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org