[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294332#comment-13294332
]
Neale Upstone commented on MTOMCAT-60:
--------------------------------------
I'm surprised there's no comment on this, as I think it's more sane than
hijacking plugin dependencies or project dependencies and abusing <scope>
I'd also consider changing addtionalWebapps to just webapps, as for build
pipelines, we may not always want the artifact containing the tests to be WAR
packaging, and would instead be consuming built WARs for testing.
> 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>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>tomcat-maven-plugin</artifactId>
> <version>1.1-SNAPSHOT</version>
> <executions>
> <execution>
>
> <id>start-tomcat-integration-tests</id>
> <goals>
> <goal>run</goal>
> </goals>
>
> <phase>pre-integration-test</phase>
> <configuration>
> <fork>true</fork>
>
> <addContextWarDependencies>true</addContextWarDependencies>
>
> <additionalWebapps>
> <webapp>
>
> <groupId>org.springframework.samples</groupId>
>
> <artifactId>mvc-showcase</artifactId>
>
> <version>1.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
