[jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294424#comment-13294424
]
Joerg Bellmann commented on MTOMCAT-60:
---
Wow,
It takes nearly 2 years that someone reacts to this.
But this feature was needed 2 years ago. So I decided to make my [own plugin |
http://t7mp.github.com/docu/html/ch01.html].
It lacks docmentation , [but it brings many features wee needed when I created
this issue and patch | https://github.com/t7mp]. Like multiple wars, additional
lib-dependencies, an experimental scanner to avoid restarts and
template-hacking when the tomcat-instance is running.
But the coming version of maven-tomcat-plugin looks promising with many same
features.
Cheers,
Joerg
Multiple-War-Deployment in configuration section.
-
Key: MTOMCAT-60
URL: https://issues.apache.org/jira/browse/MTOMCAT-60
Project: Apache Tomcat Maven Plugin
Issue Type: Improvement
Reporter: Joerg Bellmann
Priority: Minor
Attachments: maven-tomcat-plugin.patch.txt
When a user want to deploy multiple webapps with the plugin it uses all
project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
message at project-processing:
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.scope' for
org.springframework.samples:mvc-showcase:war must be one of [provided,
compile, runtime, test, system] but is 'tomcat'. @
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
{code}
Configuring the additional webapps in the configuration section like this for
example :
{code}
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
version1.1-SNAPSHOT/version
executions
execution
idstart-tomcat-integration-tests/id
goals
goalrun/goal
/goals
phasepre-integration-test/phase
configuration
forktrue/fork
addContextWarDependenciestrue/addContextWarDependencies
additionalWebapps
webapp
groupIdorg.springframework.samples/groupId
artifactIdmvc-showcase/artifactId
version1.0.0-BUILD-SNAPSHOT/version
contextPath/mvc-showcase2/contextPath
/webapp
/additionalWebapps
/configuration
/execution
/executions
/plugin
{code}
avoids the warnings and makes maven 3 happy.
As a plus you can configure an contextPath different from the artifactId.
This solution was inspired by the 'maven-dependency-plugin' and uses some
code-snippets from it.
Jörg Bellmann
--
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
[jira] [Comment Edited] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294424#comment-13294424
]
Joerg Bellmann edited comment on MTOMCAT-60 at 6/13/12 12:56 PM:
-
Wow,
It takes nearly 2 years that someone reacts to this.
But this feature was needed 2 years ago. So I decided to make my own plugin
(http://t7mp.github.com/docu/html/ch01.html).
It lacks docmentation, but it brings many features wee needed when I created
this issue and patch. Like multiple wars, additional lib-dependencies, an
experimental scanner to avoid restarts and template-hacking when the
tomcat-instance is running. (sources are here https://github.com/t7mp)
But the coming version of maven-tomcat-plugin looks promising with many same
features.
Cheers,
Joerg
was (Author: mtomcat_jbellmann):
Wow,
It takes nearly 2 years that someone reacts to this.
But this feature was needed 2 years ago. So I decided to make my [own plugin |
http://t7mp.github.com/docu/html/ch01.html].
It lacks docmentation , [but it brings many features wee needed when I created
this issue and patch | https://github.com/t7mp]. Like multiple wars, additional
lib-dependencies, an experimental scanner to avoid restarts and
template-hacking when the tomcat-instance is running.
But the coming version of maven-tomcat-plugin looks promising with many same
features.
Cheers,
Joerg
Multiple-War-Deployment in configuration section.
-
Key: MTOMCAT-60
URL: https://issues.apache.org/jira/browse/MTOMCAT-60
Project: Apache Tomcat Maven Plugin
Issue Type: Improvement
Reporter: Joerg Bellmann
Priority: Minor
Attachments: maven-tomcat-plugin.patch.txt
When a user want to deploy multiple webapps with the plugin it uses all
project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
message at project-processing:
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.scope' for
org.springframework.samples:mvc-showcase:war must be one of [provided,
compile, runtime, test, system] but is 'tomcat'. @
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
{code}
Configuring the additional webapps in the configuration section like this for
example :
{code}
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
version1.1-SNAPSHOT/version
executions
execution
idstart-tomcat-integration-tests/id
goals
goalrun/goal
/goals
phasepre-integration-test/phase
configuration
forktrue/fork
addContextWarDependenciestrue/addContextWarDependencies
additionalWebapps
webapp
groupIdorg.springframework.samples/groupId
artifactIdmvc-showcase/artifactId
version1.0.0-BUILD-SNAPSHOT/version
contextPath/mvc-showcase2/contextPath
/webapp
/additionalWebapps
/configuration
/execution
/executions
/plugin
{code}
avoids the warnings and makes maven 3 happy.
As a plus you can configure an contextPath different from the artifactId.
This solution was inspired by the 'maven-dependency-plugin' and uses some
code-snippets from it.
Jörg Bellmann
--
This
[jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13294598#comment-13294598
]
Joerg Bellmann commented on MTOMCAT-60:
---
Ok,
you can find some example-configurations at https://github.com/t7mp/examples.
If you have any improvements or ideas feel free to put it on the issue-tracker.
If you think there is a bug in the plugin use the issue-tracker, we have no
strict roadmap and milestones and releases are possible on the fly if needed.
Cheers
Joerg
Multiple-War-Deployment in configuration section.
-
Key: MTOMCAT-60
URL: https://issues.apache.org/jira/browse/MTOMCAT-60
Project: Apache Tomcat Maven Plugin
Issue Type: Improvement
Reporter: Joerg Bellmann
Priority: Minor
Attachments: maven-tomcat-plugin.patch.txt
When a user want to deploy multiple webapps with the plugin it uses all
project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
message at project-processing:
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
[WARNING] 'dependencies.dependency.scope' for
org.springframework.samples:mvc-showcase:war must be one of [provided,
compile, runtime, test, system] but is 'tomcat'. @
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
{code}
Configuring the additional webapps in the configuration section like this for
example :
{code}
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
version1.1-SNAPSHOT/version
executions
execution
idstart-tomcat-integration-tests/id
goals
goalrun/goal
/goals
phasepre-integration-test/phase
configuration
forktrue/fork
addContextWarDependenciestrue/addContextWarDependencies
additionalWebapps
webapp
groupIdorg.springframework.samples/groupId
artifactIdmvc-showcase/artifactId
version1.0.0-BUILD-SNAPSHOT/version
contextPath/mvc-showcase2/contextPath
/webapp
/additionalWebapps
/configuration
/execution
/executions
/plugin
{code}
avoids the warnings and makes maven 3 happy.
As a plus you can configure an contextPath different from the artifactId.
This solution was inspired by the 'maven-dependency-plugin' and uses some
code-snippets from it.
Jörg Bellmann
--
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
