[
http://jira.codehaus.org/browse/MTOMCAT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251467#action_251467
]
Ryan Connolly commented on MTOMCAT-74:
--------------------------------------
I do understand the desire to be able to get the same functionality strictly
from CLI but my original intents are explained in more detail below.
What I would like to do here is to take advantage of the existing
addContextWarDependencies feature that is present in the 1.1 plugin except that
I want it to look at the plugin dependencies instead of the project
dependencies. I chose this route so that the existing
addContextWarDependencies feature is left functioning the way it did before I
touched the source code and to also give the user an option to instead have the
plugin look only at war dependencies configured in the plugin dependencies.
A more specific example use case is this: I have a portal application that has
been released to our internal nexus repo and I would like for my team to be
able to take advantage of the rapid development that the tomcat:run goal offers
while developing their portlets. As the portlet needs the portal war running
in the same container and the functionality already existed in the plugin
(almost in entirety) I thought this would be the logical route to take for this
feature. With this patch, users may now choose to deploy just plugin
dependencies, just project dependencies, or both project and plugin dependency
wars to the container.
Another advantage of this patch over what you've proposed above is that it
would seem your suggestion only supports the deployment of a single artifact
(-DwarArtifact) whereas the existing solution allows for any number of war
dependencies to run alongside the current war project in the embedded container.
I hope this clarifies a bit more what I am after and why I thought this was the
right way to go with this change. I look forward to hearing your thoughts on
this.
Thanks!
> Deploy war type plugin dependencies with tomcat:run
> ---------------------------------------------------
>
> Key: MTOMCAT-74
> URL: http://jira.codehaus.org/browse/MTOMCAT-74
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: all
> Reporter: Ryan Connolly
> Attachments: tomcat-run-pluginDependency-war-deployment.patch
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> It would be nice to be able to run a war file in the embedded container
> alongside the current war project being developed. As
> addContextWarDependencies only looks at project dependencies and not those
> configured as plugin dependencies it may be worthwhile to add another option
> for deploying these types: addContextWarPluginDependencies.
> An example configuration may resemble the following:
> {code:language=xml}
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>tomcat-maven-plugin</artifactId>
> <configuration>
> <addContextWarPluginDependencies>true</addContextWarPluginDependencies>
> <path>/</path>
> </configuration>
> <dependencies>
> <dependency>
> <groupId>my.groupId</groupId>
> <artifactId>mywar-artifact</artifactId>
> <version>1.0</version>
> <type>war</type>
> </dependency>
> </dependencies>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
