[Bug 55737] JVM crash with GzipOutputFilter
https://issues.apache.org/bugzilla/show_bug.cgi?id=55737 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Mark Thomas --- That is a JVM crash, not a Tomcat crash. You should report it to your JVM vendor. As a work-around, you should be able avoid the JVM bug by disabling compression. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 55737] JVM crash with GzipOutputFilter
https://issues.apache.org/bugzilla/show_bug.cgi?id=55737 --- Comment #2 from wojtek --- No doubt this is a JVM crash. I have reported this to Oracle. Thank you for the workaround. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1538483 - in /tomcat/maven-plugin/trunk: tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomca
Author: olamy Date: Mon Nov 4 01:09:59 2013 New Revision: 1538483 URL: http://svn.apache.org/r1538483 Log: [MTOMCAT-224] Tomcat Maven Plugin is not marked @threadSafe Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployOnlyMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ExplodedMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/InplaceMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ListMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployOnlyMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ReloadMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ResourcesMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RolesMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarOnlyMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ServerInfoMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/SessionsMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ShutdownMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StartMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StopMojo.java tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/UndeployMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployOnlyMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployOnlyMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/UndeployMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarOnlyMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ShutdownMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarMojo.java tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarOnlyMojo.java Modified: tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java?rev=1538483&r1=1538482&r2=1538483&view=diff == --- tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java (original) +++ tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java Mon Nov 4 01:09:59 2013 @@ -28,7 +28,7 @@ import org.apache.maven.plugins.annotati * * @author Mark Hobson */ -@Mojo( name = "deploy" ) +@Mojo( name =
[jira] [Closed] (MTOMCAT-224) Tomcat Maven Plugin is not marked @threadSafe
[ https://issues.apache.org/jira/browse/MTOMCAT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-224. -- Resolution: Fixed Fix Version/s: 2.2 > Tomcat Maven Plugin is not marked @threadSafe > - > > Key: MTOMCAT-224 > URL: https://issues.apache.org/jira/browse/MTOMCAT-224 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6 >Affects Versions: 2.1 >Reporter: Diego Lemos >Assignee: Olivier Lamy (*$^¨%`£) > Labels: build, maven > Fix For: 2.2 > > > When tomcat6-maven-plugin is used in a parallel build, maven says that the > plugin is not thread-safe : > [WARNING] * > [WARNING] * Your build is requesting parallel execution, but project * > [WARNING] * contains the following plugin(s) that are not marked as * > [WARNING] * @threadSafe to support parallel building. * > [WARNING] * While this /may/ work fine, please look for plugin updates* > [WARNING] * and/or request plugins be made thread-safe. * > [WARNING] * If reporting an issue, report it against the plugin in* > [WARNING] * question, not against maven-core * > [WARNING] * > [WARNING] The following plugins are not marked @threadSafe in #: > [WARNING] org.apache.tomcat.maven:tomcat6-maven-plugin:2.1 > [WARNING] * > It will be nice to review the plugin to ensure that it is thread-safe and add > a @threadSafe annotation to it. > More details about the parallel builds: > https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-220) Tomcat does not stop listening to given port
[ https://issues.apache.org/jira/browse/MTOMCAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812559#comment-13812559 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-220: are you triggering shutdown mojo at the end of your integration tests? > Tomcat does not stop listening to given port > > > Key: MTOMCAT-220 > URL: https://issues.apache.org/jira/browse/MTOMCAT-220 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.1 > Environment: java 7; maven 3.0.5; ubuntu 12.10 (quantal) 64-bit >Reporter: Aivaras Ruzveltas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: moreinfo > > > We have a multimodule Maven project containing many WAR applications: > . > ├── Parent > ├── ChildWar1 > ├── ChildWar2 > └── ... > We want to run integration tests for all of those WAR modules. But after > Tomcat is shutdown (shutdown MOJO at post-integration-test) first module, > main JVM keeps listening to specified port (lsof -i TCP:18082) and when > Tomcat is being started for second WAR module it fails with output: > [INFO] --- tomcat7-maven-plugin:2.1:run-war-only (start-tomcat7) @ ChildWar2 > --- > [INFO] Running war on http://localhost:18082/ChildWar2 > [INFO] Creating Tomcat server configuration at > /somedir/ChildWar2/target/tomcat > [INFO] create webapp with contextPath: /ChildWar2 > Apr 18, 2013 4:36:02 PM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-18082"] > Apr 18, 2013 4:36:02 PM org.apache.coyote.AbstractProtocol init > SEVERE: Failed to initialize end point associated with ProtocolHandler > ["http-bio-18082"] > java.net.BindException: Address already in use :18082 > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:981) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139) > at org.apache.catalina.startup.Tomcat.start(Tomcat.java:335) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1091) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:512) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > 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:88) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > 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.plex
[jira] [Updated] (MTOMCAT-220) Tomcat does not stop listening to given port
[ https://issues.apache.org/jira/browse/MTOMCAT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-220: --- Fix Version/s: moreinfo > Tomcat does not stop listening to given port > > > Key: MTOMCAT-220 > URL: https://issues.apache.org/jira/browse/MTOMCAT-220 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.1 > Environment: java 7; maven 3.0.5; ubuntu 12.10 (quantal) 64-bit >Reporter: Aivaras Ruzveltas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: moreinfo > > > We have a multimodule Maven project containing many WAR applications: > . > ├── Parent > ├── ChildWar1 > ├── ChildWar2 > └── ... > We want to run integration tests for all of those WAR modules. But after > Tomcat is shutdown (shutdown MOJO at post-integration-test) first module, > main JVM keeps listening to specified port (lsof -i TCP:18082) and when > Tomcat is being started for second WAR module it fails with output: > [INFO] --- tomcat7-maven-plugin:2.1:run-war-only (start-tomcat7) @ ChildWar2 > --- > [INFO] Running war on http://localhost:18082/ChildWar2 > [INFO] Creating Tomcat server configuration at > /somedir/ChildWar2/target/tomcat > [INFO] create webapp with contextPath: /ChildWar2 > Apr 18, 2013 4:36:02 PM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-18082"] > Apr 18, 2013 4:36:02 PM org.apache.coyote.AbstractProtocol init > SEVERE: Failed to initialize end point associated with ProtocolHandler > ["http-bio-18082"] > java.net.BindException: Address already in use :18082 > at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:406) > at > org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610) > at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429) > at > org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119) > at > org.apache.catalina.connector.Connector.initInternal(Connector.java:981) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardService.initInternal(StandardService.java:559) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at > org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139) > at org.apache.catalina.startup.Tomcat.start(Tomcat.java:335) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1091) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:512) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > 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:88) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > 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: java.net.BindException: Addres
svn commit: r1538487 [2/13] - in /tomcat/site/trunk/docs/maven-plugin-trunk: ./ apidocs/ apidocs/org/apache/tomcat/maven/common/config/ apidocs/org/apache/tomcat/maven/common/deployer/class-use/ apido
Modified: tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.html (original) +++ tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.html Mon Nov 4 01:36:24 2013 @@ -102,7 +102,8 @@ Class ExecWarMojo -http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/maven.plugins.annotations.Mojo.html?is-external=true"; title="class or interface in org.apache">@Mojo(name="exec-war") +http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/maven.plugins.annotations.Mojo.html?is-external=true"; title="class or interface in org.apache">@Mojo(name="exec-war", + threadSafe=true) http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/maven.plugins.annotations.Execute.html?is-external=true"; title="class or interface in org.apache">@Execute(phase=PACKAGE) public class ExecWarMojoextends AbstractExecWarMojo @@ -139,7 +140,7 @@ Create a self executable jar file contai Fields inherited from class org.apache.tomcat.maven.plugin.tomcat7.run.AbstractExecWarMojo -accessLogValveFormat, artifactFactory, artifactResolver, attachArtifact, attachArtifactClassifier, attachArtifactClassifierType, bui ldDirectory, connectorHttpProtocol, enableNaming, extraDependencies, extraResources, finalName, local, mainClass, path, pluginArtifacts, project, projectArtifact, projectHelper, remoteRepos, serverXml, tomcatConfigurationFilesDirectory, warRunDependencies +accessLogValveFormat, artifactFactory, artifactResolver, attachArtifact, attachArtifactClassifier, attachArtifactClassifierType, bui ldDirectory, connectorHttpProtocol, enableNaming, extraDependencies, extraResources, finalName, httpPort, local, mainClass, path, pluginArtifacts, project, projectArtifact, projectHelper, remoteRepos, serverXml, tomcatConfigurationFilesDirectory, warRunDependencies Modified: tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.html (original) +++ tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.html Mon Nov 4 01:36:24 2013 @@ -102,7 +102,8 @@ Class ExecWarOnlyMojo -http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/maven.plugins.annotations.Mojo.html?is-external=true"; title="class or interface in org.apache">@Mojo(name="exec-war-only") +http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/maven.plugins.annotations.Mojo.html?is-external=true"; title="class or interface in org.apache">@Mojo(name="exec-war-only", + threadSafe=true) public class ExecWarOnlyMojoextends AbstractExecWarMojo @@ -135,7 +136,7 @@ Same as exec-war goal without forking th Fields inherited from class org.apache.tomcat.maven.plugin.tomcat7.run.AbstractExecWarMojo -accessLogValveFormat, artifactFactory, artifactResolver, attachArtifact, attachArtifactClassifier, attachArtifactClassifierType, bui ldDirectory, connectorHttpProtocol, enableNaming, extraDependencies, extraResources, finalName, local, mainClass, path, pluginArtifacts, project, projectArtifact, projectHelper, remoteRepos, serverXml, tomcatConfigurationFilesDirectory, warRunDependencies +accessLogValveFormat, artifactFactory, artifactResolver, attachArtifact, attachArtifactClassifier, attachArtifactClassifierType, bui ldDirectory, connectorHttpProtocol, enableNaming, extraDependencies, extraResources, finalName, httpPort, local, mainClass, path, pluginArtifacts, project, projectArtifact, projectHelper, remoteRepos, serverXml, tomcatConfigurationFilesDirectory, warRunDependencies Modified: tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/apidocs/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.html (original) +++ tomcat/sit
svn commit: r1538487 [8/13] - in /tomcat/site/trunk/docs/maven-plugin-trunk: ./ apidocs/ apidocs/org/apache/tomcat/maven/common/config/ apidocs/org/apache/tomcat/maven/common/deployer/class-use/ apido
Modified: tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-mojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-mojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-mojo.html (original) +++ tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-mojo.html Mon Nov 4 01:36:24 2013 @@ -7,7 +7,7 @@ - + Apache Tomcat Maven Plugin :: Tomcat 7.x - tomcat7:run-war @@ -193,7 +193,7 @@ - | Last Published: 01 November 2013 + | Last Published: 03 November 2013 Version: 2.2-SNAPSHOT @@ -227,6 +227,8 @@ embedded Tomcat server. Requires dependency resolution of artifacts in scope: runtime. +The goal is thread-safe and supports parallel builds. + Since version: 2.0. Invokes the execution of the http://maven.apache.org/ref/current/maven-core/lifecycles.html";>lifecycle phase package prior to executing itself. @@ -806,7 +808,9 @@ will be created to start tomcat.2.0 -(no description) +Collection of webapp artifacts to be deployed. Elements are +and contain usual GAVC plus contextPath and/or +contextFile elements. @@ -1511,7 +1515,9 @@ will be created to start tomcat. webapps: -(no description) +Collection of webapp artifacts to be deployed. Elements are + and contain usual GAVC plus contextPath and/or +contextFile elements. Modified: tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-only-mojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-only-mojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-only-mojo.html (original) +++ tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/run-war-only-mojo.html Mon Nov 4 01:36:24 2013 @@ -7,7 +7,7 @@ - + Apache Tomcat Maven Plugin :: Tomcat 7.x - tomcat7:run-war-only @@ -193,7 +193,7 @@ - | Last Published: 01 November 2013 + | Last Published: 03 November 2013 Version: 2.2-SNAPSHOT @@ -226,6 +226,8 @@ Requires dependency resolution of artifacts in scope: runtime. +The goal is thread-safe and supports parallel builds. + Since version: 2.0. @@ -803,7 +805,9 @@ will be created to start tomcat.2.0 -(no description) +Collection of webapp artifacts to be deployed. Elements are + and contain usual GAVC plus contextPath and/or +contextFile elements. @@ -1508,7 +1512,9 @@ will be created to start tomcat. webapps: -(no description) +Collection of webapp artifacts to be deployed. Elements are + and contain usual GAVC plus contextPath and/or +contextFile elements. Modified: tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/shutdown-mojo.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/shutdown-mojo.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/shutdown-mojo.html (original) +++ tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/shutdown-mojo.html Mon Nov 4 01:36:24 2013 @@ -7,7 +7,7 @@ - + Apache Tomcat Maven Plugin :: Tomcat 7.x - tomcat7:shutdown @@ -193,7 +193,7 @@ - | Last Published: 01 November 2013 + | Last Published: 03 November 2013 Version: 2.2-SNAPSHOT @@ -233,6 +233,8 @@ phase. For integration tests you might w Requires dependency resolution of artifacts in scope: runtime. +The goal is thread-safe and supports parallel builds. + Since version: 2.0. Modified: tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/sonar.html URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-maven-plugin/sonar.html?rev=1538487&r1=1538486&r2=1538487&view=diff == --- tomcat/site/trunk/docs/maven-plugin-trun
svn commit: r1538487 [13/13] - in /tomcat/site/trunk/docs/maven-plugin-trunk: ./ apidocs/ apidocs/org/apache/tomcat/maven/common/config/ apidocs/org/apache/tomcat/maven/common/deployer/class-use/ apid
Modified:
tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-war-runner/xref/org/apache/tomcat/maven/runner/Tomcat7RunnerCli.html
URL:
http://svn.apache.org/viewvc/tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-war-runner/xref/org/apache/tomcat/maven/runner/Tomcat7RunnerCli.html?rev=1538487&r1=1538486&r2=1538487&view=diff
==
---
tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-war-runner/xref/org/apache/tomcat/maven/runner/Tomcat7RunnerCli.html
(original)
+++
tomcat/site/trunk/docs/maven-plugin-trunk/tomcat7-war-runner/xref/org/apache/tomcat/maven/runner/Tomcat7RunnerCli.html
Mon Nov 4 01:36:24 2013
@@ -148,87 +148,95 @@
138 {
139
tomcat7Runner.serverXmlPath = line.getOptionValue( serverXmlPath.getOpt() );
140 }
-141 if ( line.hasOption( httpPort.getOpt() ) )
-142 {
-143
tomcat7Runner.httpPort = Integer.parseInt( line.getOptionValue(
httpPort.getOpt() ) );
-144 }
-145
-146 if ( line.hasOption( httpsPort.getOpt() ) )
-147 {
-148
tomcat7Runner.httpsPort = Integer.parseInt( line.getOptionValue(
httpsPort.getOpt() ) );
-149 }
-150 if ( line.hasOption( ajpPort.getOpt() ) )
-151 {
-152
tomcat7Runner.ajpPort = Integer.parseInt( line.getOptionValue( ajpPort.getOpt()
) );
-153 }
-154 if ( line.hasOption( resetExtract.getOpt() ) )
+141
+142 String port =
tomcat7Runner.runtimeProperties.getProperty( Tomcat7Runner.HTTP_PORT_KEY );
+143 if ( port != null)
+144 {
+145
tomcat7Runner.httpPort = Integer.parseInt( port );
+146 }
+147
+148 // cli win for the port
+149 if ( line.hasOption( httpPort.getOpt() ) )
+150 {
+151
tomcat7Runner.httpPort = Integer.parseInt( line.getOptionValue(
httpPort.getOpt() ) );
+152 }
+153
+154 if ( line.hasOption( httpsPort.getOpt() ) )
155 {
-156
tomcat7Runner.resetExtract = true;
+156
tomcat7Runner.httpsPort = Integer.parseInt( line.getOptionValue(
httpsPort.getOpt() ) );
157 }
-158 if ( line.hasOption( debug.getOpt() ) )
+158 if ( line.hasOption( ajpPort.getOpt() ) )
159 {
-160
tomcat7Runner.debug = true;
+160
tomcat7Runner.ajpPort = Integer.parseInt( line.getOptionValue( ajpPort.getOpt()
) );
161 }
-162
-163 if ( line.hasOption( httpProtocol.getOpt() ) )
-164 {
-165
tomcat7Runner.httpProtocol = line.getOptionValue( httpProtocol.getOpt() );
-166 }
-167
-168 if ( line.hasOption( sysProps.getOpt() ) )
-169 {
-170
Properties systemProperties = line.getOptionProperties( sysProps.getOpt() );
-171 if ( systemProperties != null && !systemProperties.isEmpty() )
-172 {
-173
for ( Map.Entry
sysProp : systemProperties.entrySet() )
-174 {
-175
System.setProperty( (String) sysProp.getKey(), (String) sysProp.getValue() );
-176 }
-177 }
-178 }
-179 if ( line.hasOption( clientAuth.getOpt() ) )
-180 {
-181
tomcat7Runner.clientAuth = clientAuth.getOpt();
-182 }
-183 if ( line.hasOption( keyAlias.getOpt() ) )
-184 {
-185
tomcat7Runner.keyAlias = line.getOptionValue( keyAlias.getOpt() );
+162 if ( line.hasOption( resetExtract.getOpt() ) )
+163 {
+164
tomcat7Runner.resetExtract = true;
+165 }
+166 if ( line.hasOption( debug.getOpt() ) )
+167 {
+168
tomcat7Runner.debug = true;
+169 }
+170
+171 if ( line.hasOption( httpProtocol.getOpt() ) )
+172 {
+173
tomcat7Runner.httpProtocol = line.getOptionValue( httpProtocol.getOpt() );
+174 }
+175
+176 if ( line.hasOption( sysProps.getOpt() ) )
+177 {
+178
Properties systemProperties = line.getOptionProperties( sysProps.getOpt() );
+179 if ( systemProperties != null && !systemProperties.isEmpty() )
+180 {
+181
for ( Map.Entry
sysProp : systemProperties.entrySet() )
+182 {
+183
System.setProperty( (String) sysProp.getKey(), (String) sysProp.getValue() );
+184 }
+185 }
186 }
-187
-188 if ( line.hasOption( extractDirectory.getOpt() ) )
-189 {
-190
tomcat7Runner.extractDirectory = line.getOptionValue( extractDirectory.getOpt()
);
-191 }
-192
-193 if ( line.hasOption( loggerName.getOpt() ) )
-194 {
-195
tomcat7Runner.loggerName = line.getOptionValue( loggerName.getOpt() );
-196 }
-197
-198 if ( line.hasOption( uriEncoding.ge
[jira] [Closed] (MTOMCAT-219) Web applications listed in are not accessible
[ https://issues.apache.org/jira/browse/MTOMCAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-219. -- Resolution: Not A Problem > Web applications listed in are not accessible > --- > > Key: MTOMCAT-219 > URL: https://issues.apache.org/jira/browse/MTOMCAT-219 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.1 > Environment: java 7; maven 3.0.5; ubuntu 12.10 (quantal) 64-bit >Reporter: Aivaras Ruzveltas >Assignee: Olivier Lamy (*$^¨%`£) > > Configuration: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.1 > > > > com.example > myApplication > 1.0 > war > > > > > Application: > ~/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > contains single index.html file. > Maven execution output: > [INFO] Running war on http://localhost:8080/IntegrationTests > [INFO] Creating Tomcat server configuration at > somedir/IntegrationTests/target/tomcat > [INFO] create webapp with contextPath: /IntegrationTests > [DEBUG] context reloadable: false > [INFO] Deploying dependency wars > [INFO] Deploy warfile: > /home/aivaras/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > to contextPath: /myApplication > [DEBUG] Expanding: > /home/aivaras/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > into /somedir/IntegrationTests/target/tomcat/webapps/myApplication > [DEBUG] > /somedir/IntegrationTests/target/tomcat/webapps/myApplication/index.html: > mode 100644, chmod 644 > [DEBUG] expand complete > [DEBUG] context reloadable: false > Apr 17, 2013 2:49:04 PM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-8080"] > Apr 17, 2013 2:49:05 PM org.apache.catalina.core.StandardService startInternal > INFO: Starting service Tomcat > Apr 17, 2013 2:49:05 PM org.apache.catalina.core.StandardEngine startInternal > INFO: Starting Servlet Engine: Apache Tomcat/7.0.37 > Apr 17, 2013 2:49:06 PM org.apache.coyote.AbstractProtocol start > INFO: Starting ProtocolHandler ["http-bio-8080"] > Log file contents > (/somedir/IntegrationTests/target/tomcat/logs/access_log.2013-04-17) contents > after accessing main application and dependency application: > 127.0.0.1 - - [17/Apr/2013:14:49:10 +0300] "GET /IntegrationTests/ HTTP/1.1" > 200 42 http-bio-8080-exec-1 27 > 127.0.0.1 - - [17/Apr/2013:14:49:13 +0300] "GET /myApplication/ HTTP/1.1" 404 > 949 http-bio-8080-exec-3 8 > Result: > main application is accessible > at http://localhost:8080/IntegrationTests/ > when accessing dependency application at http://localhost:8080/myApplication/ > result is Tomcat default error looking page with: > HTTP Status 404 - > type Status report > message > description The requested resource is not available. > Apache Tomcat/7.0.37 > Accessing any not existing URL, like http://localhost:8080/asdf/ gives an > empty page. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-219) Web applications listed in are not accessible
[ https://issues.apache.org/jira/browse/MTOMCAT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812564#comment-13812564 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-219: Use: com.example myApplication 1.0 war true > Web applications listed in are not accessible > --- > > Key: MTOMCAT-219 > URL: https://issues.apache.org/jira/browse/MTOMCAT-219 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.1 > Environment: java 7; maven 3.0.5; ubuntu 12.10 (quantal) 64-bit >Reporter: Aivaras Ruzveltas >Assignee: Olivier Lamy (*$^¨%`£) > > Configuration: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.1 > > > > com.example > myApplication > 1.0 > war > > > > > Application: > ~/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > contains single index.html file. > Maven execution output: > [INFO] Running war on http://localhost:8080/IntegrationTests > [INFO] Creating Tomcat server configuration at > somedir/IntegrationTests/target/tomcat > [INFO] create webapp with contextPath: /IntegrationTests > [DEBUG] context reloadable: false > [INFO] Deploying dependency wars > [INFO] Deploy warfile: > /home/aivaras/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > to contextPath: /myApplication > [DEBUG] Expanding: > /home/aivaras/.m2/repository/com/example/myApplication/1.0/myApplication-1.0.war > into /somedir/IntegrationTests/target/tomcat/webapps/myApplication > [DEBUG] > /somedir/IntegrationTests/target/tomcat/webapps/myApplication/index.html: > mode 100644, chmod 644 > [DEBUG] expand complete > [DEBUG] context reloadable: false > Apr 17, 2013 2:49:04 PM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-8080"] > Apr 17, 2013 2:49:05 PM org.apache.catalina.core.StandardService startInternal > INFO: Starting service Tomcat > Apr 17, 2013 2:49:05 PM org.apache.catalina.core.StandardEngine startInternal > INFO: Starting Servlet Engine: Apache Tomcat/7.0.37 > Apr 17, 2013 2:49:06 PM org.apache.coyote.AbstractProtocol start > INFO: Starting ProtocolHandler ["http-bio-8080"] > Log file contents > (/somedir/IntegrationTests/target/tomcat/logs/access_log.2013-04-17) contents > after accessing main application and dependency application: > 127.0.0.1 - - [17/Apr/2013:14:49:10 +0300] "GET /IntegrationTests/ HTTP/1.1" > 200 42 http-bio-8080-exec-1 27 > 127.0.0.1 - - [17/Apr/2013:14:49:13 +0300] "GET /myApplication/ HTTP/1.1" 404 > 949 http-bio-8080-exec-3 8 > Result: > main application is accessible > at http://localhost:8080/IntegrationTests/ > when accessing dependency application at http://localhost:8080/myApplication/ > result is Tomcat default error looking page with: > HTTP Status 404 - > type Status report > message > description The requested resource is not available. > Apache Tomcat/7.0.37 > Accessing any not existing URL, like http://localhost:8080/asdf/ gives an > empty page. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-183) java.lang.NoSuchMethodError: javax.xml.stream.XMLInputFactory.newFactory() error for 2.1-SNAPSHOT and 2.0-RELEASE
[ https://issues.apache.org/jira/browse/MTOMCAT-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-183. -- Resolution: Invalid Fix Version/s: (was: moreinfo) no info from user > java.lang.NoSuchMethodError: javax.xml.stream.XMLInputFactory.newFactory() > error for 2.1-SNAPSHOT and 2.0-RELEASE > -- > > Key: MTOMCAT-183 > URL: https://issues.apache.org/jira/browse/MTOMCAT-183 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 > Environment: os: win7-64x jdk: jdk1.6.0_12 maven:apache-maven-3.0.4 >Reporter: ZHANG Frank >Assignee: Olivier Lamy (*$^¨%`£) > Labels: maven > Original Estimate: 12h > Remaining Estimate: 12h > > when run tomcat7:run, errors as follow: > ... > urls[45] = > file:/C:/Users/Administrator/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar > urls[46] = > file:/C:/Users/Administrator/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar > Number of foreign imports: 1 > import: Entry[import from realm ClassRealm[maven.api, parent: null]] > - > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:139) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.apache.maven.plugin.PluginContainerException: An API > incompatibility was encountered while executing > org.apache.tomcat.maven:tomcat7-maven-plugin:2.1-SNAPSHOT:run: > java.lang.NoSuchMethodError: > javax.xml.stream.XMLInputFactory.newFactory()Ljavax/xml/stream/XMLInputFactory; > - > realm =plugin>org.apache.tomcat.maven:tomcat7-maven-plugin:2.1-SNAPSHOT > strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy > urls[0] = > file:/C:/Users/Administrator/.m2/repository/org/apache/tomcat/maven/tomcat7-maven-plugin/2.1-SNAPSHOT/tomcat7-maven-plugin-2.1-SNAPSHOT.jar > urls[1] = > file:/C:/Users/Administrator/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/7.0.32/tomcat-embed-core-7.0.32.jar > urls[2] = > file:/C:/Users/Administrator/.m2/repository/org/apache/tomcat/tomcat-util/7.0.32/tomcat-util-7.0.32.jar > ... > urls[45] = > file:/C:/Users/Administrator/.m2/repository/org/codehaus/plexus/plexus-interactivity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.jar > urls[46] = > file:/C:/Users/Administrator/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar > Number of foreign imports: 1 > import: Entry[import from realm ClassRealm[maven.api, parent: null]] > - > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) > ... 20 more > Caused by: java.lang.NoSuchMethodError: > javax.xml.stream.XMLInputFactory.newFactory()Ljavax/xml/stream/XMLInputFactory; > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.parseContextFile(AbstractRunMojo.java:589) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.createContext(AbstractRunMojo.java:539) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:929) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:478) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > [ERROR] > and when using tomcat7-maven-plugin 2.0-SNAPSHOT version. it's ok. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-146) Multiple executions of run-war-only has Valve problems at shutdown
[
https://issues.apache.org/jira/browse/MTOMCAT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-146.
--
Resolution: Won't Fix
the first shutdown already shutdown some jmx. Nothing we can really fix here.
You must configure:
true
> Multiple executions of run-war-only has Valve problems at shutdown
> --
>
> Key: MTOMCAT-146
> URL: https://issues.apache.org/jira/browse/MTOMCAT-146
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
>Affects Versions: 2.0-beta-1
>Reporter: Benson Margulies
>Assignee: Olivier Lamy (*$^¨%`£)
>
> {noformat}
> INFO: Stopping Coyote HTTP/1.1 on http-51155
> Apr 18, 2012 8:19:17 AM org.apache.catalina.core.StandardPipeline
> unregisterValve
> INFO: Can't unregister valve
> org.apache.catalina.core.StandardEngineValve[localEngine]
> javax.management.InstanceNotFoundException:
> localEngine:type=Valve,name=StandardEngineValve
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506)
> at
> org.apache.catalina.core.StandardPipeline.unregisterValve(StandardPipeline.java:322)
> at
> org.apache.catalina.core.StandardPipeline.stop(StandardPipeline.java:275)
> at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1103)
> at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:468)
> at org.apache.catalina.startup.Embedded.stop(Embedded.java:867)
> 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.apache.tomcat.maven.common.run.EmbeddedRegistry.shutdownAll(EmbeddedRegistry.java:110)
> at
> org.apache.tomcat.maven.plugin.tomcat6.ShutdownMojo.execute(ShutdownMojo.java:63)
> {noformat}
> {code}
>
> org.apache.tomcat.maven
> tomcat6-maven-plugin
> 2.0-beta-1
>
>
> tomcat-run
>
> run-war-only
>
> pre-integration-test
>
> /
> ${tomcat.port}
> UTF-8
>
> ${project.build.directory}/webapps/solr/
> true
> true
> src/test/context.xml
>
>
> ${project.build.directory}/solr_home
>
> ${project.build.directory}/bt-rni-solr3x-plugins.jar
> ../../../../..
>
>
>
>
> tomcat2-run
>
> run-war-only
>
> pre-integration-test
>
> /
> ${tomcat2.port}
> UTF-8
>
> ${project.build.directory}/webapps/solr2/
>
> ${project.build.directory}/tomcat2
> true
> true
> src/test/context.xml
>
>
> ${project.build.directory}/solr2
>
> ${project.build.directory}/bt-rni-solr3x-plugins.jar
> ../../../../..
>
>
>
>
> tomcat-shutdown
>
>
> shutdown
>
> post-integration-test
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For
[jira] [Commented] (MTOMCAT-224) Tomcat Maven Plugin is not marked @threadSafe
[ https://issues.apache.org/jira/browse/MTOMCAT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812589#comment-13812589 ] Hudson commented on MTOMCAT-224: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #263 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/263/]) [MTOMCAT-224] Tomcat Maven Plugin is not marked @threadSafe (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1538483) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ExplodedMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/InplaceMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ListMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ReloadMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ResourcesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RolesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ServerInfoMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/SessionsMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ShutdownMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StartMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StopMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/UndeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/UndeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ShutdownMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarOnlyMojo.java > Tomcat Maven Plugin is not marked @threadSafe > - > > Key: MTOMCAT-224 > URL: https://issues.apache.org/jira/browse/MTOMCAT-224 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6 >Affects Versions: 2.1 >Reporter: Diego Lemos >Assignee: Olivier Lamy (*$^¨%`£) > Labels: build, maven > Fix For: 2.2 > > > When tomcat6-maven-plugin is used in a pa
[jira] [Closed] (MTOMCAT-101) Add the ability to deploy to a Tomcat instance on the filesystem rather than via HTTP
[ https://issues.apache.org/jira/browse/MTOMCAT-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-101. -- Resolution: Won't Fix Fix Version/s: (was: backlog) There are plenty of maven plugins to copy a file to a file system structure. So you can certainly one of those. > Add the ability to deploy to a Tomcat instance on the filesystem rather than > via HTTP > - > > Key: MTOMCAT-101 > URL: https://issues.apache.org/jira/browse/MTOMCAT-101 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat6, tomcat7 >Reporter: Steve Swinsburg >Assignee: Olivier Lamy (*$^¨%`£) > > It would be great to have the ability to deploy a webapp to Tomcat without > using HTTP and the Tomcat Manager, by simply doing a filesystem copy of the > built war file to the location specified. > We currently use an ant profile to do this, but want to replace this with a > proper plugin. > We will be looking at contributing this feature in the near future. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-90) useNaming not very useful; perhaps use StandardServer to make it more useful
[ https://issues.apache.org/jira/browse/MTOMCAT-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-90: -- Fix Version/s: backlog > useNaming not very useful; perhaps use StandardServer to make it more useful > > > Key: MTOMCAT-90 > URL: https://issues.apache.org/jira/browse/MTOMCAT-90 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Benson Margulies > Fix For: backlog > > > While the Tomcat 'Embedded' class has 'useNaming', it's not useful. This is > because the rest of Tomcat won't actually set up the full JNDI foundation > unless the NamingContextListener is deployed inside of a container that > implements Server or Context. The plugin does not use StandardServer to be a > server, and nothing in the plugin will add the NamingContextListener to a > context. > One possible response here is to remove the option; another is to add > StandardServer, a third is to add that listener to the context when useNaming > is turned on. > I suppose that it's hypothetically possible for someone to use context.xml to > add the NamingContextListener. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-91) tomcat-maven-plugin hard codes INITIAL_CONTEXT
[ https://issues.apache.org/jira/browse/MTOMCAT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-91: -- Fix Version/s: backlog > tomcat-maven-plugin hard codes INITIAL_CONTEXT > -- > > Key: MTOMCAT-91 > URL: https://issues.apache.org/jira/browse/MTOMCAT-91 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Kennard Consulting > Fix For: backlog > > > Hi guys, > Thanks for a great Maven plugin in tomcat-maven-plugin. I am using it in my > Open Source project and it works really well. > I recently tried getting tomcat-maven-plugin to coexist with > jetty-maven-plugin. There is a problem that appears to sit somewhere in the > middle of the two projects, and requires both of you to agree on a solution :) > Basically tomcat-maven-plugin appears to be setting INITIAL_CONTEXT at the VM > level (whereas Jetty does not) and this means that Jetty ends up trying to > use Tomcat's JNDI implementation. It would be great if Tomcat/Jetty could > live together in a build process, so that I could run my integration tests > against multiple appservers. > Please see JETTY-1370 for an example pom.xml and an error log, and also > discussion from the jetty-maven-plugin guys about what might be 'wrong'. > Regards, > Richard. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-91) tomcat-maven-plugin hard codes INITIAL_CONTEXT
[ https://issues.apache.org/jira/browse/MTOMCAT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812594#comment-13812594 ] Olivier Lamy (*$^¨%`£) commented on MTOMCAT-91: --- need some changes in tomcat core. > tomcat-maven-plugin hard codes INITIAL_CONTEXT > -- > > Key: MTOMCAT-91 > URL: https://issues.apache.org/jira/browse/MTOMCAT-91 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Kennard Consulting > Fix For: backlog > > > Hi guys, > Thanks for a great Maven plugin in tomcat-maven-plugin. I am using it in my > Open Source project and it works really well. > I recently tried getting tomcat-maven-plugin to coexist with > jetty-maven-plugin. There is a problem that appears to sit somewhere in the > middle of the two projects, and requires both of you to agree on a solution :) > Basically tomcat-maven-plugin appears to be setting INITIAL_CONTEXT at the VM > level (whereas Jetty does not) and this means that Jetty ends up trying to > use Tomcat's JNDI implementation. It would be great if Tomcat/Jetty could > live together in a build process, so that I could run my integration tests > against multiple appservers. > Please see JETTY-1370 for an example pom.xml and an error log, and also > discussion from the jetty-maven-plugin guys about what might be 'wrong'. > Regards, > Richard. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1538501 - /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Author: olamy
Date: Mon Nov 4 04:11:44 2013
New Revision: 1538501
URL: http://svn.apache.org/r1538501
Log:
remove non used exception
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java?rev=1538501&r1=1538500&r2=1538501&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Mon Nov 4 04:11:44 2013
@@ -1412,7 +1412,7 @@ public abstract class AbstractRunMojo
private void addContextFromArtifact( Tomcat container, List
contexts, Artifact artifact,
String contextPath, File contextXml,
boolean asWebApp )
-throws MojoExecutionException, MalformedURLException,
ServletException, IOException
+throws MojoExecutionException, ServletException, IOException
{
getLog().info( "Deploy warfile: " + String.valueOf( artifact.getFile()
) + " to contextPath: " + contextPath );
File webapps = new File( configurationDir, "webapps" );
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-92) Bind tomcat to a self-chosen network interface
[ https://issues.apache.org/jira/browse/MTOMCAT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-92. - Resolution: Fixed Fix Version/s: (was: backlog) 2.2 > Bind tomcat to a self-chosen network interface > -- > > Key: MTOMCAT-92 > URL: https://issues.apache.org/jira/browse/MTOMCAT-92 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Björn Michael >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > > Tomcat is bound to 0.0.0.0 (all interfaces) by default. I feel the need to > change this binding to e.g. localhost (127.0.0.1) or another interface by > adding a 127.0.0.1 to plugin configuration in pom.xml. This is > often necessary for security or firewall reasons during the development of > web applications. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-83) Support specifying arguments using a real forked JVM
[ https://issues.apache.org/jira/browse/MTOMCAT-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-83: -- Fix Version/s: backlog > Support specifying arguments using a real forked JVM > > > Key: MTOMCAT-83 > URL: https://issues.apache.org/jira/browse/MTOMCAT-83 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Stevo Slavic > Fix For: backlog > > > [tomcat-maven-plugin's run > goal|http://mojo.codehaus.org/tomcat-maven-plugin/run-mojo.html] seems to > support forking, but not specifying arguments for forked JVM. Something like > that IMO would be useful for specifying memory options different from Maven > build and javaagent like jacoco for coverage. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1538502 - in /tomcat/maven-plugin/trunk: tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java tomcat7-maven-plugin/src/main/java/org/apache/tomca
Author: olamy
Date: Mon Nov 4 04:12:13 2013
New Revision: 1538502
URL: http://svn.apache.org/r1538502
Log:
[MTOMCAT-92] Bind tomcat to a self-chosen network interface
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Modified:
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java?rev=1538502&r1=1538501&r2=1538502&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
Mon Nov 4 04:12:13 2013
@@ -136,6 +136,16 @@ public abstract class AbstractRunMojo
private int port;
/**
+ *
+ * For servers with more than one IP address, this attribute specifies
which address
+ * will be used for listening on the specified port.
+ * By default, this port will be used on all IP addresses associated with
the server.
+ * @since 2.2
+ */
+@Parameter( property = "maven.tomcat.address")
+private String address;
+
+/**
* The AJP port to run the Tomcat server on.
* By default it's 0 this means won't be started.
* The ajp connector will be started only for value > 0.
@@ -909,6 +919,13 @@ public abstract class AbstractRunMojo
}
httpConnector.setURIEncoding( uriEncoding );
httpConnector.setUseBodyEncodingForURI(
this.useBodyEncodingForURI );
+
+if ( address !=null)
+{
+//ici
+httpConnector.setAttribute( "address", address );
+}
+
container.addConnector( httpConnector );
// create https connector
Modified:
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java?rev=1538502&r1=1538501&r2=1538502&view=diff
==
---
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
(original)
+++
tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
Mon Nov 4 04:12:13 2013
@@ -151,6 +151,16 @@ public abstract class AbstractRunMojo
private int port;
/**
+ *
+ * For servers with more than one IP address, this attribute specifies
which address
+ * will be used for listening on the specified port.
+ * By default, this port will be used on all IP addresses associated with
the server.
+ * @since 2.2
+ */
+@Parameter( property = "maven.tomcat.address")
+private String address;
+
+/**
* The AJP port to run the Tomcat server on.
* By default it's 0 this means won't be started.
* The ajp connector will be started only for value > 0.
@@ -,6 +1121,11 @@ public abstract class AbstractRunMojo
connector.setRedirectPort( httpsPort );
}
+if ( address !=null)
+{
+connector.setAttribute( "address", address );
+}
+
connector.setURIEncoding( uriEncoding );
connector.setUseBodyEncodingForURI( this.useBodyEncodingForURI
);
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-75) Dependency scope of "tomcat" needed for addContextWarDependencies to work in run/run-war goals.
[ https://issues.apache.org/jira/browse/MTOMCAT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-75. - Resolution: Duplicate Assignee: Olivier Lamy (*$^¨%`£) > Dependency scope of "tomcat" needed for addContextWarDependencies to work in > run/run-war goals. > --- > > Key: MTOMCAT-75 > URL: https://issues.apache.org/jira/browse/MTOMCAT-75 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 1.1 > Environment: Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400) > Java version: 1.6.0_22 > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.5.8" arch: "x86_64" Family: "mac" >Reporter: Ryan Connolly >Assignee: Olivier Lamy (*$^¨%`£) > > The feature to deploy dependency wars to embedded containers created with > tomcat:run and tomcat:run-war depend upon a war dependency scope being > defined as "tomcat". It would seem a much cleaner to allow the configuration > of such war dependencies in the plugin dependencies using a valid dependency > scope. > Log Output: > [WARNING] Some problems were encountered while building the effective model > for com.rynam0:tomcat-maven-plugin-test:war:1.0-SNAPSHOT > [WARNING] 'dependencies.dependency.scope' for > com.rynam0:simple-portal-war:war must be one of [provided, compile, runtime, > test, system] but is 'tomcat'. @ line 22, column 14 > [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. > [WARNING] -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-228) Provide option to deploy war file(s) from a location when executing run mojo
[ https://issues.apache.org/jira/browse/MTOMCAT-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-228: --- Fix Version/s: 3.0 > Provide option to deploy war file(s) from a location when executing run mojo > > > Key: MTOMCAT-228 > URL: https://issues.apache.org/jira/browse/MTOMCAT-228 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Reporter: Peter Nguyen >Priority: Minor > Fix For: 3.0 > > > Can we please add the ability to deploy a war file from a location instead of > the m2 repository (via webapps) when running the run mojo? > I currently have a multi module project that contains two sub projects: a > project containing a war file and it's sibling containing a suite of selenium > tests > project-parent > +-- war-project (war project) > +-- integration-tests (non-war project) > I'd like to have the integration tests start up an embedded server and deploy > the war file from the project containing the web app. It seems I can only do > this if the artifact under test has been installed and deployed via the > configuration. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-132) cookie jession submit by hidden
[ https://issues.apache.org/jira/browse/MTOMCAT-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-132. -- Resolution: Not A Problem this is an Apache Tomcat question not related to the maven plugin. > cookie jession submit by hidden > --- > > Key: MTOMCAT-132 > URL: https://issues.apache.org/jira/browse/MTOMCAT-132 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6 >Affects Versions: 1.1 > Environment: tomcat6 jdk1.5.09 >Reporter: hongzhou sun >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Original Estimate: 12h > Remaining Estimate: 12h > > On the condition that the ie's cookie is disable! But I also want to submit > the jsessionid by the value="xx" /> syntax. > The result is there is a new Session was created on the server instead of the > old Session which i want to keep. > Is there anybody who can tell me the reason? > And I also don't want to use the Url rewrite to resolve the Session content > trans.'Cause it seems to be some security problems. > Best regards! Thanks! -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-159) WAR dependencies extracted every run
[ https://issues.apache.org/jira/browse/MTOMCAT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) updated MTOMCAT-159: --- Fix Version/s: 2.2 > WAR dependencies extracted every run > > > Key: MTOMCAT-159 > URL: https://issues.apache.org/jira/browse/MTOMCAT-159 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: commons-lib >Affects Versions: 2.0 >Reporter: Robert Hollencamp >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.2 > > Attachments: MTOMCAT-159-1.diff > > > If there is a WAR dependency, it is extracted to > target/apache-tomcat-maven-plugin/ARTIFACT_NAME. This directory is deleted > and re-created every invocation of the plugin, meaning that all WAR > dependencies are re-extracted every run. > Do not delete these extracted directories. Instead check the last modified > timestamp of the directory against the last modified timestamp of the WAR > dependency, and re-extract only if the WAR is newer -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1538505 - /tomcat/maven-plugin/trunk/pom.xml
Author: olamy Date: Mon Nov 4 05:04:42 2013 New Revision: 1538505 URL: http://svn.apache.org/r1538505 Log: add contributor Modified: tomcat/maven-plugin/trunk/pom.xml Modified: tomcat/maven-plugin/trunk/pom.xml URL: http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/pom.xml?rev=1538505&r1=1538504&r2=1538505&view=diff == --- tomcat/maven-plugin/trunk/pom.xml (original) +++ tomcat/maven-plugin/trunk/pom.xml Mon Nov 4 05:04:42 2013 @@ -170,6 +170,9 @@ Cedric Dutoit + + Robert Hollencamp + - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1538504 - /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java
Author: olamy
Date: Mon Nov 4 05:04:31 2013
New Revision: 1538504
URL: http://svn.apache.org/r1538504
Log:
[MTOMCAT-159] WAR dependencies extracted every run
Submitted by Robert Hollencamp
Modified:
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java
Modified:
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java
URL:
http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java?rev=1538504&r1=1538503&r2=1538504&view=diff
==
---
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java
(original)
+++
tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java
Mon Nov 4 05:04:31 2013
@@ -88,15 +88,9 @@ public class DefaultClassLoaderEntriesCa
throw new TomcatRunException( e.getMessage(), e );
}
-// TODO find a solution to use a timestamp marker to not
delete/extract all the time
-
File tmpExtractDatas =
new File( request.getMavenProject().getBuild().getDirectory(),
"apache-tomcat-maven-plugin" );
-if ( tmpExtractDatas.exists() )
-{
-deleteDirectory( tmpExtractDatas, request.getLog() );
-}
tmpExtractDatas.mkdirs();
// add artifacts to loader
@@ -138,18 +132,44 @@ public class DefaultClassLoaderEntriesCa
File tmpDir = new File( tmpExtractDatas,
artifact.getArtifactId() );
-tmpDir.mkdirs();
+boolean existed = !tmpDir.mkdirs();
+// does a directory for this artifact already exist?
+if (existed)
+{
+// check timestamp to see if artifact is newer than
extracted directory
+long dirLastMod = tmpDir.lastModified();
+long warLastMod = artifact.getFile().lastModified();
+
+if (warLastMod == 0L || warLastMod > dirLastMod)
+{
+request.getLog().debug(
+"re-exploding artifact " +
artifact.getArtifactId() + " due to newer WAR");
+
+deleteDirectory( tmpDir, request.getLog() );
+tmpDir = new File( tmpExtractDatas,
artifact.getArtifactId() );
+tmpDir.mkdirs();
+existed = false;
+}
+else
+{
+request.getLog().debug(
+"using existing exploded war for artifact " +
artifact.getArtifactId());
+}
+}
tmpDirectories.add( tmpDir );
try
{
-tmpDir.deleteOnExit();
-File warFile = artifact.getFile();
-UnArchiver unArchiver = archiverManager.getUnArchiver(
"jar" );
-unArchiver.setSourceFile( warFile );
-unArchiver.setDestDirectory( tmpDir );
-unArchiver.extract();
+// explode the archive if it is not already exploded
+if (!existed)
+{
+File warFile = artifact.getFile();
+UnArchiver unArchiver =
archiverManager.getUnArchiver( "jar" );
+unArchiver.setSourceFile( warFile );
+unArchiver.setDestDirectory( tmpDir );
+unArchiver.extract();
+}
File libsDirectory = new File( tmpDir, "WEB-INF/lib" );
if ( libsDirectory.exists() )
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-159) WAR dependencies extracted every run
[ https://issues.apache.org/jira/browse/MTOMCAT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-159. -- Resolution: Fixed Applied. Thanks for the patch! > WAR dependencies extracted every run > > > Key: MTOMCAT-159 > URL: https://issues.apache.org/jira/browse/MTOMCAT-159 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: commons-lib >Affects Versions: 2.0 >Reporter: Robert Hollencamp >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.2 > > Attachments: MTOMCAT-159-1.diff > > > If there is a WAR dependency, it is extracted to > target/apache-tomcat-maven-plugin/ARTIFACT_NAME. This directory is deleted > and re-created every invocation of the plugin, meaning that all WAR > dependencies are re-extracted every run. > Do not delete these extracted directories. Instead check the last modified > timestamp of the directory against the last modified timestamp of the WAR > dependency, and re-extract only if the WAR is newer -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-32) Allow manager url in settings.xml (via server/configuration/url)
[
https://issues.apache.org/jira/browse/MTOMCAT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-32.
-
Resolution: Won't Fix
Assignee: Olivier Lamy (*$^¨%`£)
no feedback from user.
> Allow manager url in settings.xml (via server/configuration/url)
>
>
> Key: MTOMCAT-32
> URL: https://issues.apache.org/jira/browse/MTOMCAT-32
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Affects Versions: 1.0-beta-1
> Environment: Windows/Apache/Tomcat/Maven2/JDK1.6
>Reporter: Steve Gillam
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
>
> URL for tomcat manager is a function of machine configuration (refelcted in
> maven's settings.xml) as opposed to the project settings (as reflected in
> pom.xml)
> Maven's settings.xml does support
> {server}{configuration}{url} http://localhost/manager
> {/url}{/configuration}{/server} as used by
> http://pyx4me.com/pyx4me-maven-plugins/obex-maven-plugin/
> Unfortunately, whilst not generating any errors, the tomcat plugin seems not
> to look for/use it (and defaults to http://localhost:8080/manager)
> Would be very useful if it did
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-84) tomcat:reload logs the wrong message
[ https://issues.apache.org/jira/browse/MTOMCAT-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-84. - Resolution: Won't Fix Assignee: Olivier Lamy (*$^¨%`£) we use tomcat manager reload url so the message looks correct for me. > tomcat:reload logs the wrong message > > > Key: MTOMCAT-84 > URL: https://issues.apache.org/jira/browse/MTOMCAT-84 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Michael Osipov >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Attachments: ASF.LICENSE.NOT.GRANTED--MTOMCAT-84.patch > > > Instead of emitting "Reloading app", it emits "Redeploying app". I have > patched the issue. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-181) Allow to run the webapp under the root context
[ https://issues.apache.org/jira/browse/MTOMCAT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-181. -- > 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 > > Right now the plugin simply ignores this: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0 > > / > > > and take the artifactId as default context path. > Would be possible to run it under the root context? -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-193) Odd need to create an empty context.xml file for the Apache Tomcat Maven plugin to work
[ https://issues.apache.org/jira/browse/MTOMCAT-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-193. -- > Odd need to create an empty context.xml file for the Apache Tomcat Maven > plugin to work > --- > > Key: MTOMCAT-193 > URL: https://issues.apache.org/jira/browse/MTOMCAT-193 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 > Environment: Ubuntu Linux, JDK 7, CXF 2.7.1 >Reporter: Glen Mazza >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > > Hi, I switched from the Codehaus to the Apache Tomcat plugin for Apache CXF's > REST archetype: > http://svn.apache.org/viewvc/cxf/trunk/maven-plugins/archetypes/cxf-jaxrs-service/src/main/resources/archetype-resources/pom.xml?r1=1417501&r2=1418739&diff_format=h > For "mvn clean install" to work with the new plugin I needed to add an empty > META-INF/context.xml file: > http://svn.apache.org/viewvc/cxf/trunk/maven-plugins/archetypes/cxf-jaxrs-service/src/main/resources/archetype-resources/src/main/webapp/META-INF/ > This file was never needed by the Codehaus plugin. If I didn't add it for > the Apache one, "mvn clean install" returns this error: > [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ testrest --- > [INFO] Skipping execution of surefire because it has already been run for > this configuration > [INFO] > [INFO] --- maven-war-plugin:2.1.1:war (default-war) @ testrest --- > [INFO] Packaging webapp > [INFO] Assembling webapp [testrest] in > [/media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT] > [INFO] Processing war project > [INFO] Copying webapp resources > [/media/work1/opensource/testrest/src/main/webapp] > [INFO] Webapp assembled in [29 msecs] > [INFO] Building war: > /media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT.war > [INFO] WEB-INF/web.xml already added, skipping > [INFO] > [INFO] <<< tomcat7-maven-plugin:2.0:run-war (start-tomcat) @ testrest <<< > [INFO] > [INFO] --- tomcat7-maven-plugin:2.0:run-war (start-tomcat) @ testrest --- > [INFO] Running war on http://localhost:56114/jaxrs-service > [INFO] Creating Tomcat server configuration at > /media/work1/opensource/testrest/target/tomcat > [INFO] create webapp with contextPath: /jaxrs-service > Dec 08, 2012 2:37:48 PM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-bio-56114"] > Dec 08, 2012 2:37:48 PM org.apache.catalina.core.StandardService startInternal > INFO: Starting service Tomcat > Dec 08, 2012 2:37:48 PM org.apache.catalina.core.StandardEngine startInternal > INFO: Starting Servlet Engine: Apache Tomcat/7.0.30 > Dec 08, 2012 2:37:48 PM org.apache.catalina.startup.ContextConfig > processContextConfig > SEVERE: Missing context.xml: > file:/media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT/META-INF/context.xml > java.io.FileNotFoundException: > /media/work1/opensource/testrest/target/testrest-0.0.1-SNAPSHOT/META-INF/context.xml > (No such file or directory) > at java.io.FileInputStream.open(Native Method) > at java.io.FileInputStream.(FileInputStream.java:138) > at java.io.FileInputStream.(FileInputStream.java:97) > at > sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) > at > sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) > at java.net.URL.openStream(URL.java:1037) > at > org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:618) > at > org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:599) > at > org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:837) > at > org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:387) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) > at > org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401) > at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.Thr
[jira] [Closed] (MTOMCAT-89) addContextWarDependencies uses tomcat but this isn't in the documentation
[ https://issues.apache.org/jira/browse/MTOMCAT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MTOMCAT-89. - > addContextWarDependencies uses tomcat but this isn't in the > documentation > > > Key: MTOMCAT-89 > URL: https://issues.apache.org/jira/browse/MTOMCAT-89 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Benson Margulies > > The mojo doc for addContextWarDependencies does not mention scope=tomcat. > This had me really, really, puzzled. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Closed] (MTOMCAT-79) Running "package" before tomcat:deploy breaks build
[
https://issues.apache.org/jira/browse/MTOMCAT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-79.
-
Assignee: Olivier Lamy (*$^¨%`£)
> Running "package" before tomcat:deploy breaks build
> ---
>
> Key: MTOMCAT-79
> URL: https://issues.apache.org/jira/browse/MTOMCAT-79
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: Maven 2.2.11
>Reporter: Michael Osipov
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Blocker
> Fix For: 1.1
>
>
> @execute="package" breaks multi-module builds with overlays.
> I have this situation:
> {noformat}
> parent
> |-war1
> |-war2 (overlayed with war1)
> {noformat}
> To have war2 overlayed with war1 from reactor, I have to build from parent.
> I.e., to deploy a correctly overlayed war2, I have to have to go from parent.
> Otherwise overlay happens from local repo which is incorrect. So, because
> tomcat-maven-p invokes "package" at war2 and only at war2, the overlay war1
> is taken from local repo. The overlayed WAR is incorrect. I explicitly have
> to call "package" from parent.
> I have logs available which prove the issue but cannot make them public. I
> can send them privately.
> All this means, that the automatic execution of package needs to be removed.
> If there is no warFile to deploy, exit with build failure and tell that
> package has to run first.
> Remove this line:
> http://mojo.codehaus.org/tomcat-maven-plugin/xref/org/codehaus/mojo/tomcat/DeployMojo.html#26
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
