[jira] [Commented] (MTOMCAT-32) Allow manager url in settings.xml (via server/configuration/url)

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126988#comment-13126988
 ] 

Olivier Lamy commented on MTOMCAT-32:
-

and url is configurable tru cli: -Dmaven.tomcat.url=
see 
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/deploy-mojo.html#url
  

> Allow manager url in settings.xml (via server/configuration/url)
> 
>
> Key: MTOMCAT-32
> URL: https://issues.apache.org/jira/browse/MTOMCAT-32
> Project: Maven 2.x Tomcat Plugin
>  Issue Type: Improvement
>Affects Versions: 1.0-beta-1
> Environment: Windows/Apache/Tomcat/Maven2/JDK1.6
>Reporter: Steve Gillam
>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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-94) tomcat:run doesn't take into account classesDir param

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128289#comment-13128289
 ] 

Olivier Lamy commented on MTOMCAT-94:
-

But we add List classPathElements = 
project.getCompileClasspathElements();
So I don't see why it's an issue ?

> tomcat:run doesn't take into account classesDir param
> -
>
> Key: MTOMCAT-94
> URL: https://issues.apache.org/jira/browse/MTOMCAT-94
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Ilya Klyuchnikov
>  Labels: tocheck
>
> tomcat:run doesn't take into account classesDir param
> See that corresponding code is commented out:
> https://fisheye.codehaus.org/browse/mojo/tags/tomcat-maven-plugin-1.1/src/main/java/org/codehaus/mojo/tomcat/RunMojo.java?hb=true#to148

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-81) mvn tomcat:run does not work with spring tomcat classloader

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138146#comment-13138146
 ] 

Olivier Lamy commented on MTOMCAT-81:
-

how is declared your dependency on spring-tomcat-weaver or 
spring-instrument-tomcat ?

> mvn tomcat:run does not work with spring tomcat classloader
> ---
>
> Key: MTOMCAT-81
> URL: https://issues.apache.org/jira/browse/MTOMCAT-81
> Project: Apache Tomcat Maven 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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-103) Executable War fails to run with a NullPointerException

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138150#comment-13138150
 ] 

Olivier Lamy commented on MTOMCAT-103:
--

does the file smapi-1.0-war-exec.jar contains the war file smapi-1.0.war ?
As it looks to not be here: how do you configure the mojo in your pom ?

> Executable War fails to run with a NullPointerException
> ---
>
> Key: MTOMCAT-103
> URL: https://issues.apache.org/jira/browse/MTOMCAT-103
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Mac OSX (tried on windows 7 as well)
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
>Priority: Critical
> Fix For: 2.0
>
>
> Running the package goal with maven with the tomcat7 plugin configured the 
> generated executable war fails to run.  The error is:
> $ java -jar ./smapi-1.0-war-exec.jar -debug
> populateWebAppWarPerContext warValue:/smapi-1.0.war|/smapi-1.0
> populateWebAppWarPerContext contextValue/warFileName:/smapi-1.0//smapi-1.0.war
> webappWarPerContext entry key/value: /smapi-1.0//smapi-1.0.war
> Exception in thread "main" java.lang.NullPointerException
>   at 
> org.apache.tomcat.maven.runner.Tomcat7Runner.expand(Tomcat7Runner.java:406)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7Runner.extract(Tomcat7Runner.java:309)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:98)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:144)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-105) creating executable war failed

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142940#comment-13142940
 ] 

Olivier Lamy commented on MTOMCAT-105:
--

It looks the war generated by your project is not generated.
Does your project produce a war file ?
To trigger exec-war-only goal in the package phase, your execution block must 
be in build/plugins/plugin rather than in pluginManagement section.

> creating executable war failed
> --
>
> Key: MTOMCAT-105
> URL: https://issues.apache.org/jira/browse/MTOMCAT-105
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: C:\Users\albert\workspace\BasicSetup>mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-03-01 00:31:09+0700)
> Maven home: C:\Users\albert\Desktop\myapps\apache-maven-3.0.3\bin\..
> Java version: 1.7.0, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: albert kam
>Assignee: Olivier Lamy
>Priority: Critical
>  Labels: exec-war
> Fix For: 2.0
>
>   Original Estimate: 0.05h
>  Remaining Estimate: 0.05h
>
> Just today on November 3rd, i tried out the tomcat7 maven plugin to try out 
> the executable war.
> Following the configuration from the 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html, 
> here's the output of my tomcat7:exec-war-only -X :
> ... lot of lines removed ...
> org.codehaus.plexus:plexus-archiver:jar:2.0.1:compile, 
> junit:junit:jar:4.9:compile, org.hamcrest:hamcrest-core:jar:1.1:compile, 
> org.codehaus.plexus:plexus-io:jar:2.0.1:compile]
> [DEBUG]   (f) project = MavenProject: 
> kam.albert.study:BasicSetup:0.0.1-SNAPSHOT @ 
> C:\Users\albert\workspace\BasicSetup\pom.xml
> [DEBUG]   (f) projectArtifact = kam.albert.study:BasicSetup:war:0.0.1-SNAPSHOT
> [DEBUG]   (f) remoteRepos = [   id: jvnet-nexus-releases
>   url: https://maven.java.net/content/repositories/releases/
>layout: default
> snapshots: [enabled => true, update => daily]
>  releases: [enabled => true, update => daily]
> ,id: central
>   url: http://repo1.maven.org/maven2
>layout: default
> snapshots: [enabled => false, update => daily]
>  releases: [enabled => true, update => daily]
> ]
> [DEBUG]   (f) serverXml = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf\server.xml
> [DEBUG]   (f) tomcatConfigurationFilesDirectory = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.827s
> [INFO] Finished at: Thu Nov 03 13:06:40 ICT 2011
> [INFO] Final Memory: 6M/15M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:319)
>   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(Nativ

[jira] [Commented] (MTOMCAT-105) creating executable war failed

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143009#comment-13143009
 ] 

Olivier Lamy commented on MTOMCAT-105:
--

see http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/mail-lists.html
Can I have a sample application  to reproduce that ?

> creating executable war failed
> --
>
> Key: MTOMCAT-105
> URL: https://issues.apache.org/jira/browse/MTOMCAT-105
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: C:\Users\albert\workspace\BasicSetup>mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-03-01 00:31:09+0700)
> Maven home: C:\Users\albert\Desktop\myapps\apache-maven-3.0.3\bin\..
> Java version: 1.7.0, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: albert kam
>Assignee: Olivier Lamy
>Priority: Critical
>  Labels: exec-war
> Fix For: 2.0
>
>   Original Estimate: 0.05h
>  Remaining Estimate: 0.05h
>
> Just today on November 3rd, i tried out the tomcat7 maven plugin to try out 
> the executable war.
> Following the configuration from the 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html, 
> here's the output of my tomcat7:exec-war-only -X :
> ... lot of lines removed ...
> org.codehaus.plexus:plexus-archiver:jar:2.0.1:compile, 
> junit:junit:jar:4.9:compile, org.hamcrest:hamcrest-core:jar:1.1:compile, 
> org.codehaus.plexus:plexus-io:jar:2.0.1:compile]
> [DEBUG]   (f) project = MavenProject: 
> kam.albert.study:BasicSetup:0.0.1-SNAPSHOT @ 
> C:\Users\albert\workspace\BasicSetup\pom.xml
> [DEBUG]   (f) projectArtifact = kam.albert.study:BasicSetup:war:0.0.1-SNAPSHOT
> [DEBUG]   (f) remoteRepos = [   id: jvnet-nexus-releases
>   url: https://maven.java.net/content/repositories/releases/
>layout: default
> snapshots: [enabled => true, update => daily]
>  releases: [enabled => true, update => daily]
> ,id: central
>   url: http://repo1.maven.org/maven2
>layout: default
> snapshots: [enabled => false, update => daily]
>  releases: [enabled => true, update => daily]
> ]
> [DEBUG]   (f) serverXml = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf\server.xml
> [DEBUG]   (f) tomcatConfigurationFilesDirectory = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.827s
> [INFO] Finished at: Thu Nov 03 13:06:40 ICT 2011
> [INFO] Final Memory: 6M/15M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:319)
>   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:57)
>   at 
> sun.ref

[jira] [Commented] (MTOMCAT-105) creating executable war failed

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143326#comment-13143326
 ] 

Olivier Lamy commented on MTOMCAT-105:
--

can you try with enabling naming:
{code:xml}
true
{code}

> creating executable war failed
> --
>
> Key: MTOMCAT-105
> URL: https://issues.apache.org/jira/browse/MTOMCAT-105
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: C:\Users\albert\workspace\BasicSetup>mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-03-01 00:31:09+0700)
> Maven home: C:\Users\albert\Desktop\myapps\apache-maven-3.0.3\bin\..
> Java version: 1.7.0, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: albert kam
>Assignee: Olivier Lamy
>Priority: Critical
>  Labels: exec-war
> Fix For: 2.0
>
> Attachments: BasicSetup.zip
>
>   Original Estimate: 0.05h
>  Remaining Estimate: 0.05h
>
> Just today on November 3rd, i tried out the tomcat7 maven plugin to try out 
> the executable war.
> Following the configuration from the 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html, 
> here's the output of my tomcat7:exec-war-only -X :
> ... lot of lines removed ...
> org.codehaus.plexus:plexus-archiver:jar:2.0.1:compile, 
> junit:junit:jar:4.9:compile, org.hamcrest:hamcrest-core:jar:1.1:compile, 
> org.codehaus.plexus:plexus-io:jar:2.0.1:compile]
> [DEBUG]   (f) project = MavenProject: 
> kam.albert.study:BasicSetup:0.0.1-SNAPSHOT @ 
> C:\Users\albert\workspace\BasicSetup\pom.xml
> [DEBUG]   (f) projectArtifact = kam.albert.study:BasicSetup:war:0.0.1-SNAPSHOT
> [DEBUG]   (f) remoteRepos = [   id: jvnet-nexus-releases
>   url: https://maven.java.net/content/repositories/releases/
>layout: default
> snapshots: [enabled => true, update => daily]
>  releases: [enabled => true, update => daily]
> ,id: central
>   url: http://repo1.maven.org/maven2
>layout: default
> snapshots: [enabled => false, update => daily]
>  releases: [enabled => true, update => daily]
> ]
> [DEBUG]   (f) serverXml = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf\server.xml
> [DEBUG]   (f) tomcatConfigurationFilesDirectory = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.827s
> [INFO] Finished at: Thu Nov 03 13:06:40 ICT 2011
> [INFO] Final Memory: 6M/15M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:319)
>   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:57)
>   at 
> sun.reflect.DelegatingMethodAccess

[jira] [Commented] (MTOMCAT-100) support war overlay to add war external dependencies in tomcat run

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145153#comment-13145153
 ] 

Olivier Lamy commented on MTOMCAT-100:
--

http://svn.apache.org/viewvc?view=revision&revision=1198376 do that 

> support war overlay to add war external dependencies in tomcat run 
> ---
>
> Key: MTOMCAT-100
> URL: https://issues.apache.org/jira/browse/MTOMCAT-100
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Improvement
>  Components: tomcat6, tomcat7
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
>  /WEB-INF/lib/*.jar and /WEB-INF/classes will added to web app classloader 
> when using tomcat*:run to do as war overlays does.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-100) support war overlay to add war external dependencies in tomcat run

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149150#comment-13149150
 ] 

Olivier Lamy commented on MTOMCAT-100:
--

The issue I have here is to have a different behavior with the maven-war-plugin.
This one doesn't handle resources from war dependencies.
So usually folks use maven-dependency-plugin to unpack war dependencies to have 
those resources packaged with the war artifacts.

> support war overlay to add war external dependencies in tomcat run 
> ---
>
> Key: MTOMCAT-100
> URL: https://issues.apache.org/jira/browse/MTOMCAT-100
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Improvement
>  Components: tomcat6, tomcat7
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
>  /WEB-INF/lib/*.jar and /WEB-INF/classes will added to web app classloader 
> when using tomcat*:run to do as war overlays does.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-106) tomcat7-maven-plugin extraDependency not working with class not found

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151313#comment-13151313
 ] 

Olivier Lamy commented on MTOMCAT-106:
--

please attach a patch file and check "Grant license to ASF for inclusion in ASF 
works (as per the Apache License §5)"

Thanks!

> tomcat7-maven-plugin extraDependency not working with class not found
> -
>
> Key: MTOMCAT-106
> URL: https://issues.apache.org/jira/browse/MTOMCAT-106
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Ubuntu 11.04 @32bit with Maven 2.2.1 and Java 1.6.0_26
>Reporter: William Ghelfi
>Assignee: Olivier Lamy
>  Labels: maven, snapshot, tomcat
>
> Hello,
> I'm trying to use the 'exec-war-only' goal from version 2.0-SNAPSHOT of 
> tomcat7-maven-plugin, taken from 
> http://people.apache.org/repo/m2-snapshot-repository
> Needing derby, I would use the extraDependencies configuration element as 
> showed in the second example at:
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html
> Here's my configuration:
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   tomcat-run
>   
>   exec-war-only
>   
>   package
>   
>   /${project.artifactId}
>   true
>   
>   
>   
> org.apache.derby
>   
> derby
>   
> 10.8.2.2
>   
>   
>   
>   
>   
> 
> So I launch "mvn clean package -e" and get:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: 
> org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to parse the 
> created DOM for plugin configuration
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>   at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>   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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Error 
> configuring: org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to 
> parse the created DOM for plugin configuration
>   at 
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>   ... 17 more
> Caused by: 
> org.codehaus.plexus.component.configurator.ComponentConfigurationException: 
> Error loading class 
> 'org.apache.tomcat.maven.plugin.tomcat7.run.ExtraDependency'
>   a

[jira] [Commented] (MTOMCAT-106) tomcat7-maven-plugin extraDependency not working with class not found

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151378#comment-13151378
 ] 

Olivier Lamy commented on MTOMCAT-106:
--

to prevent too much complicated xml configuration.
I would prefer : ExtraDependency extend Dependency

> tomcat7-maven-plugin extraDependency not working with class not found
> -
>
> Key: MTOMCAT-106
> URL: https://issues.apache.org/jira/browse/MTOMCAT-106
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Ubuntu 11.04 @32bit with Maven 2.2.1 and Java 1.6.0_26
>Reporter: William Ghelfi
>Assignee: Olivier Lamy
>  Labels: maven, snapshot, tomcat
> Attachments: 
> 0001-extraDependencies-didn-t-really-work-exiting-with-er.patch
>
>
> Hello,
> I'm trying to use the 'exec-war-only' goal from version 2.0-SNAPSHOT of 
> tomcat7-maven-plugin, taken from 
> http://people.apache.org/repo/m2-snapshot-repository
> Needing derby, I would use the extraDependencies configuration element as 
> showed in the second example at:
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html
> Here's my configuration:
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   tomcat-run
>   
>   exec-war-only
>   
>   package
>   
>   /${project.artifactId}
>   true
>   
>   
>   
> org.apache.derby
>   
> derby
>   
> 10.8.2.2
>   
>   
>   
>   
>   
> 
> So I launch "mvn clean package -e" and get:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: 
> org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to parse the 
> created DOM for plugin configuration
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>   at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>   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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Error 
> configuring: org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to 
> parse the created DOM for plugin configuration
>   at 
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>   ... 17 more
> Caused by: 
> org.codehaus.plexus.component.configurator.ComponentConfigurationException: 
> Error loading class 
> 'org

[jira] [Commented] (MTOMCAT-106) tomcat7-maven-plugin extraDependency not working with class not found

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151588#comment-13151588
 ] 

Olivier Lamy commented on MTOMCAT-106:
--

you are using mvn 2.x ?

> tomcat7-maven-plugin extraDependency not working with class not found
> -
>
> Key: MTOMCAT-106
> URL: https://issues.apache.org/jira/browse/MTOMCAT-106
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Ubuntu 11.04 @32bit with Maven 2.2.1 and Java 1.6.0_26
>Reporter: William Ghelfi
>Assignee: Olivier Lamy
>  Labels: maven, snapshot, tomcat
> Attachments: 
> 0001-extraDependencies-didn-t-really-work-exiting-with-er.patch
>
>
> Hello,
> I'm trying to use the 'exec-war-only' goal from version 2.0-SNAPSHOT of 
> tomcat7-maven-plugin, taken from 
> http://people.apache.org/repo/m2-snapshot-repository
> Needing derby, I would use the extraDependencies configuration element as 
> showed in the second example at:
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html
> Here's my configuration:
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   tomcat-run
>   
>   exec-war-only
>   
>   package
>   
>   /${project.artifactId}
>   true
>   
>   
>   
> org.apache.derby
>   
> derby
>   
> 10.8.2.2
>   
>   
>   
>   
>   
> 
> So I launch "mvn clean package -e" and get:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: 
> org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to parse the 
> created DOM for plugin configuration
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>   at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>   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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Error 
> configuring: org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to 
> parse the created DOM for plugin configuration
>   at 
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>   ... 17 more
> Caused by: 
> org.codehaus.plexus.component.configurator.ComponentConfigurationException: 
> Error loading class 
> 'org.apache.tomcat.maven.plugin.tomcat7.run.ExtraDependency'
>   at 
> org.cod

[jira] [Commented] (MTOMCAT-106) tomcat7-maven-plugin extraDependency not working with class not found

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151608#comment-13151608
 ] 

Olivier Lamy commented on MTOMCAT-106:
--

ok. fyi You won't have this issue with 3.x
BTW I have to fix that ;-)

> tomcat7-maven-plugin extraDependency not working with class not found
> -
>
> Key: MTOMCAT-106
> URL: https://issues.apache.org/jira/browse/MTOMCAT-106
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Ubuntu 11.04 @32bit with Maven 2.2.1 and Java 1.6.0_26
>Reporter: William Ghelfi
>Assignee: Olivier Lamy
>  Labels: maven, snapshot, tomcat
> Attachments: 
> 0001-extraDependencies-didn-t-really-work-exiting-with-er.patch
>
>
> Hello,
> I'm trying to use the 'exec-war-only' goal from version 2.0-SNAPSHOT of 
> tomcat7-maven-plugin, taken from 
> http://people.apache.org/repo/m2-snapshot-repository
> Needing derby, I would use the extraDependencies configuration element as 
> showed in the second example at:
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html
> Here's my configuration:
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   tomcat-run
>   
>   exec-war-only
>   
>   package
>   
>   /${project.artifactId}
>   true
>   
>   
>   
> org.apache.derby
>   
> derby
>   
> 10.8.2.2
>   
>   
>   
>   
>   
> 
> So I launch "mvn clean package -e" and get:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: 
> org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to parse the 
> created DOM for plugin configuration
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>   at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>   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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Error 
> configuring: org.apache.tomcat.maven:tomcat7-maven-plugin. Reason: Unable to 
> parse the created DOM for plugin configuration
>   at 
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1363)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724)
>   at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468)
>   at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>   ... 17 more
> Caused by: 
> org.codehaus.plexus.component.configurator.ComponentConfigurationException: 
> Error loading class 
> 'org.apache.tomcat.maven.plugin.tomc

[jira] [Commented] (MTOMCAT-107) restore a simple tomcat plugin with version scheme in for operations non dependent on the tomcat version

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157186#comment-13157186
 ] 

Olivier Lamy commented on MTOMCAT-107:
--

is there any way to ask tomcat in a standard url (non version dependent) to get 
back the version ?

http://ip:port/manager/version return tomcat version ?

> restore a simple tomcat plugin with version scheme in for operations non 
> dependent on the tomcat version
> 
>
> Key: MTOMCAT-107
> URL: https://issues.apache.org/jira/browse/MTOMCAT-107
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Improvement
>  Components: commons-lib
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>
> some remote operations (deploy/undeploy etc...) doesn't depend on the tomcat 
> api.
> so having back a tomcat mojo can ease here instead of having tomcat6:deploy 
> or tomcat7:deploy having a simple tomcat:deploy (the deploy url will be 
> adjust by the user)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-109) org.apache.coyote.http11.Http11NioProtocol not honoured

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170995#comment-13170995
 ] 

Olivier Lamy commented on MTOMCAT-109:
--

do you prefer something configurable tru cli when running your jar or something 
in the mojo which build the jar ? (perso I prefer 2) )

> org.apache.coyote.http11.Http11NioProtocol not honoured
> 
>
> Key: MTOMCAT-109
> URL: https://issues.apache.org/jira/browse/MTOMCAT-109
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Morten Haraldsen
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Tomcat7Runner.java
> Line 146: Connector connector = new Connector( "HTTP/1.1" );
> Make it possible to use NIO connector, through  option so that 
> connector is initialized using something like:
> Connector connector = new Connector( 
> "org.apache.coyote.http11.Http11NioProtocol" );

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170996#comment-13170996
 ] 

Olivier Lamy commented on MTOMCAT-108:
--

@Brad looks a good patch. Note the maven plugin use the maven code formatting: 
http://maven.apache.org/developers/conventions/code.html

> THe httpsPort flag starts another http thread not an https thread
> -
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol 
> listener thread on the port listed not an https protocol listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171218#comment-13171218
 ] 

Olivier Lamy commented on MTOMCAT-108:
--

btw regarding this obfuscate stuff I wonder how it's secured as the deobfuscate 
method is open source :-)

> THe httpsPort flag starts another http thread not an https thread
> -
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol 
> listener thread on the port listed not an https protocol listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172118#comment-13172118
 ] 

Olivier Lamy commented on MTOMCAT-108:
--

why not reading the password from a file ? 
And -httpsPasswordFile= (the file will contains only the password)
this comment "Lifted from Jetty org.mortbay.jetty.security.Password" can/will 
lead in some ip issues.
With such source code import, license headers must be preserve and I don't see 
that in your patch.

> THe httpsPort flag starts another http thread not an https thread
> -
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol 
> listener thread on the port listed not an https protocol listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-110) Support Slf4j bridge logger

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172164#comment-13172164
 ] 

Olivier Lamy commented on MTOMCAT-110:
--

I miss you here. 
Do you need that for tomcat*:run or for the exec war ? or for both ;-) ?

> Support Slf4j bridge logger
> ---
>
> Key: MTOMCAT-110
> URL: https://issues.apache.org/jira/browse/MTOMCAT-110
> Project: Apache Tomcat Maven Plugin
>  Issue Type: New Feature
>Reporter: Morten Haraldsen
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> As a lot of web-applications use slf4j for logging, it would be nice if you 
> could support this as a Mojo parameter, like slf4j
> This should trigger something like:
> java.util.logging.LogManager.getLogManager().reset();
> SLF4JBridgeHandler.install();
> (requires org.slf4j:jul-to-slf4j on the classpath)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-110) Support Slf4j bridge logger

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172282#comment-13172282
 ] 

Olivier Lamy commented on MTOMCAT-110:
--

I'm not in favor about adding such dependency by default for all users (some 
not use slf4j).
What I can do is to search if SLF4JBridgeHandler class is available (with a 
tccl.getClass() or Class.forName() ) and in such case install it.
Makes sense for you ?

> Support Slf4j bridge logger
> ---
>
> Key: MTOMCAT-110
> URL: https://issues.apache.org/jira/browse/MTOMCAT-110
> Project: Apache Tomcat Maven Plugin
>  Issue Type: New Feature
>Reporter: Morten Haraldsen
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> As a lot of web-applications use slf4j for logging, it would be nice if you 
> could support this as a Mojo parameter, like slf4j
> This should trigger something like:
> java.util.logging.LogManager.getLogManager().reset();
> SLF4JBridgeHandler.install();
> (requires org.slf4j:jul-to-slf4j on the classpath)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-105) creating executable war failed

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172760#comment-13172760
 ] 

Olivier Lamy commented on MTOMCAT-105:
--

any way you provide a sample project to reproduce that ?
BTW some changes has been applied could you retry if you still have the issues ?

> creating executable war failed
> --
>
> Key: MTOMCAT-105
> URL: https://issues.apache.org/jira/browse/MTOMCAT-105
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: C:\Users\albert\workspace\BasicSetup>mvn --version
> Apache Maven 3.0.3 (r1075438; 2011-03-01 00:31:09+0700)
> Maven home: C:\Users\albert\Desktop\myapps\apache-maven-3.0.3\bin\..
> Java version: 1.7.0, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>Reporter: albert kam
>Assignee: Olivier Lamy
>Priority: Critical
>  Labels: exec-war
> Fix For: 2.0
>
> Attachments: BasicSetup.zip
>
>   Original Estimate: 0.05h
>  Remaining Estimate: 0.05h
>
> Just today on November 3rd, i tried out the tomcat7 maven plugin to try out 
> the executable war.
> Following the configuration from the 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/executable-war-jar.html, 
> here's the output of my tomcat7:exec-war-only -X :
> ... lot of lines removed ...
> org.codehaus.plexus:plexus-archiver:jar:2.0.1:compile, 
> junit:junit:jar:4.9:compile, org.hamcrest:hamcrest-core:jar:1.1:compile, 
> org.codehaus.plexus:plexus-io:jar:2.0.1:compile]
> [DEBUG]   (f) project = MavenProject: 
> kam.albert.study:BasicSetup:0.0.1-SNAPSHOT @ 
> C:\Users\albert\workspace\BasicSetup\pom.xml
> [DEBUG]   (f) projectArtifact = kam.albert.study:BasicSetup:war:0.0.1-SNAPSHOT
> [DEBUG]   (f) remoteRepos = [   id: jvnet-nexus-releases
>   url: https://maven.java.net/content/repositories/releases/
>layout: default
> snapshots: [enabled => true, update => daily]
>  releases: [enabled => true, update => daily]
> ,id: central
>   url: http://repo1.maven.org/maven2
>layout: default
> snapshots: [enabled => false, update => daily]
>  releases: [enabled => true, update => daily]
> ]
> [DEBUG]   (f) serverXml = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf\server.xml
> [DEBUG]   (f) tomcatConfigurationFilesDirectory = 
> C:\Users\albert\workspace\BasicSetup\src\main\tomcatconf
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.827s
> [INFO] Finished at: Thu Nov 03 13:06:40 ICT 2011
> [INFO] Final Memory: 6M/15M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed. NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> (default-cli) on project BasicSetup: Execution default-cli of goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:exec-war-only 
> failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:319)
>   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(N

[jira] [Commented] (MTOMCAT-92) Bind tomcat to a self-chosen network interface

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172765#comment-13172765
 ] 

Olivier Lamy commented on MTOMCAT-92:
-

in tomcat run plugin ?

> 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.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-104) Running java -jar from a parent directory causes a Zip file error

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172767#comment-13172767
 ] 

Olivier Lamy commented on MTOMCAT-104:
--

some fixes has been committed do you still have the issue ?

> Running java -jar from a parent directory causes a Zip file error
> -
>
> Key: MTOMCAT-104
> URL: https://issues.apache.org/jira/browse/MTOMCAT-104
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: Mac OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
>Priority: Minor
> Fix For: 2.0
>
>
> If you attempt to run the executable jar rather than from the directory the 
> jar file is in you get an error with Zip extraction.
> java -jar ./target/smapi-1.0-war-exec.jar 
> Exception in thread "main" java.util.zip.ZipException: error in opening zip 
> file
>   at java.util.zip.ZipFile.open(Native Method)
>   at java.util.zip.ZipFile.(ZipFile.java:127)
>   at java.util.jar.JarFile.(JarFile.java:135)
>   at java.util.jar.JarFile.(JarFile.java:72)
>   at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:72)
>   at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:48)
>   at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:55)
>   at 
> sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104)
>   at 
> sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:132)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7Runner.getContextXml(Tomcat7Runner.java:229)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:208)
>   at 
> org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:144)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173256#comment-13173256
 ] 

Olivier Lamy commented on MTOMCAT-108:
--

@Keith until a release :-)
Currently you can use 2.0-SNAPSHOT to test.
see [http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html]

> THe httpsPort flag starts another http thread not an https thread
> -
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: https.patch, https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol 
> listener thread on the port listed not an https protocol listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-110) Support Slf4j bridge logger

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174031#comment-13174031
 ] 

Olivier Lamy commented on MTOMCAT-110:
--

lovely :-)
But from where parameter loggerName comes ? IMHO a cli option ?

> Support Slf4j bridge logger
> ---
>
> Key: MTOMCAT-110
> URL: https://issues.apache.org/jira/browse/MTOMCAT-110
> Project: Apache Tomcat Maven Plugin
>  Issue Type: New Feature
>Reporter: Morten Haraldsen
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> As a lot of web-applications use slf4j for logging, it would be nice if you 
> could support this as a Mojo parameter, like slf4j
> This should trigger something like:
> java.util.logging.LogManager.getLogManager().reset();
> SLF4JBridgeHandler.install();
> (requires org.slf4j:jul-to-slf4j on the classpath)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174300#comment-13174300
 ] 

Olivier Lamy commented on MTOMCAT-108:
--

http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
says https://repository.apache.org/content/groups/snapshots-group

> THe httpsPort flag starts another http thread not an https thread
> -
>
> Key: MTOMCAT-108
> URL: https://issues.apache.org/jira/browse/MTOMCAT-108
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
> Environment: MAc OSX 10.6.8
>Reporter: Keith Corbin
>Assignee: Olivier Lamy
> Fix For: 2.0
>
> Attachments: https.patch, https.patch
>
>
> WHen you run the executable war the httpsPort flag starts an http protocol 
> listener thread on the port listed not an https protocol listener.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-92) Bind tomcat to a self-chosen network interface

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175073#comment-13175073
 ] 

Olivier Lamy commented on MTOMCAT-92:
-

I miss you here. You are running tomcat:run on production systems ?
As it's a maven plugin, it's a dev folks tool only.

> 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.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-43) Allow configuration of URI encoding

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187641#comment-13187641
 ] 

Olivier Lamy commented on MTOMCAT-43:
-

this issue concerns tomcat*:run mojo not the new feature for executable jar/war.
But that's true :-)
I will open a separate issue.

> Allow configuration of URI encoding
> ---
>
> Key: MTOMCAT-43
> URL: https://issues.apache.org/jira/browse/MTOMCAT-43
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Improvement
>  Components: tomcat6, tomcat7
>Affects Versions: 1.1
>Reporter: Dan C
>Priority: Minor
> Fix For: 2.0
>
> Attachments: configure-uri-encoding.patch
>
>
> My webapp relies on the servlet container decoding URIs as UTF-8. The 
> attached patch lets me configure this for the embedded Tomcat.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-116) NonRepeatableRequestException when executing goal tomcat6:deploy

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191995#comment-13191995
 ] 

Olivier Lamy commented on MTOMCAT-116:
--

any network issues ?
Does it happen on all build or only one ?

> NonRepeatableRequestException when executing goal tomcat6:deploy
> 
>
> Key: MTOMCAT-116
> URL: https://issues.apache.org/jira/browse/MTOMCAT-116
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0
> Environment: Client: Windows 7/Eclipse Indigo/Java 5/m2eclipse 
> (embedded mvn 3.0.2/1.0.100.20110804-1717)
> Server: Windows 2003 Server/Tomcat 6.0.32/Java 6/
>Reporter: Michael Yockey
>Assignee: Olivier Lamy
>
> Deployment to Tomcat fails after war upload. The war file does not appear on 
> the server but the maven log marks the upload progess to completion. The 
> application is not successfully deployed. Here is the relevant stack trace 
> from the Maven debugging output:
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy 
> (default-cli) on project web-integration: Cannot invoke Tomcat manager
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:592)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke 
> Tomcat manager
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:152)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:71)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: org.apache.http.client.ClientProtocolException
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:926)
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:718)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:681)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:363)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:87)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:86)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:143)
>   ... 22 more
> Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry 
> request with a non-repeatable request entity.
>   at 
> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:686)
>   at 
> org.apache.http.impl.client.DefaultRequestDir

[jira] [Commented] (MTOMCAT-118) tomcat7:run wont accept additionalClasspathDir arguments

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198652#comment-13198652
 ] 

Olivier Lamy commented on MTOMCAT-118:
--

which maven version are you using ?

> tomcat7:run wont accept additionalClasspathDir arguments
> 
>
> Key: MTOMCAT-118
> URL: https://issues.apache.org/jira/browse/MTOMCAT-118
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1, 2.0
>Reporter: Dave Lund
>Assignee: Olivier Lamy
>
> Using the below configuration, the following error is given:
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:run (default-cli) 
> on project XXX: A type incompatibility occured while executing 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:run: 
> java.lang.String cannot be cast to java.io.File
> Example taken from docs site 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/run-mojo-features.html
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   9090
>   /
>   false
>   
> src/sandbox/tomcat/sandbox-context.xml
>   
>   
> src/test/resources
>   
>   
>   
>   
>   mysql
>   mysql-connector-java
>   ${mysql.mysql-connector-java}
>   
>   
>   ch.qos.logback
>   logback-classic
>   0.9.15
>   
>   
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-118) tomcat7:run wont accept additionalClasspathDir arguments

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198682#comment-13198682
 ] 

Olivier Lamy commented on MTOMCAT-118:
--

argh I see this can work only with 3.0.3+
I will fix that but until you must use 3.0.3/3.0.4

> tomcat7:run wont accept additionalClasspathDir arguments
> 
>
> Key: MTOMCAT-118
> URL: https://issues.apache.org/jira/browse/MTOMCAT-118
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1, 2.0
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 12:50:56+0100)
> Java version: 1.6.0_24
> Java home: C:\dev\java\java\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>Reporter: Dave Lund
>Assignee: Olivier Lamy
> Fix For: 2.0
>
>
> Using the below configuration, the following error is given:
> [ERROR] Failed to execute goal 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:run (default-cli) 
> on project XXX: A type incompatibility occured while executing 
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:run: 
> java.lang.String cannot be cast to java.io.File
> Example taken from docs site 
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/run-mojo-features.html
> 
>   org.apache.tomcat.maven
>   tomcat7-maven-plugin
>   2.0-SNAPSHOT
>   
>   
>   9090
>   /
>   false
>   
> src/sandbox/tomcat/sandbox-context.xml
>   
>   
> src/test/resources
>   
>   
>   
>   
>   mysql
>   mysql-connector-java
>   ${mysql.mysql-connector-java}
>   
>   
>   ch.qos.logback
>   logback-classic
>   0.9.15
>   
>   
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-125) mvn tomcat7:run got "javax.naming.NameNotFoundException: Name jdbc is not bound in this Context"

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227456#comment-13227456
 ] 

Olivier Lamy commented on MTOMCAT-125:
--

Do you have more logs ? (especially container start )
How do you add dependency on your jdbc driver when you use the plugin ?

> mvn tomcat7:run got "javax.naming.NameNotFoundException: Name jdbc is not 
> bound in this Context"
> 
>
> Key: MTOMCAT-125
> URL: https://issues.apache.org/jira/browse/MTOMCAT-125
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0-beta-1
> Environment: JDK 7, Tomcat 7.0.25, tomcat7-maven-plugin/2.0-beta-1
>Reporter: guofeng zhang
>Assignee: Olivier Lamy
>
> I configured the datatsource as global naming datasource in server.xml,
>   
> auth="Container"
>maxPoolSize="100" minPoolSize="10"
>name="jdbc/iviewDS"
>testQuery="select count(*) from T_ROLE"
>factory=".."
>type="javax.sql.DataSource"
>uniqueResourceName="jdbc/iviewDS"/>
> The server.xml is copied to src\main\tomcatconf, (this also copyied by the 
> plugin to target\tomcat\conf, so it is used).
> then in webapp/META-INF/context.xml, I have:
> name="jdbc/iviewDS"
> global="jdbc/iviewDS"
> type="javax.sql.DataSource"
> />
> And in web.xml:
> 
> datasoruce
> jdbc/iviewDS
> javax.sql.DataSource
> Container
> 
> In my code, I lookup the datasource using 'java:/comp/env/jdbc/iviewDS'.
> This works well when I deploy the app into tomcat/app directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-116) NonRepeatableRequestException when executing goal tomcat6:deploy

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227843#comment-13227843
 ] 

Olivier Lamy commented on MTOMCAT-116:
--

NAT'ed ? or using some redirect or mod_proxy ?

> NonRepeatableRequestException when executing goal tomcat6:deploy
> 
>
> Key: MTOMCAT-116
> URL: https://issues.apache.org/jira/browse/MTOMCAT-116
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: Client: Windows 7/Eclipse Indigo/Java 5/m2eclipse 
> (embedded mvn 3.0.2/1.0.100.20110804-1717)
> Server: Windows 2003 Server/Tomcat 6.0.32/Java 6/
>Reporter: Michael Yockey
>Assignee: Olivier Lamy
>
> Deployment to Tomcat fails after war upload. The war file does not appear on 
> the server but the maven log marks the upload progess to completion. The 
> application is not successfully deployed. Here is the relevant stack trace 
> from the Maven debugging output:
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy 
> (default-cli) on project web-integration: Cannot invoke Tomcat manager
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:592)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke 
> Tomcat manager
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:152)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:71)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: org.apache.http.client.ClientProtocolException
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:926)
>   at 
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:718)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:681)
>   at 
> org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(TomcatManager.java:363)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:87)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:86)
>   at 
> org.apache.tomcat.maven.plugin.tomcat6.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:143)
>   ... 22 more
> Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry 
> request with a non-repeatable request entity.
>   at 
> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:686)
>   at 
> org.apache.http.impl.client.DefaultRequestDirector.exe

[jira] [Commented] (MTOMCAT-121) Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231737#comment-13231737
 ] 

Olivier Lamy commented on MTOMCAT-121:
--

any logs ?

> Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT
> -
>
> Key: MTOMCAT-121
> URL: https://issues.apache.org/jira/browse/MTOMCAT-121
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: pache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> 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.7.3", arch: "x86_64", family: "mac"
> Tomcat: 6.0.35
>Reporter: Eamonn Linehan
>Assignee: Olivier Lamy
>
> I updated from 2.0-SNAPSHOT to 2.0-beta-1 and stopped being able to deploy 
> war files to tomcat. No changes were made to tomcat. The tomcat manager 
> application is configured to allow access using username 'admin' and no 
> password. The plugin configuration is:
> 
>   org.apache.tomcat.maven
>   tomcat6-maven-plugin
>   2.0-beta-1 
>   
>   /
>   
> ${project.build.directory}/${project.build.finalName}.war
>   
>   true
>   both
>   Britebill
>   
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
>   
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[jira] [Commented] (MTOMCAT-121) Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT

[Olivier Lamy (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/MTOMCAT-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232743#comment-13232743
 ] 

Olivier Lamy commented on MTOMCAT-121:
--

did you try last 2.0-SNAPSHOT ?

> Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT
> -
>
> Key: MTOMCAT-121
> URL: https://issues.apache.org/jira/browse/MTOMCAT-121
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: pache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+)
> Maven home: /usr/share/maven
> Java version: 1.6.0_29, vendor: Apple Inc.
> 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.7.3", arch: "x86_64", family: "mac"
> Tomcat: 6.0.35
>Reporter: Eamonn Linehan
>Assignee: Olivier Lamy
>
> I updated from 2.0-SNAPSHOT to 2.0-beta-1 and stopped being able to deploy 
> war files to tomcat. No changes were made to tomcat. The tomcat manager 
> application is configured to allow access using username 'admin' and no 
> password. The plugin configuration is:
> 
>   org.apache.tomcat.maven
>   tomcat6-maven-plugin
>   2.0-beta-1 
>   
>   /
>   
> ${project.build.directory}/${project.build.finalName}.war
>   
>   true
>   both
>   Britebill
>   
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
>   
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org