[jira] [Closed] (MTOMCAT-96) deployment of the site in the tomcat land
[ https://issues.apache.org/jira/browse/MTOMCAT-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MTOMCAT-96. --- Resolution: Fixed done deployment of the site in the tomcat land - Key: MTOMCAT-96 URL: https://issues.apache.org/jira/browse/MTOMCAT-96 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.0 The goal is to deploy the generated maven site to http://tomcat.apache.org/maven-plugin/ . And add a link to it in Tomcat home called Maven Plugin just below the existing Taglibs link. Let me know if that makes sense ? -- This message is automatically generated by JIRA. 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] [Closed] (MTOMCAT-97) rename current tomcat maven plugin to tomcat6 and add tomcat7
[ https://issues.apache.org/jira/browse/MTOMCAT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MTOMCAT-97. --- Resolution: Fixed done renamed to tomcat6 rename current tomcat maven plugin to tomcat6 and add tomcat7 -- Key: MTOMCAT-97 URL: https://issues.apache.org/jira/browse/MTOMCAT-97 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.0 To prevent confusion for users, I'd like to rename the current version which supports tomcat 6 to tomcat6 and add tomcat 7 support in tomcat7. users will have now to use tomcat6:run instead tomcat:run. Btw users will have to add a pluginGroup entry in ~/.m2/settings.xml as the used groupId is not automatically discovered by maven core. Any objections ? -- This message is automatically generated by JIRA. 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] [Updated] (MTOMCAT-97) rename current tomcat maven plugin to tomcat6 and add tomcat7
[ https://issues.apache.org/jira/browse/MTOMCAT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-97: Fix Version/s: 2.0 rename current tomcat maven plugin to tomcat6 and add tomcat7 -- Key: MTOMCAT-97 URL: https://issues.apache.org/jira/browse/MTOMCAT-97 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.0 To prevent confusion for users, I'd like to rename the current version which supports tomcat 6 to tomcat6 and add tomcat 7 support in tomcat7. users will have now to use tomcat6:run instead tomcat:run. Btw users will have to add a pluginGroup entry in ~/.m2/settings.xml as the used groupId is not automatically discovered by maven core. Any objections ? -- This message is automatically generated by JIRA. 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] [Assigned] (MTOMCAT-87) Make http protocol configurable for the embedded Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reassigned MTOMCAT-87: --- Assignee: Olivier Lamy Make http protocol configurable for the embedded Tomcat --- Key: MTOMCAT-87 URL: https://issues.apache.org/jira/browse/MTOMCAT-87 Project: Maven 2.x Tomcat Plugin Issue Type: New Feature Reporter: Adrien C Assignee: Olivier Lamy Fix For: 2.0 Attachments: http-protocol.patch tomcat maven plugin 1.1 sets HTTP connector with default HTTP/1.1 protocol. Being able to set another protocol (ex: org.apache.coyote.http11.Http11NioProtocol) would be useful. -- This message is automatically generated by JIRA. 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] [Updated] (MTOMCAT-87) Make http protocol configurable for the embedded Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-87: Fix Version/s: 2.0 Make http protocol configurable for the embedded Tomcat --- Key: MTOMCAT-87 URL: https://issues.apache.org/jira/browse/MTOMCAT-87 Project: Maven 2.x Tomcat Plugin Issue Type: New Feature Reporter: Adrien C Assignee: Olivier Lamy Fix For: 2.0 Attachments: http-protocol.patch tomcat maven plugin 1.1 sets HTTP connector with default HTTP/1.1 protocol. Being able to set another protocol (ex: org.apache.coyote.http11.Http11NioProtocol) would be useful. -- This message is automatically generated by JIRA. 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] [Closed] (MTOMCAT-87) Make http protocol configurable for the embedded Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MTOMCAT-87. --- Resolution: Fixed fixed rev 1169647. Thanks for the patch ! Make http protocol configurable for the embedded Tomcat --- Key: MTOMCAT-87 URL: https://issues.apache.org/jira/browse/MTOMCAT-87 Project: Maven 2.x Tomcat Plugin Issue Type: New Feature Reporter: Adrien C Assignee: Olivier Lamy Fix For: 2.0 Attachments: http-protocol.patch tomcat maven plugin 1.1 sets HTTP connector with default HTTP/1.1 protocol. Being able to set another protocol (ex: org.apache.coyote.http11.Http11NioProtocol) would be useful. -- This message is automatically generated by JIRA. 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] [Created] (MTOMCAT-97) rename current tomcat maven plugin to tomcat6 and add tomcat7
rename current tomcat maven plugin to tomcat6 and add tomcat7 -- Key: MTOMCAT-97 URL: https://issues.apache.org/jira/browse/MTOMCAT-97 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy To prevent confusion for users, I'd like to rename the current version which supports tomcat 6 to tomcat6 and add tomcat 7 support in tomcat7. users will have now to use tomcat6:run instead tomcat:run. Btw users will have to add a pluginGroup entry in ~/.m2/settings.xml as the used groupId is not automatically discovered by maven core. Any objections ? -- This message is automatically generated by JIRA. 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] [Created] (MTOMCAT-96) deployment of the site in the tomcat land
deployment of the site in the tomcat land - Key: MTOMCAT-96 URL: https://issues.apache.org/jira/browse/MTOMCAT-96 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy The goal is to deploy the generated maven site to http://tomcat.apache.org/maven-plugin/ . And add a link to it in Tomcat home called Maven Plugin just below the existing Taglibs link. Let me know if that makes sense ? -- This message is automatically generated by JIRA. 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-96) deployment of the site in the tomcat land
[ https://issues.apache.org/jira/browse/MTOMCAT-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100213#comment-13100213 ] Olivier Lamy commented on MTOMCAT-96: - In fact I would prefer to have versionned generated Maven site plugin : * http://tomcat.apache.org/maven-plugin-2.0 * http://tomcat.apache.org/maven-plugin-2.1 * etc... With a page http://tomcat.apache.org/maven-plugin.html which will contains link to various versions and informations (svn url, bug tracker url etc...) deployment of the site in the tomcat land - Key: MTOMCAT-96 URL: https://issues.apache.org/jira/browse/MTOMCAT-96 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy The goal is to deploy the generated maven site to http://tomcat.apache.org/maven-plugin/ . And add a link to it in Tomcat home called Maven Plugin just below the existing Taglibs link. Let me know if that makes sense ? -- This message is automatically generated by JIRA. 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] [Updated] (MTOMCAT-96) deployment of the site in the tomcat land
[ https://issues.apache.org/jira/browse/MTOMCAT-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-96: Fix Version/s: 2.0 deployment of the site in the tomcat land - Key: MTOMCAT-96 URL: https://issues.apache.org/jira/browse/MTOMCAT-96 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.0 The goal is to deploy the generated maven site to http://tomcat.apache.org/maven-plugin/ . And add a link to it in Tomcat home called Maven Plugin just below the existing Taglibs link. Let me know if that makes sense ? -- This message is automatically generated by JIRA. 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] [Updated] (MTOMCAT-62) Support Tomcat 7
[ https://issues.apache.org/jira/browse/MTOMCAT-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-62: Fix Version/s: 2.0 Assignee: Olivier Lamy Support Tomcat 7 Key: MTOMCAT-62 URL: https://issues.apache.org/jira/browse/MTOMCAT-62 Project: Maven 2.x Tomcat Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: Travis Schneeberger Assignee: Olivier Lamy Fix For: 2.0 Please support Tomcat 7. BTW. There are several maven tomcat plugins that support Tomcat 7: http://code.google.com/p/t7mp/ http://cargo.codehaus.org/ -- This message is automatically generated by JIRA. 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] [Closed] (MTOMCAT-93) Move tomcat-maven-plugin to Apache Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MTOMCAT-93. --- Resolution: Fixed Fix Version/s: 2.0 Move tomcat-maven-plugin to Apache Tomcat - Key: MTOMCAT-93 URL: https://issues.apache.org/jira/browse/MTOMCAT-93 Project: Maven 2.x Tomcat Plugin Issue Type: Task Reporter: Mark Hobson Assignee: Olivier Lamy Fix For: 2.0 Moving the tomcat-maven-plugin to Apache Tomcat would resolve the trademark issues and keep the codebase closer to Tomcat itself. -- This message is automatically generated by JIRA. 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] [Updated] (MTOMCAT-81) mvn tomcat:run does not work with spring tomcat classloader
[ https://issues.apache.org/jira/browse/MTOMCAT-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-81: Fix Version/s: backlog need a sample project to test it. mvn tomcat:run does not work with spring tomcat classloader --- Key: MTOMCAT-81 URL: https://issues.apache.org/jira/browse/MTOMCAT-81 Project: Maven 2.x Tomcat Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Ubuntu 10.10 Reporter: Jothi Shankar Kumar Priority: Blocker Fix For: backlog I have been trying for weeks to get the mvn tomcat:run work for my Spring based project. I use the spring-tomcat-weaver.jar for doing the class loading in Tomcat. When I run my project using mvn tomcat:run command it gives me a class not found. Below is a stack trace of what I get: SEVERE: LifecycleException java.lang.ClassNotFoundException: org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at org.apache.catalina.loader.WebappLoader.createClassLoader(WebappLoader.java:801) at org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:661) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4504) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:785) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445) at org.apache.catalina.startup.Embedded.start(Embedded.java:825) at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:558) at org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:255) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) 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:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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) -- This message is automatically generated by JIRA. 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
