tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin with version scheme in for operations non dependent on the tomcat version
Date Fri, 25 Nov 2011 15:49:39 GMT

    [ 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


Mime
View raw message