[jira] [Updated] (MTOMCAT-129) Regression of MTOMCAT-54 in tomcat7-maven-plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-129: - Fix Version/s: 2.0 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 Fix For: 2.0 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] [Updated] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters
[
https://issues.apache.org/jira/browse/MTOMCAT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-124:
-
Fix Version/s: 2.0
Assignee: Olivier Lamy
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
Assignee: Olivier Lamy
Priority: Trivial
Labels: archetype, maven, tomcat
Fix For: 2.0
Attachments: MTOMCAT-124-tomcat-maven-archetype.patch
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] [Updated] (MTOMCAT-119) tomcat7:run-war fails because it expects META-INF\context.xml
[
https://issues.apache.org/jira/browse/MTOMCAT-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-119:
-
Fix Version/s: 2.0
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
Fix For: 2.0
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.init(FileInputStream.java:138)
at java.io.FileInputStream.init(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] [Updated] (MTOMCAT-122) Maven and dependencies for $CATALINA/lib
[
https://issues.apache.org/jira/browse/MTOMCAT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-122:
-
Fix Version/s: 2.0
Assignee: Olivier Lamy
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
Assignee: Olivier Lamy
Fix For: 2.0
*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
plugin
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat6-maven-plugin/artifactId
version2.0-SNAPSHOT/version
dependencies
dependency
groupIdspy/groupId
artifactIdspymemcached/artifactId
version2.8.0/version
scoperuntime/scope
/dependency
dependency
groupIdde.javakaffee.msm/groupId
artifactIdmemcached-session-manager-tc6/artifactId
version1.6.1/version
scoperuntime/scope
/dependency
dependency
groupIdde.javakaffee.msm/groupId
artifactIdmsm-kryo-serializer/artifactId
version1.6.0/version
scoperuntime/scope
/dependency
/dependencies
/plugin{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] [Updated] (MTOMCAT-122) add all plugin dependencies to the tomcat class loader
[
https://issues.apache.org/jira/browse/MTOMCAT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-122:
-
Summary: add all plugin dependencies to the tomcat class loader (was:
Maven and dependencies for $CATALINA/lib)
add all plugin dependencies to the tomcat class loader
--
Key: MTOMCAT-122
URL: https://issues.apache.org/jira/browse/MTOMCAT-122
Project: Apache Tomcat Maven Plugin
Issue Type: Improvement
Reporter: James Apfel
Assignee: Olivier Lamy
Fix For: 2.0
*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
plugin
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat6-maven-plugin/artifactId
version2.0-SNAPSHOT/version
dependencies
dependency
groupIdspy/groupId
artifactIdspymemcached/artifactId
version2.8.0/version
scoperuntime/scope
/dependency
dependency
groupIdde.javakaffee.msm/groupId
artifactIdmemcached-session-manager-tc6/artifactId
version1.6.1/version
scoperuntime/scope
/dependency
dependency
groupIdde.javakaffee.msm/groupId
artifactIdmsm-kryo-serializer/artifactId
version1.6.0/version
scoperuntime/scope
/dependency
/dependencies
/plugin{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] [Updated] (MTOMCAT-118) tomcat7:run wont accept additionalClasspathDir arguments
[
https://issues.apache.org/jira/browse/MTOMCAT-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-118:
-
Fix Version/s: 2.0
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
plugin
groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
version2.0-SNAPSHOT/version
configuration
!-- http port --
port9090/port
path//path
useTestClasspathfalse/useTestClasspath
contextFilesrc/sandbox/tomcat/sandbox-context.xml/contextFile
additionalClasspathDirs
additionalClasspathDirsrc/test/resources/additionalClasspathDir
/additionalClasspathDirs
/configuration
dependencies
dependency
groupIdmysql/groupId
artifactIdmysql-connector-java/artifactId
version${mysql.mysql-connector-java}/version
/dependency
dependency
groupIdch.qos.logback/groupId
artifactIdlogback-classic/artifactId
version0.9.15/version
/dependency
/dependencies
/plugin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-43) Allow configuration of URI encoding for tomcat run goals
[ https://issues.apache.org/jira/browse/MTOMCAT-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-43: Component/s: tomcat7 tomcat6 Affects Version/s: 1.1 Fix Version/s: 2.0 Summary: Allow configuration of URI encoding for tomcat run goals (was: Allow configuration of URI encoding) Allow configuration of URI encoding for tomcat run goals 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 Assignee: Olivier Lamy 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] [Updated] (MTOMCAT-115) Allow configuration of URI encoding for executable war
[ https://issues.apache.org/jira/browse/MTOMCAT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-115: - Component/s: (was: tomcat6) 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: 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] [Updated] (MTOMCAT-105) creating executable war failed
[ https://issues.apache.org/jira/browse/MTOMCAT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-105: - Fix Version/s: (was: 2.0) moreinfo 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\BasicSetupmvn --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: moreinfo 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.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at
[jira] [Updated] (MTOMCAT-113) Show progress on WAR uploads
[ https://issues.apache.org/jira/browse/MTOMCAT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-113: - Fix Version/s: 2.0 already fixed in trunk :-) . See http://svn.apache.org/viewvc?view=revisionrevision=1212875 Try last SNAPSHOT: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html 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 Assignee: Olivier Lamy Priority: Minor Labels: features Fix For: 2.0 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] [Updated] (MTOMCAT-111) Make extract directory configurable
[ https://issues.apache.org/jira/browse/MTOMCAT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-111: - for sure definitely something I wanted to do :-) 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 Original Estimate: 1h Remaining Estimate: 1h 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] [Updated] (MTOMCAT-108) THe httpsPort flag starts another http thread not an https thread
[ https://issues.apache.org/jira/browse/MTOMCAT-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-108: - Fix Version/s: 2.0 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] [Updated] (MTOMCAT-109) protocolorg.apache.coyote.http11.Http11NioProtocol/protocol not honoured
[ https://issues.apache.org/jira/browse/MTOMCAT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-109: - Affects Version/s: 2.0 Fix Version/s: 2.0 Assignee: Olivier Lamy need a new parameter for that. protocolorg.apache.coyote.http11.Http11NioProtocol/protocol 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 protocol 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] [Updated] (MTOMCAT-102) Add a mojo to build a standalone jar to run a web application
[ https://issues.apache.org/jira/browse/MTOMCAT-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-102: - Component/s: tomcat7 Assignee: Olivier Lamy 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 Components: tomcat7 Reporter: Olivier Lamy Assignee: 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] [Updated] (MTOMCAT-61) maven tomcat:run ignores the useSeperateTomcatClassloaded when using serverXml property
[ https://issues.apache.org/jira/browse/MTOMCAT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-61: Fix Version/s: 2.0 Assignee: Olivier Lamy maven tomcat:run ignores the useSeperateTomcatClassloaded when using serverXml property --- Key: MTOMCAT-61 URL: https://issues.apache.org/jira/browse/MTOMCAT-61 Project: Apache Tomcat Maven Plugin Issue Type: Bug Affects Versions: 1.0 Environment: Mac OS X, JDK 1.6, Maven 2.2.1 Reporter: Lars Vonk Assignee: Olivier Lamy Fix For: 2.0 When configuring the tomcat plugin as follows: configuration useSeparateTomcatClassLoadertrue/useSeparateTomcatClassLoader serverXml/src/test/config/server.xml/serverXml /configuration the useSeparateTomcatClassLoader is ignored. In our case this causes classloading issues. It could be it is not supported but that is not clear from the documentation. If so I would like to know how I can add server.xml stuff in case of tomcat:run (one this is the single sign on Valve). -- 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] [Updated] (MTOMCAT-85) Perfoming tomcat:redeploy is not reflected in log messages
[ https://issues.apache.org/jira/browse/MTOMCAT-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-85: Fix Version/s: 2.0 Assignee: Olivier Lamy Perfoming tomcat:redeploy is not reflected in log messages -- Key: MTOMCAT-85 URL: https://issues.apache.org/jira/browse/MTOMCAT-85 Project: Apache Tomcat Maven Plugin Issue Type: Bug Affects Versions: 1.1 Reporter: Michael Osipov Assignee: Olivier Lamy Fix For: 2.0 Attachments: MTOMCAT-85.patch Log messages still say Deploying ... to Appropriate messages have not been used. -- 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] [Updated] (MTOMCAT-77) Add support for using the test classpath instead of the compile classpath with tomcat:run
[
https://issues.apache.org/jira/browse/MTOMCAT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MTOMCAT-77:
Fix Version/s: 2.0
Assignee: Olivier Lamy
Add support for using the test classpath instead of the compile classpath
with tomcat:run
-
Key: MTOMCAT-77
URL: https://issues.apache.org/jira/browse/MTOMCAT-77
Project: Apache Tomcat Maven Plugin
Issue Type: New Feature
Affects Versions: 1.1
Environment: Maven
Reporter: Oscar Westra van Holthe - Kind
Assignee: Olivier Lamy
Fix For: 2.0
For an _instant developer experience_, we need to be able to do something
like the following:
{code}
svn co https://company.repository.com/project/foo foo
cd foo
mvn install
mvn tomcat:run
{code}
Using the tomcat:run goal in itself works perfectly, but the (in-memory)
database is empty. Using the Jetty plugin, I can choose to use the test
classpath (which tells Hibernate to initialize the database):
{code:xml}
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.1.26/version
configuration
useTestClasspathtrue/useTestClasspath
webAppConfig
jettyEnvXmlFile/src/test/config/jetty-env.xml/jettyEnvXmlFile
/webAppConfig
/configuration
!-- Cut out: dependencies for the database --
/plugin
{code}
I want to do something similar with the Tomcat plugin:
{code:xml}
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtomcat-maven-plugin/artifactId
version1.1/version
configuration
useTestClasspathtrue/useTestClasspath!-- This is the requested
item. --
path//path
contextFilesrc/test/config/tomcat-context.xml/contextFile
/configuration
!-- Cut out: dependencies for the database --
/plugin
{code}
So my request is: add a useTestClasspath configuration setting for tje
class RunMojo that tells it to use
{{MavenProject.getTestClasspathElements()}} instead of
{{MavenProject.getCompileClasspathElements()}} when creating the webapp
loader. On 2011-02-08, this was line 132 in the class
{{org.codehaus.mojo.tomcat.RunMojo}}.
--
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] [Updated] (MTOMCAT-99) Make redeploy goal consistent with deploy goals
[ https://issues.apache.org/jira/browse/MTOMCAT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-99: Fix Version/s: 2.0 Assignee: Olivier Lamy Make redeploy goal consistent with deploy goals --- Key: MTOMCAT-99 URL: https://issues.apache.org/jira/browse/MTOMCAT-99 Project: Apache Tomcat Maven Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: Michael Osipov Assignee: Olivier Lamy Fix For: 2.0 Redeploy is the same as deploy but has the update flag set to true. redeploy does not fork a package phase, deploy does. The behavior is diffrent. It should be: deploy = redeploy deploy-only = redeploy-only -- 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] [Updated] (MTOMCAT-92) Bind tomcat to a self-chosen network interface
[ https://issues.apache.org/jira/browse/MTOMCAT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-92: Fix Version/s: 2.0 Assignee: Olivier Lamy 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 host127.0.0.1/host 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] [Updated] (MTOMCAT-95) Add directories to the embedded tomcat classloader (equivalent to shared.loader property in regular tomcat instance).
[ https://issues.apache.org/jira/browse/MTOMCAT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-95: Fix Version/s: 2.0 Assignee: Olivier Lamy Add directories to the embedded tomcat classloader (equivalent to shared.loader property in regular tomcat instance). - Key: MTOMCAT-95 URL: https://issues.apache.org/jira/browse/MTOMCAT-95 Project: Apache Tomcat Maven Plugin Issue Type: Improvement Affects Versions: 1.1 Reporter: Nick Lloyd Assignee: Olivier Lamy Priority: Minor Fix For: 2.0 Attachments: additionalClasspathDirs.patch For one of my projects I needed to add directories to the classpath of a tomcat instance. I added additional functionality to tomcat-maven-plugin v1.1 to support this by adding configured directories to the Embedded tomcat classloader (only tomcat:run mojo affected). Attached is the patch file of my modifications. -- 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] [Updated] (MTOMCAT-101) Add the ability to deploy to a Tomcat instance on the filesystem rather than via HTTP
[ https://issues.apache.org/jira/browse/MTOMCAT-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-101: - Fix Version/s: 2.0 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 Fix For: 2.0 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] [Updated] (MTOMCAT-100) support war overlay to add war external dependencies in tomcat run
[ https://issues.apache.org/jira/browse/MTOMCAT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-100: - Component/s: tomcat7 tomcat6 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 Components: tomcat6, tomcat7 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] [Updated] (MTOMCAT-100) support war overlay to add war external dependencies in tomcat run
[ https://issues.apache.org/jira/browse/MTOMCAT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MTOMCAT-100: - Description: /WEB-INF/lib/*.jar and /WEB-INF/classes will added to web app classloader when using tomcat*:run to do as war overlays does. (was: if activated /WEB-INF/lib/*.jar and /WEB-INF/classes will added to web app classloader when using tomcat*:run) 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 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
