[ https://issues.apache.org/jira/browse/MTOMCAT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478775#comment-13478775 ]
Sergio Fernández commented on MTOMCAT-181: ------------------------------------------ You can reproduce the issue with any webapp which uses the plugin. This setup is quite common with other plugins, such as jetty: http://stackoverflow.com/questions/8685970/setting-root-context-path-with-maven-jetty-plugin#8880979 In my case, the issue is raised by the LMF webapp: https://code.google.com/p/lmf/source/browse/lmf-webapp/pom.xml?name=mavenized#40 Therefore, we can provide support for testing the implementation of such feature. > Allow to run the webapp under the root context > ---------------------------------------------- > > Key: MTOMCAT-181 > URL: https://issues.apache.org/jira/browse/MTOMCAT-181 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat7 > Reporter: Sergio Fernández > Assignee: Olivier Lamy (*$^¨%`£) > Priority: Minor > Fix For: moreinfo > > > Right now the plugin simply ignores this: > <plugin> > <groupId>org.apache.tomcat.maven</groupId> > <artifactId>tomcat7-maven-plugin</artifactId> > <version>2.0</version> > <configuration> > <path>/</path> > </configuration> > </plugin> > and take the artifactId as default context path. > Would be possible to run it under the root context? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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