[jira] [Created] (MTOMCAT-120) Support "skip" parameter

[Created]

Support "skip" parameter


 Key: MTOMCAT-120
 URL: https://issues.apache.org/jira/browse/MTOMCAT-120
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat7
Affects Versions: 2.0-beta-1
 Environment: -
Reporter: Cédric Dutoit
Assignee: Olivier Lamy
 Fix For: 2.0


Please support a "skip" parameter to tomcat-run, tomcat-shutdown, as does jetty 
project.

For my project, I use SkipITs variable to ask failsafe plugin to not execute IT 
tests.
I also want to avoid having Tomcat started, stopped if IT tests won't execute 
(skipITs=true).
I have the following configuration:




org.apache.tomcat.maven

tomcat7-maven-plugin
2.0-SNAPSHOT


TomcatRunner





tomcat-run


run-war-only


pre-integration-test



tomcat-shutdown


shutdown


post-integration-test




I need a skip variable as to use the following execution configuration:
${skipITs}


Maybe a single variable + 
if (skip)  {
   log(...)
   return;
}
... in org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo
(http://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java)
would be enough.

--
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] [Created] (MTOMCAT-126) Add support for keystoreType

[Created]

Add support for keystoreType


 Key: MTOMCAT-126
 URL: https://issues.apache.org/jira/browse/MTOMCAT-126
 Project: Apache Tomcat Maven Plugin
  Issue Type: New Feature
  Components: tomcat6, tomcat7
Affects Versions: 2.0
Reporter: Cédric Couralet
Assignee: Olivier Lamy
Priority: Minor


I think it would be interesting to add the possibility of changing the keystore 
type for the https connector.

It could be done in exactly the same way as keystoreFile or keystorePass.

--
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] [Created] (MTOMCAT-127) tomcat:run - Configuring Logging with JULI

[Created]

tomcat:run - Configuring Logging with JULI 
---

 Key: MTOMCAT-127
 URL: https://issues.apache.org/jira/browse/MTOMCAT-127
 Project: Apache Tomcat Maven Plugin
  Issue Type: New Feature
  Components: tomcat6, tomcat7
Affects Versions: 2.0
Reporter: Cédric Couralet
Assignee: Olivier Lamy
Priority: Minor


The configuration for a custom logging.properties is not taken into account 
with the tomcat6-7:run goal.
>From what I've seen, the reason is that the configuration for 
>java.util.logging is done before setting the system properties in the same 
>class loader.

I think it could be fixed by putting a call to 
LogManager.getLogManager().readConfiguration(); right after setting the system 
properties. I'm not confident enough on the possible side effects to say it is 
the best solution. 


--
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] [Created] (MTOMCAT-143) contextFile and tomcatUsers defined in pom.xml are not used with target tomcat7:run

[Created]

contextFile and tomcatUsers defined in pom.xml are not used with target 
tomcat7:run
---

 Key: MTOMCAT-143
 URL: https://issues.apache.org/jira/browse/MTOMCAT-143
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0
 Environment: linux
Reporter: Raphaël Zürcher
Assignee: Olivier Lamy (*$^¨%`£)


In the configuration of the plugin into my pom.xml, I've defined the path to 
the contextFile and the tomcatUsers like this :

${appdir}/context.xml
${appdir}/tomcat-users.xml

It works using version 2.0-beta-1 and worked with 2.0-SNAPSHOT until a few days 
ago. Tomcat7 start correctly, but my tomcat-users.xml is not used and I cannot 
authentied services deployed on my tomcat. I use this configuration with 
jenkins for testing.

Is there a regression in 2.0-SNAPSHOT or a new configuration issue ?

--
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] [Created] (MTOMCAT-102) Add a mojo to build a standalone jar to run a web application

[Olivier Lamy (Created) (JIRA)]

Add a mojo to build a standalone jar to run a web application
-

 Key: MTOMCAT-102
 URL: https://issues.apache.org/jira/browse/MTOMCAT-102
 Project: Apache Tomcat Maven Plugin
  Issue Type: New Feature
Reporter: Olivier Lamy
 Fix For: 2.0


goal exec-war will create a standalone jar which will contains all tomcat jars, 
a war to run your application with a simple java -jar 

--
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] [Created] (MTOMCAT-103) Executable War fails to run with a NullPointerException

[Keith Corbin (Created) (JIRA)]

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] [Created] (MTOMCAT-104) Running java -jar from a parent directory causes a Zip file error

[Keith Corbin (Created) (JIRA)]

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] [Created] (MTOMCAT-105) creating executable war failed

[albert kam (Created) (JIRA)]

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
 Fix For: 2.0


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.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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.PluginExecutionException: Execution 
default-cli of goal 
org.apache.tomcat.maven:tomcat7-ma

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

[William Ghelfi (Created) (JIRA)]

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


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.codehaus.plexus.component.configurator.converters.composite.CollectionConverter.fromConfiguration(CollectionConverter.java:170)
at 
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
at 
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
at 
org.codehaus.plexus.component.configurator.Basic

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

[Olivier Lamy (Created) (JIRA)]

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] [Created] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread

[Keith Corbin (Created) (JIRA)]

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


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] [Created] (MTOMCAT-109) org.apache.coyote.http11.Http11NioProtocol not honoured

[Morten Haraldsen (Created) (JIRA)]

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
Reporter: Morten Haraldsen


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] [Created] (MTOMCAT-110) Support Slf4j bridge logger

[Morten Haraldsen (Created) (JIRA)]

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


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] [Created] (MTOMCAT-111) Make extract directory configurable

[Morten Haraldsen (Created) (JIRA)]

Make extract directory configurable
---

 Key: MTOMCAT-111
 URL: https://issues.apache.org/jira/browse/MTOMCAT-111
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat7
Reporter: Morten Haraldsen
Assignee: Olivier Lamy
 Fix For: 2.0


If one is launching the application bundled as an executable jar/war, it would 
be nice not to have to be in the directory you want to extract the war file.

Now you have Tomcat7Runner.java:86: 
public File extractDirectory = new File( ".extract" );

Could you make this an option like -extractDirectory when launching?

Thanks again!

--
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] [Created] (MTOMCAT-113) Show progress on WAR uploads

[Adrian Petrescu (Created) (JIRA)]

Show progress on WAR uploads


 Key: MTOMCAT-113
 URL: https://issues.apache.org/jira/browse/MTOMCAT-113
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Reporter: Adrian Petrescu
Priority: Minor


This may seem frivolous, but it would be really great to have some indication 
of progress when uploading a WAR to a remote server, as part of a tomcat:deploy 
or tomcat:redeploy goal. I often find myself uploading large WARs using Maven, 
and I have no idea how long I should expect to be waiting.

--
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] [Created] (MTOMCAT-114) Add an archetype project sample

[Olivier Lamy (Created) (JIRA)]

Add an archetype project sample
---

 Key: MTOMCAT-114
 URL: https://issues.apache.org/jira/browse/MTOMCAT-114
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Reporter: Olivier Lamy
Assignee: Olivier Lamy
 Fix For: 2.0


the archetype will be a multi module maven project with jar and war module.
The webapp will have a selenium test to show how to start tomcat with the 
plugin to run selenium tests.

--
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] [Created] (MTOMCAT-115) Allow configuration of URI encoding for executable war

[Olivier Lamy (Created) (JIRA)]

Allow configuration of URI encoding for executable war
--

 Key: MTOMCAT-115
 URL: https://issues.apache.org/jira/browse/MTOMCAT-115
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat6, tomcat7
Affects Versions: 1.1
Reporter: Dan C
Assignee: Olivier Lamy
Priority: Minor
 Fix For: 2.0


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] [Created] (MTOMCAT-116) NonRepeatableRequestException when executing goal tomcat6:deploy

[Michael Yockey (Created) (JIRA)]

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.DefaultRequestDirector.execute(DefaultRequestDirector.java:515)
at 
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923)
... 29 more

--
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/s

[jira] [Created] (MTOMCAT-117) Sporadic problem invoking tomcat manager during deploy goal

[Daniel Triphaus (Created) (JIRA)]

Sporadic problem invoking tomcat manager during deploy goal
---

 Key: MTOMCAT-117
 URL: https://issues.apache.org/jira/browse/MTOMCAT-117
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6
Affects Versions: 2.0
 Environment: Linux RHEL, Tomcat 6.0.26, tomcat6-maven-plugin 
2.0-SNAPSHOT
Reporter: Daniel Triphaus
Assignee: Olivier Lamy


We (just sometimes, so url, user, password and so on are definitely correct) 
have problems invoking tomcat manager during deploy goal and get the error 
stacktrace below.

Note: Restarting tomcat mostly solves the problem.

Thanks for any help!

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3:22.619s
[INFO] Finished at: Fri Jan 27 13:47:18 CET 2012
[INFO] Final Memory: 30M/409M
[INFO] 
mavenExecutionResult exceptions not empty
message : Failed to execute goal 
org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy (default) on 
project XXX: Cannot invoke Tomcat manager
cause : Cannot invoke Tomcat manager
Stack trace : 
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy (default) on 
project XXX: 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.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
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.launchStandard(Launcher.java:329)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:112)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
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:101)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 27 more
Caused by: java.io.IOException: Server returned HTTP response code: 403 for 
URL: http:///manager/deploy?path=%2F&update=true
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at 
org.apache.tomcat.maven.common.deployer.TomcatManager.invoke(TomcatManager.java:607)
at 
org.apache.tomcat.maven.common.deployer.TomcatManager.deployImpl(TomcatManager.java:660)
at 
org.apache.tomcat.maven.common.deployer.TomcatManager.deploy(Tom

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

[Dave Lund (Created) (JIRA)]

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] [Created] (MTOMCAT-119) tomcat7:run-war fails because it expects META-INF\context.xml

[Samuel Langlois (Created) (JIRA)]

tomcat7:run-war fails because it expects META-INF\context.xml
-

 Key: MTOMCAT-119
 URL: https://issues.apache.org/jira/browse/MTOMCAT-119
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Samuel Langlois
Assignee: Olivier Lamy


run-war and run-war-only goals fail on tomcat7 plugin, looking for the file 
=META-INF\context.xml=

How to reproduce:
* Use the archetype to create a project
mvn archetype:generate -DarchetypeGroupId=org.apache.tomcat.maven 
-DarchetypeArtifactId=tomcat-maven-archetype -DarchetypeVersion=2.0-beta-1
* Build it
* cd basic-webapp
* mvn org.apache.tomcat.maven:tomcat6-maven-plugin:run-war
=> works fine
* mvn org.apache.tomcat.maven:tomcat7-maven-plugin:run
=> works fine
* mvn org.apache.tomcat.maven:tomcat7-maven-plugin:run-war
-> kaboom
{code}
[INFO] --- tomcat7-maven-plugin:2.0-beta-1:run-war (default-cli) @ basic-webapp 
---
[INFO] Running war on http://localhost:9090/
[INFO] Using existing Tomcat server configuration at 
C:\Users\SAMUEL~1.LAN\AppData\Local\Temp\com.antelink.toto\basic-webapp\target\tomcat
févr. 16, 2012 6:56:24 PM org.apache.coyote.AbstractProtocol init
Infos: Initializing ProtocolHandler ["http-bio-9090"]
févr. 16, 2012 6:56:24 PM org.apache.catalina.core.StandardService startInternal
Infos: Starting service Tomcat
févr. 16, 2012 6:56:24 PM org.apache.catalina.core.StandardEngine startInternal
Infos: Starting Servlet Engine: Apache Tomcat/7.0.25
févr. 16, 2012 6:56:24 PM org.apache.catalina.startup.ContextConfig 
processContextConfig
Grave: Missing context.xml: 
file:/C:/Users/SAMUEL~1.LAN/AppData/Local/Temp/com.antelink.toto/basic-webapp/target/basic-webapp-1.0-SNAPSHOT/META-INF/context.xml
java.io.FileNotFoundException: 
C:\Users\SAMUEL~1.LAN\AppData\Local\Temp\com.antelink.toto\basic-webapp\target\basic-webapp-1.0-SNAPSHOT\META-INF\context.xml
 (Le fichier spécifié est introuvable)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:138)
at java.io.FileInputStream.(FileInputStream.java:97)
at 
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at 
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at java.net.URL.openStream(URL.java:1035)
at 
org.apache.catalina.startup.ContextConfig.processContextConfig(ContextConfig.java:565)
at 
org.apache.catalina.startup.ContextConfig.contextConfig(ContextConfig.java:546)
at 
org.apache.catalina.startup.ContextConfig.init(ContextConfig.java:784)
at 
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:318)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:401)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:110)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
{code}

--
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] [Created] (MTOMCAT-121) Plugin gets 403 unauthorized errors after upgrading from SNAPSHOT

[Eamonn Linehan (Created) (JIRA)]

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] [Created] (MTOMCAT-122) Maven and dependencies for $CATALINA/lib

[James Apfel (Created) (JIRA)]

Maven and dependencies for $CATALINA/lib


 Key: MTOMCAT-122
 URL: https://issues.apache.org/jira/browse/MTOMCAT-122
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Reporter: James Apfel


*Me* {quote}I'm working on a project that requires me to replace Tomcat's
SessionManager. I've created a src/main/webapp/META-INF/context.xml
(it defines the custom Manager) and I've edited my Maven pom file to
include the requires JARs in the tomcat6-maven-plugin's dependencies
section (see below) but I'm not sure if that actually refers to
$CATALINA/lib or if these dependencies are for something else. It's
failing with a ClassNotFoundException (it can't find the Manager class
as defined in context.xml).

Thanks,
 James


  org.apache.tomcat.maven
  tomcat6-maven-plugin
  2.0-SNAPSHOT
  

  spy
  spymemcached
  2.8.0
  runtime


  de.javakaffee.msm
  memcached-session-manager-tc6
  1.6.1
  runtime


  de.javakaffee.msm
  msm-kryo-serializer
  1.6.0
  runtime

  
{quote}

*Oliver Lamy* {quote}Arghh :-)
The dependencies for the tomcat start (the plugin create a class
loader with needed embeded tomcat jars) are limited to groupId
org.apache.tomcat
Can you load an issue ? https://issues.apache.org/jira/browse/MTOMCAT
That's an easy fix.{quote}


--
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] [Created] (MTOMCAT-123) Can't add test scoped dependency filters to web.xml

[Nathan Schile (Created) (JIRA)]

Can't add test scoped dependency filters to web.xml
---

 Key: MTOMCAT-123
 URL: https://issues.apache.org/jira/browse/MTOMCAT-123
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1, 2.0
 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 11:31:09-0600)
Maven home: /usr/local/Cellar/maven/3.0.3/libexec
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.6.8", arch: "i386", family: "mac"
Reporter: Nathan Schile
Assignee: Olivier Lamy


When a Filter that is from a test scoped dependency is added to the web.xml, a 
ClassNotFoundException is thrown when starting the Tomcat server.  Everything 
runs fine when dependency is changed to compile.


org.apache.tomcat.maven
tomcat7-maven-plugin
2.0-beta-1


tomcat-run

run

pre-integration-test

/
true
true

${basedir}/src/test/webapp
true



tomcat-shutdown

shutdown

post-integration-test




--
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] [Created] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters

[patrick garcia (Created) (JIRA)]

tomcat-maven-archetype unused generation parameters
---

 Key: MTOMCAT-124
 URL: https://issues.apache.org/jira/browse/MTOMCAT-124
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
Affects Versions: 2.0-beta-1
Reporter: patrick garcia
Priority: Trivial


I found several problems on the superb and very useful "tomcat-maven-archetype"

The improvement I propos are the followings:

1/
"groupId" and "version" can have default values but should be prompt for user 
value the same way as for "version" of 
"org.apache.maven.archetypes:maven-archetype-quickstart:1.1"


"org.apache.maven.archetypes:maven-archetype-quickstart:1.1" proposes a default 
"version" and prompt the user for modification at the same time. Pressing enter 
validate the default value.



2/
Following variables are not in used:
artifactId-api
artifactId-api-impl
artifactId-webapp
artifactId-webapp-exec
artifactId-webapp-it

This variables should impact the "mvn archetype:generate" behaviour



3/
I propos to change the default values of :
artifactId-api = ${artifactId}-api
artifactId-api-impl = ${artifactId}-api-impl
artifactId-webapp = ${artifactId}-webapp
artifactId-webapp-exec = ${artifactId}-webapp-exec
artifactId-webapp-it = ${artifactId}-webapp-it


4/
rootArtifactId cat be renamed as artifactId with no default value



I will propos patches for this later. I, first, have to understand "archetype" 
framework.


--
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] [Created] (MTOMCAT-125) mvn tomcat7:run got "javax.naming.NameNotFoundException: Name jdbc is not bound in this Context"

[guofeng zhang (Created) (JIRA)]

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,
  


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:
   

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] [Created] (MTOMCAT-129) Regression of MTOMCAT-54 in tomcat7-maven-plugin

[Justin Wunderle (Created) (JIRA)]

Regression of MTOMCAT-54 in tomcat7-maven-plugin


 Key: MTOMCAT-129
 URL: https://issues.apache.org/jira/browse/MTOMCAT-129
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Justin Wunderle
Assignee: Olivier Lamy


In r1180428, the code that fixed MTOMCAT-54 was removed, so inside a webapp 
that is deployed at "/", request.getContextPath() will return "/" when it 
should return "".

The bug is that, in general, trailing slashes on the path variable should be 
removed (it's not really a special case for "/", though it causes the worst 
effects in that case)

See this link for the rules for how the contextPath should look: 
http://tomcat.apache.org/tomcat-7.0-doc/servletapi/javax/servlet/http/HttpServletRequest.html#getContextPath()

--
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] [Created] (MTOMCAT-130) finalName doesn't seem to be used when using mvn tomcat:deploy or configuration is ignored?

[Rick Reumann (Created) (JIRA)]

finalName doesn't seem to be used when using mvn tomcat:deploy or configuration 
is ignored?
---

 Key: MTOMCAT-130
 URL: https://issues.apache.org/jira/browse/MTOMCAT-130
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6
Affects Versions: 2.0-beta-1
 Environment: MacOSX, Java6
Reporter: Rick Reumann
Assignee: Olivier Lamy


Maybe I'm missing something basic, so sorry if this is the wrong place to post 
this, but I have a finalName set that is defined and a typical mvn clean 
install builds the war file just fine using the finalName. However, when I run 
mvn tomcat:deploy, it seems to ignore the finalName that is set. I'm thinking 
the issue might be that the configuration seems to be ignored since I also have 
update set to true in the configuration and doing mvn tomcat:deploy isn't 
undeploying the old application even though I have update set to true.

Here is the snippet of relevant info:


my-app

org.apache.tomcat.maven
tomcat6-maven-plugin
2.0-beta-1

true

${project.build.directory}/${project.build.finalName}.war




--
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] [Created] (MTOMCAT-131) maven-Tomcat-plugin Overlay Task execution fails in windows with java.io.IOException[The filename, directory name, or volume label syntax is incorrect], when targetPath

[Tony Kollamparambil (Created) (JIRA)]

maven-Tomcat-plugin Overlay Task execution fails in windows with 
java.io.IOException[The filename, directory name, or volume label syntax is 
incorrect], when targetPath is present
---

 Key: MTOMCAT-131
 URL: https://issues.apache.org/jira/browse/MTOMCAT-131
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
 Environment: Fails in Windows, it works fine in Mac & Linux/Unix
Reporter: Tony Kollamparambil
Priority: Minor


Thanks for introducing the "Overlay concept", which is very helpful.  we have a 
scenario in which we need to overlay a war file over the other. we have 
successfully  implemented the overlay in our project.

maven install is failing with java.io exception when we build the module in 
WINDOWS with some path in the overlays:overlay:targetpath tag(its works fine in 
the mac/linux/unix/solaris).   

Trace :
ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.2:war 
(default-war) on project enrollment-rest: Failed to copy file for overlay [ id 
xxx:]: The filename, directory name, or volume label syntax is 
incorrect -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-war-plugin:2.2:war (default-war) on project 
xxx-: Failed to copy file for overlay [ id xxx:].

Root Cause:
As per the analysis that we had performed, its a code bug. Please refer line# 
84-88 present in the 
http://code.google.com/p/maven-alfresco-archetypes/source/browse/trunk/plugins/maven-amp-plugin/src/main/java/org/alfresco/maven/plugin/amp/packaging/OverlayPackagingTask.java?r=127.
 

ie; 
 String targetPath = overlay.getTargetPath();
if (!targetPath.endsWith( "/" ))
{
targetPath = targetPath + "/";
}

by considering the above code snippet as a source of truth, windows will not 
recognize the forward slash ("/") as a valid file separator.  file separator 
would vary from OS to OS(it works fine in linux and mac, since the file 
separator for these operating systems are "/").

System.getProperties("file.separator") can be used for computing the 
file.separator.  Please do the needful. Thanks in advance

Stack Trace : 
[DEBUG] OverlayPackagingTask performPackaging overlay.getTargetPath() 
C:\projects\xxx\yy\target
[INFO] Processing overlay [ id xxx:]
[DEBUG] Overlay [ id xxx:] was already unpacked
ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.2:war 
(default-war) on project enrollment-rest: Failed to copy file for overlay [ id 
xxx:]: The filename, directory name, or volume label syntax is 
incorrect -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-war-plugin:2.2:war (default-war) on project 
xxx-: Failed to copy file for overlay [ id xxx:].
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:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.pl

[jira] [Created] (MTOMCAT-132) cookie jession submit by hidden

[hongzhou sun (Created) (JIRA)]

cookie jession submit by hidden
---

 Key: MTOMCAT-132
 URL: https://issues.apache.org/jira/browse/MTOMCAT-132
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat6
Affects Versions: 1.1
 Environment: tomcat6 jdk1.5.09
Reporter: hongzhou sun
Assignee: Olivier Lamy
Priority: Minor


On the condition that the ie's cookie is disable! But I also want to submit the 
jsessionid by the  
syntax.
The result is there is a new Session was created on the server instead of the 
old Session which i want to keep.
Is there anybody who can tell me the reason?
And I also don't want to use the Url rewrite to resolve the Session content 
trans.'Cause it seems to be some security problems.

Best regards! Thanks!

--
This message 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] [Created] (MTOMCAT-133) Servlet mapping to "/" does not work

[Gildas Cuisinier (Created) (JIRA)]

Servlet mapping to "/" does not work 
-

 Key: MTOMCAT-133
 URL: https://issues.apache.org/jira/browse/MTOMCAT-133
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0
 Environment: Mac OS X, Apple JRE 1.6
Reporter: Gildas Cuisinier
Assignee: Olivier Lamy (*$^¨%`£)


Using the Servlet 3.0 possibilities to add and configure servlet 
(ServletContainerInitializer through Spring 3.1 WebApplicationInitializer), I 
try to map a servlet  "/", but is not working properly.
The servlet is started correctly, but the mapping does not work. 
If I replace "/" by "test/*", everything work perfectly.

For information, the "/" mapping works well in a standalone tomcat 7.0.25.

I put a sample project on github that reproduce the bug : 
https://github.com/hikage/tomcat7-bug


--
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] [Created] (MTOMCAT-134) Empty additionalClasspathDir causes NPE in RunMojo.java

[John Meyer (Created) (JIRA)]

Empty additionalClasspathDir causes NPE in RunMojo.java
---

 Key: MTOMCAT-134
 URL: https://issues.apache.org/jira/browse/MTOMCAT-134
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6, tomcat7
Affects Versions: 2.0-beta-1
 Environment:   
org.apache.tomcat.maven
tomcat7-maven-plugin
2.0-SNAPSHOT

9090
/myapp-1.0



false







tomcat-run


exec-war-only

package

/myapp-1.0




Reporter: John Meyer
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Minor


Hit an issue where specifying an empty additionalClasspathDir caused a 
mysterious NPE and no explaination of what was wrong

--
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] [Created] (MTOMCAT-135) tomcat7:run does not load HandlesTypes in application classes

[Gildas Cuisinier (Created) (JIRA)]

tomcat7:run does not load HandlesTypes in application classes
-

 Key: MTOMCAT-135
 URL: https://issues.apache.org/jira/browse/MTOMCAT-135
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0
 Environment: Mac OS X, Apple JDK 1.6
Reporter: Gildas Cuisinier
Assignee: Olivier Lamy (*$^¨%`£)


Spring 3.1 brings a SpringServletContainerInitializer, that has annotation 
@HandlesTypes(WebApplicationInitializer.class).

In my application, I have a WebApplicationInitializer directly in my war. This 
one is compiled and put in WEB-INF/classes.

When launching with tomcat7:run-war, my WebApplicationInitializer is correctly 
found by tomcat and provided to SpringServletContainerInitializer.
But with tomcat7:run, I've this line in logs :

INFO: No Spring WebApplicationInitializer types detected on classpath

It seems that the problems come from the ContextConfig classe (from tomcat 
source), in method webConfig that specificly search a "WEB-INF/classes" : 

  // Step 4. Process /WEB-INF/classes for annotations
// This will add any matching classes to the typeInitializerMap
if (ok) {
// Hack required by Eclipse's "serve modules without
// publishing" feature since this backs WEB-INF/classes by
// multiple locations rather than one.
NamingEnumeration listBindings = null;
try {
try {
listBindings = context.getResources().listBindings(
"/WEB-INF/classes");
} catch (NameNotFoundException ignore) {
// Safe to ignore
}




--
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] [Created] (MTOMCAT-136) Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal

[Leigh Anderson (Created) (JIRA)]

Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run 
goal
---

 Key: MTOMCAT-136
 URL: https://issues.apache.org/jira/browse/MTOMCAT-136
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
 Environment: Java 1.6.0_26, Maven 3.0.4, OS X 10.7.3
Reporter: Leigh Anderson
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Minor


I'm trying to start a web application with 'mvn tomcat7:run'. It seems
that with the configuration below it fails with the following error:

[INFO] 

[ERROR] Failed to execute goal 
org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli) on 
project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.  

I have also tried
* 'mvn tomcat:run-war', which seems to get past this point, but then 
the application will not start because the 'additionalClasspathDir' property is 
not supported by the 'run-war' goal.
* removing 'useSeparateTomcatClassLoader' which then doesn't load the 
Spring instrumenting class loader required to use AspectJ LTW, specified in 
context.xml. I have confirmed that I get the same 'no such archiver' error if I 
remove the context.xml, so I don't believe this to be the cause.

Plugin configuration:


org.apache.tomcat.maven
tomcat7-maven-plugin
2.0-beta-1



true
localhost
9090
8443

9090
8443
/
false

   
${project.basedir}/config


true



org.springframework

spring-instrument-tomcat
${spring.version}







--
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] [Created] (MTOMCAT-137) Adding a static context to tomcat for static files like images, js, html etc.

[Gaurav Vishnoi (Created) (JIRA)]

Adding a static context to tomcat for static files like images, js, html etc.
-

 Key: MTOMCAT-137
 URL: https://issues.apache.org/jira/browse/MTOMCAT-137
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat6
Affects Versions: 2.0-beta-1
 Environment: Eclipse on windows platform with internal tomcat server.
Reporter: Gaurav Vishnoi
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Minor
 Fix For: 2.0-beta-1


There is no configuration available in the current tomcat maven plugin to add a 
static context. If you want to include static context you would need an 
external Apache server hosting your static files. Instead of setting the Apache 
I wanted to include the static context in my pom.xml. So, I modified the tomcat 
maven plugin to include the configurations for static context. 
I have created a patch and will attach it here.

--
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] [Created] (MTOMCAT-138) Cannot define the embedded Tomcat version

[Morten Haraldsen (Created) (JIRA)]

Cannot define the  embedded Tomcat version
--

 Key: MTOMCAT-138
 URL: https://issues.apache.org/jira/browse/MTOMCAT-138
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
 Environment: Ubuntu 11.10
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /home/mha/progs/apache-maven-3.0.3
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-17-generic", arch: "amd64", family: "unix"
Reporter: Morten Haraldsen
Assignee: Olivier Lamy (*$^¨%`£)


You have documented how to change the version of embedded Tomcat here: 
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/examples/adjust-embedded-tomcat-version.html

However, using Maven 3, this is no longer possible as it is using static 
evaluation of properties, i.e. cannot override. See 
http://maven.40175.n5.nabble.com/Variables-interpolation-dynamic-in-Maven-2-static-in-Maven-3-td3360336.html

(This is currently a showstopper, as I need to use 7.0.27 because of a fix in 
NIO connector of 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] [Created] (MTOMCAT-139) All static resources gives error 404

[Morten Haraldsen (Created) (JIRA)]

All static resources gives error 404


 Key: MTOMCAT-139
 URL: https://issues.apache.org/jira/browse/MTOMCAT-139
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0
Reporter: Morten Haraldsen
Assignee: Olivier Lamy (*$^¨%`£)


Using beta-1 it works fine, but using SNAPSHOT gives 404 for all static 
resources.
Looking at https://issues.apache.org/jira/browse/MTOMCAT-137 and the code I 
suspect this is the culprit. (I'm not using the static context feature)

--
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] [Created] (MTOMCAT-140) Allow specifying the classloader to use for loading webapps.

[Leigh Anderson (Created) (JIRA)]

Allow specifying the classloader to use for loading webapps.


 Key: MTOMCAT-140
 URL: https://issues.apache.org/jira/browse/MTOMCAT-140
 Project: Apache Tomcat Maven Plugin
  Issue Type: Improvement
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Leigh Anderson
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Minor


If one uses a context.xml with a  element to specify the class loader 
implementation to use with the tomcat7:run goal, this causes Tomcat to override 
the WebAppLoader carefully created by the plugin, without the
benefit of a properly configured class path.

The attached patch adds a  property to configure which class 
loader implementation to use. This is probably of limited utility as most 
classes will be loaded by the parent classloader anyway. 



--
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] [Created] (MTOMCAT-141) Context root "/" not workin for Tomcat 7

[Dave Syer (Created) (JIRA)]

Context root "/" not workin for Tomcat 7


 Key: MTOMCAT-141
 URL: https://issues.apache.org/jira/browse/MTOMCAT-141
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Dave Syer
Assignee: Olivier Lamy (*$^¨%`£)


It looks like the fix for MTOMCAT-54 was only applied to the Tomcat 6 plugin.

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



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

[jira] [Created] (MTOMCAT-142) contextFile path="..." ignored when using tomcat:run

[Dave Syer (Created) (JIRA)]

contextFile path="..." ignored when using tomcat:run


 Key: MTOMCAT-142
 URL: https://issues.apache.org/jira/browse/MTOMCAT-142
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0-beta-1
Reporter: Dave Syer
Assignee: Olivier Lamy (*$^¨%`£)


contextFile path="..." ignored when using tomcat:run.  I have been trying to 
use a custom context file (with contextFile config param).  I can see the 
context being logged in the console, but the path attribute is ignored, and for 
all I know so are other settings (the app is always deployed with 
path=${project.artifactId}).

--
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] [Created] (MTOMCAT-144) resourcePaths returns null

[Per Wramdemark (Created) (JIRA)]

resourcePaths returns null
--

 Key: MTOMCAT-144
 URL: https://issues.apache.org/jira/browse/MTOMCAT-144
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat7
Affects Versions: 2.0
 Environment: windows tomcat7:run
Reporter: Per Wramdemark
Assignee: Olivier Lamy (*$^¨%`£)


Hi,
Suddenly a few days ago (unclear exactly when) when i run the code below it 
returns null. It worked two weeks ago and still works if I step back to version 
2.0-beta-1.
I'm running the goal "tomcat7:run"

code that returns null:
getServletContext().getResourcePaths(path);


pom config:
org.apache.tomcat.maven
tomcat7-maven-plugin

2.0-SNAPSHOT

--
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] [Created] (MTOMCAT-145) [2.0-beta-1] Unable to deploy

[Jeff Vincent (Created) (JIRA)]

[2.0-beta-1] Unable to deploy 
--

 Key: MTOMCAT-145
 URL: https://issues.apache.org/jira/browse/MTOMCAT-145
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6
Affects Versions: 2.0-beta-1
 Environment: Maven 3.0.4 command-line on Windows 7 x64
Tomcat 6.0.13 
CentOs 4.9
Reporter: Jeff Vincent
Assignee: Olivier Lamy (*$^¨%`£)
Priority: Critical


I have been using the codhaus version of the tomcat-maven-plugin and am trying 
to switch to the latest Apache Tomcat Maven Plugin.

Deploy works with the codhaus version using 'mvn tomcat:redeploy -Pdev02`.  The 
username/password are normally in my profile settings.  

Deploy fails with apache version using:  'mvn tomcat6:redeploy -Pdev02'.  I've 
specified a  entry in the settings.xml, and specified the same value 
in the  sectino of the the plugin  section to avoid 
"[DEBUG] No server specified for authentication - using defaults" errors.

Below is my maven profile.  I've tried changing the URL when running the 
tomcat6:deploy/redeploy targets with and without a trailing '/text'.  I get a 
404 with the '/text' and an error "Cannot invoke Tomcat manager" without the 
'/text'.

Without the '/text' in the URL, it appears to upload the war as it shows a 
progress indicator then fails with the 




  dev02
  
false
  
  

  
org.apache.tomcat.maven
tomcat6-maven-plugin
2.0-beta-1

  war
  http://10.12.4.2/manager
  true
  UTF-8
  UTF-8
  HTTP/1.1
  true
  dev02

  

  



//- MAVEN OUTPUT 
[DEBUG] Configuring mojo 
org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-beta-1:redeploy from plugin 
realm 
ClassRealm[plugin>org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-beta-1, 
parent: sun.misc.Launcher$AppClassLoader@3326b249]
[DEBUG] Configuring mojo 
'org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-beta-1:redeploy' with basic 
configurator -->
[DEBUG]   (f) charset = UTF-8
[DEBUG]   (f) contextFile = 
C:\Users\jvincent\Dev\Java\Domain\target\Domain-2012.04.04-SNAPSHOT\META-INF\context.xml
[DEBUG]   (f) ignorePackaging = false
[DEBUG]   (f) mode = war
[DEBUG]   (f) packaging = war
[DEBUG]   (f) path = /Domain
[DEBUG]   (f) server = dev02
[DEBUG]   (f) update = true
[DEBUG]   (f) url = http://10.12.4.2/manager
[DEBUG]   (f) version = 2.0-beta-1
[DEBUG]   (f) warFile = 
C:\Users\jvincent\Dev\Java\Domain\target\Domain-2012.04.04-SNAPSHOT.war
[DEBUG] -- end configuration --
[INFO] Deploying war to http://10.12.4.2/Domain  
Uploading: http://10.12.4.2/manager/deploy?path=%2FDomain&update=true

[Progress Indicator..]

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 5.490s
[INFO] Finished at: Tue Apr 17 17:51:59 MDT 2012
[INFO] Final Memory: 8M/244M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-beta-1:redeploy (default-cli) 
on project Domain: Cannot invoke Tomcat manager: ClientProtocolException: 
Cannot retry request with a non-repeatable request entity. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-beta-1:redeploy (default-cli) 
on project Domain: 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:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25

[jira] [Created] (MTOMCAT-146) Multiple executions of run-war-only has Valve problems at shutdown

[Benson Margulies (Created) (JIRA)]

Multiple executions of run-war-only has Valve problems at shutdown
--

 Key: MTOMCAT-146
 URL: https://issues.apache.org/jira/browse/MTOMCAT-146
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6
Affects Versions: 2.0-beta-1
Reporter: Benson Margulies
Assignee: Olivier Lamy (*$^¨%`£)


{noformat}
INFO: Stopping Coyote HTTP/1.1 on http-51155
Apr 18, 2012 8:19:17 AM org.apache.catalina.core.StandardPipeline 
unregisterValve
INFO: Can't unregister valve 
org.apache.catalina.core.StandardEngineValve[localEngine]
javax.management.InstanceNotFoundException: 
localEngine:type=Valve,name=StandardEngineValve
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506)
at 
org.apache.catalina.core.StandardPipeline.unregisterValve(StandardPipeline.java:322)
at 
org.apache.catalina.core.StandardPipeline.stop(StandardPipeline.java:275)
at org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1103)
at org.apache.catalina.core.StandardEngine.stop(StandardEngine.java:468)
at org.apache.catalina.startup.Embedded.stop(Embedded.java:867)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.tomcat.maven.common.run.EmbeddedRegistry.shutdownAll(EmbeddedRegistry.java:110)
at 
org.apache.tomcat.maven.plugin.tomcat6.ShutdownMojo.execute(ShutdownMojo.java:63)
{noformat}

{code}
  
  org.apache.tomcat.maven
  tomcat6-maven-plugin
  2.0-beta-1



tomcat-run

run-war-only

pre-integration-test

/
${tomcat.port}
UTF-8

${project.build.directory}/webapps/solr/
true
true
src/test/context.xml

  
${project.build.directory}/solr_home
  
${project.build.directory}/bt-rni-solr3x-plugins.jar
  ../../../../..





tomcat2-run

run-war-only

pre-integration-test

/
${tomcat2.port}
UTF-8

${project.build.directory}/webapps/solr2/

${project.build.directory}/tomcat2
true
true
src/test/context.xml

  
${project.build.directory}/solr2
  
${project.build.directory}/bt-rni-solr3x-plugins.jar
  ../../../../..






tomcat-shutdown

  
shutdown

post-integration-test



{code}

--
This message 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] [Created] (MTOMCAT-100) support war overlay to add war external dependencies in tomcat run

[Olivier Lamy (Created) (JIRA)]

support war overlay to add war external dependencies in tomcat run 
---

 Key: MTOMCAT-100
 URL: https://issues.apache.org/jira/browse/MTOMCAT-100
 Project: Maven 2.x Tomcat Plugin
  Issue Type: Improvement
Reporter: Olivier Lamy
Assignee: Olivier Lamy
 Fix For: 2.0


if activated /WEB-INF/lib/*.jar and /WEB-INF/classes will added to web app 
classloader when using tomcat*:run

--
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] [Created] (MTOMCAT-101) Add the ability to deploy to a Tomcat instance on the filesystem rather than via HTTP

[Steve Swinsburg (Created) (JIRA)]

Add the ability to deploy to a Tomcat instance on the filesystem rather than 
via HTTP
-

 Key: MTOMCAT-101
 URL: https://issues.apache.org/jira/browse/MTOMCAT-101
 Project: Maven 2.x Tomcat Plugin
  Issue Type: New Feature
  Components: tomcat6, tomcat7
Reporter: Steve Swinsburg
Assignee: Olivier Lamy


It would be great to have the ability to deploy a webapp to Tomcat without 
using HTTP and the Tomcat Manager, by simply doing a filesystem copy of the 
built war file to the location specified.

We currently use an ant profile to do this, but want to replace this with a 
proper plugin.

We will be looking at contributing this feature in the near future.

--
This message 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] [Created] (MTOMCAT-112) file path inside ${basedir}/src/main/tomcatconf is not preserved

[Fabio Cechinel Veronez (Created) (JIRA)]

file path inside ${basedir}/src/main/tomcatconf is not preserved


 Key: MTOMCAT-112
 URL: https://issues.apache.org/jira/browse/MTOMCAT-112
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6
Affects Versions: 2.0
 Environment: $ uname --all
Linux 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 
i686 i386 GNU/Linux

$ mvn -version
Apache Maven 3.0.3 (r1075438; 2011-02-28 14:31:09-0300)
Maven home: /home/veronez/install/java/apache-maven-3.0.3
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-14-generic-pae", arch: "i386", family: "unix"
Reporter: Fabio Cechinel Veronez
    Assignee: Olivier Lamy


Hello

I have created a file under ${basedir}/src/main/tomcatconf using the folder 
structure /Catalina/localhost/context#subcontext.xml

I expected to have this files copied to 
/target/tomcat/conf/Catalina/localhost/context#subcontext.xml but instead it is 
copied to /target/tomcat/conf/context#subcontext.xml.

My intention is to create subcontext to map resources to an folder located 
outside of my application. As explained at 
http://harkiran-howtos.blogspot.com/2009/08/map-external-directory-into-your.html.


Ps.: I'm not sure if it is a bug or expected behavior, i would sent this 
question to a mail list but i couldn't find it... sorry if i miss posted it 
here.

--
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] [Created] (MTOMCAT-128) The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml option

[Gilberto C Andrade (Created) (JIRA)]

The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml 
option
-

 Key: MTOMCAT-128
 URL: https://issues.apache.org/jira/browse/MTOMCAT-128
 Project: Apache Tomcat Maven Plugin
  Issue Type: Bug
  Components: tomcat6, tomcat7
Affects Versions: 2.0-beta-1
 Environment: openSUSE 12.1 32Bits
Reporter: Gilberto C Andrade
Assignee: Olivier Lamy
Priority: Trivial
 Fix For: 2.0


In our project(jpa-spring-wicket) we need to filter the web.xml file, changing 
some placeholder and putting it (the web.xml) in 
${project.build.directory}/${project.build.finalName}/WEB-INF/web.xml.
Using tomcat6-maven-plugin it find the correct file, but fail when parsing it:

Caused by: java.lang.IllegalArgumentException: Duplicate context initialization 
parameter contextConfigLocation
at 
org.apache.catalina.core.StandardContext.addParameter(StandardContext.java:2661)
... 52 more
Mar 16, 2012 11:49:12 AM org.apache.catalina.startup.ContextConfig 
applicationWebConfig
SEVERE: Parse error in application web.xml file at 
jndi:/localhost/a2p/WEB-INF/web.xml
org.xml.sax.SAXParseException; systemId: jndi:/localhost/a2p/WEB-INF/web.xml; 
lineNumber: 15; columnNumber: 21; Error at (15, 21: Duplicate context 
initialization parameter contextConfigLocation
at 
org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2806)


Using tomcat7-maven-plugin it find the correct file, but ignores it so using 
the original file which contain the ${placeholder}. Thus not initializing the 
application:

INFO  - ContextLoader  - Root WebApplicationContext: initialization 
completed in 7808 ms
INFO  - WebXmlFile - web.xml: url mapping found for filter with 
name A2P: [/*]
Mar 16, 2012 12:08:16 PM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter A2P
java.lang.IllegalArgumentException: Invalid configuration type: 
'${wicket.MODE}'.  Must be "development" or "deployment".
at 
org.apache.wicket.protocol.http.WebApplication.getConfigurationType(WebApplication.java:670)
at org.apache.wicket.Application.configure(Application.java:297)
at 
org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplication.java:613)
at org.apache.wicket.Application.initApplication(Application.java:806)
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346)
at 
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286)
at 
org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:277)
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258)

 

The plugin configuration:

  
org.apache.tomcat.maven
tomcat7-maven-plugin
2.0-beta-1

${project.build.finalName}

${project.build.directory}/${project.build.finalName}/WEB-INF/web.xml




I have the jetty plugin setup as well and working, so I would try with tomcat 
but without success until now.
Regards

--
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