[jira] [Commented] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
[
https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13252312#comment-13252312
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-136:
more details I need: do you have a dependency of type war in your project ?
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
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
version2.0-beta-1/version
configuration
systemProperties
log4j.defaultInitOverridetrue/log4j.defaultInitOverride
HOSTNAMElocalhost/HOSTNAME
port.http9090/port.http
port.https8443/port.https
/systemProperties
port9090/port
httpsPort8443/httpsPort
path//path
useTestClasspathfalse/useTestClasspath
additionalClasspathDirs
additionalClasspathDir${project.basedir}/config/additionalClasspathDir
/additionalClasspathDirs
useSeparateTomcatClassLoadertrue/useSeparateTomcatClassLoader
/configuration
dependencies
dependency
groupIdorg.springframework/groupId
artifactIdspring-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
[jira] [Commented] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
[
https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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=revrev=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=revrev=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
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
version2.0-beta-1/version
configuration
systemProperties
log4j.defaultInitOverridetrue/log4j.defaultInitOverride
HOSTNAMElocalhost/HOSTNAME
port.http9090/port.http
port.https8443/port.https
/systemProperties
port9090/port
httpsPort8443/httpsPort
path//path
useTestClasspathfalse/useTestClasspath
additionalClasspathDirs
additionalClasspathDir${project.basedir}/config/additionalClasspathDir
/additionalClasspathDirs
useSeparateTomcatClassLoadertrue/useSeparateTomcatClassLoader
/configuration
dependencies
dependency
groupIdorg.springframework/groupId
artifactIdspring-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
[jira] [Commented] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13251458#comment-13251458 ] Leigh Anderson commented on MTOMCAT-136: [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] org.apache.maven.lifecycle.LifecycleExecutionException: 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'. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: No such archiver: 'jar'. at org.apache.tomcat.maven.plugin.tomcat7.run.RunMojo.createWebappLoader(RunMojo.java:277) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.createContext(AbstractRunMojo.java:415) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:719) at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:353) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.tomcat.maven.common.run.TomcatRunException: No such archiver: 'jar'. at org.apache.tomcat.maven.common.run.DefaultClassLoaderEntriesCalculator.calculateClassPathEntries(DefaultClassLoaderEntriesCalculator.java:184) at org.apache.tomcat.maven.plugin.tomcat7.run.RunMojo.createWebappLoader(RunMojo.java:232) ... 24 more Caused by: org.codehaus.plexus.archiver.manager.NoSuchArchiverException: No such archiver: 'jar'. at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:77) at org.apache.tomcat.maven.common.run.DefaultClassLoaderEntriesCalculator.calculateClassPathEntries(DefaultClassLoaderEntriesCalculator.java:146) ... 25 more 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
[jira] [Commented] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
[
https://issues.apache.org/jira/browse/MTOMCAT-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13247266#comment-13247266
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-136:
can you paste running mvn -e ?
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
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
version2.0-beta-1/version
configuration
systemProperties
log4j.defaultInitOverridetrue/log4j.defaultInitOverride
HOSTNAMElocalhost/HOSTNAME
port.http9090/port.http
port.https8443/port.https
/systemProperties
port9090/port
httpsPort8443/httpsPort
path//path
useTestClasspathfalse/useTestClasspath
additionalClasspathDirs
additionalClasspathDir${project.basedir}/config/additionalClasspathDir
/additionalClasspathDirs
useSeparateTomcatClassLoadertrue/useSeparateTomcatClassLoader
/configuration
dependencies
dependency
groupIdorg.springframework/groupId
artifactIdspring-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
