[
https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252335#comment-13252335
]
Hudson commented on MTOMCAT-136:
--------------------------------
Integrated in TomcatMavenPlugin-mvn3.x #127 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/127/])
[MTOMCAT-136] Tomcat7-maven-plugin 2.0-beta1 and
useSeparateTomcatClassloader fails with run goal
fix issue for tomcat6 plugin too. (Revision 1325195)
[MTOMCAT-136] Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader
fails with run goal (Revision 1325194)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1325195
Files :
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1325194
Files :
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with
> run goal
> -----------------------------------------------------------------------------------
>
> Key: MTOMCAT-136
> URL: https://issues.apache.org/jira/browse/MTOMCAT-136
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.0-beta-1
> Environment: Java 1.6.0_26, Maven 3.0.4, OS X 10.7.3
> Reporter: Leigh Anderson
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> I'm trying to start a web application with 'mvn tomcat7:run'. It seems
> that with the configuration below it fails with the following error:
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli) on
> project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> I have also tried
> * 'mvn tomcat:run-war', which seems to get past this point, but then
> the application will not start because the 'additionalClasspathDir' property
> is not supported by the 'run-war' goal.
> * removing 'useSeparateTomcatClassLoader' which then doesn't load the
> Spring instrumenting class loader required to use AspectJ LTW, specified in
> context.xml. I have confirmed that I get the same 'no such archiver' error if
> I remove the context.xml, so I don't believe this to be the cause.
> Plugin configuration:
> <plugin>
> <groupId>org.apache.tomcat.maven</groupId>
> <artifactId>tomcat7-maven-plugin</artifactId>
> <version>2.0-beta-1</version>
> <configuration>
> <systemProperties>
>
> <log4j.defaultInitOverride>true</log4j.defaultInitOverride>
> <HOSTNAME>localhost</HOSTNAME>
> <port.http>9090</port.http>
> <port.https>8443</port.https>
> </systemProperties>
> <port>9090</port>
> <httpsPort>8443</httpsPort>
> <path>/</path>
> <useTestClasspath>false</useTestClasspath>
> <additionalClasspathDirs>
>
> <additionalClasspathDir>${project.basedir}/config</additionalClasspathDir>
> </additionalClasspathDirs>
>
> <useSeparateTomcatClassLoader>true</useSeparateTomcatClassLoader>
> </configuration>
> <dependencies>
> <dependency>
> <groupId>org.springframework</groupId>
>
> <artifactId>spring-instrument-tomcat</artifactId>
> <version>${spring.version}</version>
> </dependency>
> </dependencies>
> </plugin>
--
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
