[jira] [Created] (MTOMCAT-174) tomcatConfigurationFilesDirectory is not implemented
Robin Böhm created MTOMCAT-174: -- Summary: tomcatConfigurationFilesDirectory is not implemented Key: MTOMCAT-174 URL: https://issues.apache.org/jira/browse/MTOMCAT-174 Project: Apache Tomcat Maven Plugin Issue Type: Task Components: tomcat6, tomcat7 Affects Versions: 2.0-beta-1 Reporter: Robin Böhm Assignee: Olivier Lamy (*$^¨%`£) Hey Ya :) the property "tomcatConfigurationFilesDirectory" is not implemented yet. There is just a field declaration without any handling. Ive written a quick patch for my own project that i assign on this issue. Maybe someone can take this as base for the implementation... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-174) tomcatConfigurationFilesDirectory is not implemented
[ https://issues.apache.org/jira/browse/MTOMCAT-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Böhm updated MTOMCAT-174: --- Attachment: patch.diff simple patch for my project. may could help :) > tomcatConfigurationFilesDirectory is not implemented > > > Key: MTOMCAT-174 > URL: https://issues.apache.org/jira/browse/MTOMCAT-174 > Project: Apache Tomcat Maven Plugin > Issue Type: Task > Components: tomcat6, tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Robin Böhm >Assignee: Olivier Lamy (*$^¨%`£) > Attachments: patch.diff > > > Hey Ya :) > the property "tomcatConfigurationFilesDirectory" is not implemented yet. > There is just a field declaration without any handling. > Ive written a quick patch for my own project that i assign on this issue. > Maybe someone can take this as base for the implementation... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-181) Allow to run the webapp under the root context
Sergio Fernández created MTOMCAT-181: Summary: Allow to run the webapp under the root context Key: MTOMCAT-181 URL: https://issues.apache.org/jira/browse/MTOMCAT-181 Project: Apache Tomcat Maven Plugin Issue Type: New Feature Components: tomcat7 Reporter: Sergio Fernández Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor Right now the plugin simply ignores this: org.apache.tomcat.maven tomcat7-maven-plugin 2.0 / and take the artifactId as default context path. Would be possible to run it under the root context? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-181) Allow to run the webapp under the root context
[ https://issues.apache.org/jira/browse/MTOMCAT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478775#comment-13478775 ] Sergio Fernández commented on MTOMCAT-181: -- You can reproduce the issue with any webapp which uses the plugin. This setup is quite common with other plugins, such as jetty: http://stackoverflow.com/questions/8685970/setting-root-context-path-with-maven-jetty-plugin#8880979 In my case, the issue is raised by the LMF webapp: https://code.google.com/p/lmf/source/browse/lmf-webapp/pom.xml?name=mavenized#40 Therefore, we can provide support for testing the implementation of such feature. > Allow to run the webapp under the root context > -- > > Key: MTOMCAT-181 > URL: https://issues.apache.org/jira/browse/MTOMCAT-181 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat7 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: moreinfo > > > Right now the plugin simply ignores this: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0 > > / > > > and take the artifactId as default context path. > Would be possible to run it under the root context? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-181) Allow to run the webapp under the root context
[ https://issues.apache.org/jira/browse/MTOMCAT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478883#comment-13478883 ] Sergio Fernández commented on MTOMCAT-181: -- OK, I see the source of this issue: - the project generated by the artifact includes the path at /project/build/pluginManagement/plugins/plugin/configuration/path - since I had it at /project/build/plugins/plugin/configuration/path But reorganizing my pom as it should be, I got the following error: The plugin 'org.apache.maven.plugins:maven-tomcat7-plugin' does not exist or no valid version could be found Notice the wrong groupId of the plugin, which I'm not sure from where it comes from :-S > Allow to run the webapp under the root context > -- > > Key: MTOMCAT-181 > URL: https://issues.apache.org/jira/browse/MTOMCAT-181 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat7 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: moreinfo > > > Right now the plugin simply ignores this: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0 > > / > > > and take the artifactId as default context path. > Would be possible to run it under the root context? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-181) Allow to run the webapp under the root context
[ https://issues.apache.org/jira/browse/MTOMCAT-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478930#comment-13478930 ] Sergio Fernández commented on MTOMCAT-181: -- True, not a real bug, just a bit confusing how maven manages the external plugin groups. Thanks anyway. > Allow to run the webapp under the root context > -- > > Key: MTOMCAT-181 > URL: https://issues.apache.org/jira/browse/MTOMCAT-181 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat7 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > > Right now the plugin simply ignores this: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0 > > / > > > and take the artifactId as default context path. > Would be possible to run it under the root context? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-173) Direct dependencies are not added to classpath
[ https://issues.apache.org/jira/browse/MTOMCAT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481281#comment-13481281 ] Loïc Guerrin commented on MTOMCAT-173: -- Hello, I have the same issue with tomcat7-maven-plugin:2.0. But it's during an integration test with junit. I have the structure below: / -- project-domain -- project-webapp The module project-domain isn't added to the classpath and the startup of the tomcat fails. In the maven debug log I see too 'skip adding artifact project-domain as it's in reactors'. In DefaultClassLoaderEntriesCalculator#calculateClassPathEntries at line 116, the method isInProjectReferences rejects the project-domain as it's in projectReferences of project-webapp. So is it possible to add a cheap workaround like a configuration parameter 'forceIncludeProjectReferences' in order to add those project references to module classpath? Thanks. > Direct dependencies are not added to classpath > -- > > Key: MTOMCAT-173 > URL: https://issues.apache.org/jira/browse/MTOMCAT-173 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6, tomcat7 >Affects Versions: 2.0 >Reporter: Arne Franken >Assignee: Olivier Lamy (*$^¨%`£) > > in DefaultClassLoaderEntriesCalculator#calculateClassPathEntries, direct > dependencies are not added, the log message says "skip adding artifact " + > artifact.getArtifactId() + " as it's in reactors". > In my case, it's a jar that is configured as a direct dependency. When the > Webapp starts, the Jar is missing from the Classpath and the startup fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-187) Scan resources executing run goal
Sergio Fernández created MTOMCAT-187: Summary: Scan resources executing run goal Key: MTOMCAT-187 URL: https://issues.apache.org/jira/browse/MTOMCAT-187 Project: Apache Tomcat Maven Plugin Issue Type: Question Components: tomcat7 Affects Versions: 2.0-beta-1 Reporter: Sergio Fernández Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor I tried to find this detail at the documentation, but sorry but I didn't. The question is: does the plugin has any way to force the goal tomcat7:run to scan (and updated when are modified) resources? Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergio Fernández updated MTOMCAT-187: - Description: I tried to find this detail at the documentation, but sorry but I didn't. The question is: does the plugin has any way to force the goal tomcat7:run to scan (and updated when are modified) resources? Something equivalent to scanIntervalSeconds in the maven jetty plugin. Thanks in advance. was: I tried to find this detail at the documentation, but sorry but I didn't. The question is: does the plugin has any way to force the goal tomcat7:run to scan (and updated when are modified) resources? Thanks in advance. > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508827#comment-13508827 ] Sergio Fernández commented on MTOMCAT-187: -- Umm, not... I'll try it. What's the semantics of -1 as default value? > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508842#comment-13508842 ] Sergio Fernández commented on MTOMCAT-187: -- Not working for me: org.apache.tomcat.maven tomcat7-maven-plugin 2.0 10 Modified resources are not refreshed at the webapp :-/ > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510338#comment-13510338 ] Sergio Fernández commented on MTOMCAT-187: -- so, bug confirmed? awaiting to have it fix it at 2.1-SNAPSHOT thanks! > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > Fix For: 2.1 > > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-263) tomcat7:exec-war can't create .extract/webapps
[
https://issues.apache.org/jira/browse/MTOMCAT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219736#comment-15219736
]
Sergio Fernández commented on MTOMCAT-263:
--
I'm still getting the same issue with {{2.3-SNAPSHOT}} available in the ASF
snapshot repo...
So two questions:
1. When do you plan to have {{2.3}} out?
2. Is there any pre-release build available?
> tomcat7:exec-war can't create .extract/webapps
> --
>
> Key: MTOMCAT-263
> URL: https://issues.apache.org/jira/browse/MTOMCAT-263
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 2.1, 2.2
>Reporter: jieryn
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 3.0
>
> Attachments: MTOMCAT-263_1.patch
>
>
> bash$ java -jar target/app-1.0-SNAPSHOT-war-exec.jar
> Exception in thread "main" java.lang.Exception: FATAL: impossible to create
> directories:.extract/webapps
> at
> org.apache.tomcat.maven.runner.Tomcat7Runner.extract(Tomcat7Runner.java:586)
> at
> org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:204)
> at
> org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:212)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-263) tomcat7:exec-war can't create .extract/webapps
[ https://issues.apache.org/jira/browse/MTOMCAT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219761#comment-15219761 ] Sergio Fernández commented on MTOMCAT-263: -- Sorry, it actually works, so ignore the first line of my previous comment. The two questions remain valid. > tomcat7:exec-war can't create .extract/webapps > -- > > Key: MTOMCAT-263 > URL: https://issues.apache.org/jira/browse/MTOMCAT-263 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2 >Reporter: jieryn >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 3.0 > > Attachments: MTOMCAT-263_1.patch > > > bash$ java -jar target/app-1.0-SNAPSHOT-war-exec.jar > Exception in thread "main" java.lang.Exception: FATAL: impossible to create > directories:.extract/webapps > at > org.apache.tomcat.maven.runner.Tomcat7Runner.extract(Tomcat7Runner.java:586) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:204) > at > org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:212) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-234) Tomcat8 Maven Plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724855#comment-15724855 ] Björn Raupach commented on MTOMCAT-234: --- Any updates? > Tomcat8 Maven Plugin > > > Key: MTOMCAT-234 > URL: https://issues.apache.org/jira/browse/MTOMCAT-234 > Project: Apache Tomcat Maven Plugin > Issue Type: Dependency upgrade >Affects Versions: 2.0, 2.1, 2.2 > Environment: Maven 3.1, Tomcat8.0RC1, Oracle JDK7u25 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Blocker > Fix For: 3.0 > > > Please provide initial version of Tomcat8 Maven Plugin. > I tried the recommendations in > http://tomcat.10.x6.nabble.com/Tomcat-8-Tomcat-Maven-Plugin-2-2-Tomcat8-Maven-Plugin-td4995858.html#none > but the guideline > http://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html > does not work for Tomcat8 . > The problem is in changed Tomcat 8 API, the maven throws folloving exception: > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:142) > ... 20 more > by: java.lang.NoSuchMethodError: > org.apache.catalina.startup.Tomcat.setDefaultRealm(Lorg/apache/catalina/Realm;)V > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:999) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:514) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more > The method setDefaultRealm is deprecated in Tomcat7 and was removed in > Tomcat8 as described in documentation: > http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html#setDefaultRealm(org.apache.catalina.Realm) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-245) Missing useBodyEncodingForURI parameter on connector
Cédric Dutoit created MTOMCAT-245: - Summary: Missing useBodyEncodingForURI parameter on connector Key: MTOMCAT-245 URL: https://issues.apache.org/jira/browse/MTOMCAT-245 Project: Apache Tomcat Maven Plugin Issue Type: Improvement Components: tomcat7 Affects Versions: 2.2 Reporter: Cédric Dutoit Assignee: Olivier Lamy (*$^¨%`£) Priority: Critical Fix For: 2.2 UseBodyEncodingForURI is unsupported yet (25 oct 2013) in 2.2-SNAPSHOT. Please add it: tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java @Parameter( property = "maven.tomcat.useBodyEncodingForURI", defaultValue = "false" ) private boolean useBodyEncodingForURI; then next to "connector.setURIEncoding( uriEncoding );", add connector.setUseBodyEncodingForURI( useBodyEncodingForURI ); then next to "ajpConnector.setURIEncoding( uriEncoding );", add ajpConnector.setUseBodyEncodingForURI( useBodyEncodingForURI ); -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-256) Adding maxPostSize to the tomcat connector
Matthias Günther created MTOMCAT-256: Summary: Adding maxPostSize to the tomcat connector Key: MTOMCAT-256 URL: https://issues.apache.org/jira/browse/MTOMCAT-256 Project: Apache Tomcat Maven Plugin Issue Type: New Feature Components: tomcat6, tomcat7 Reporter: Matthias Günther Assignee: Olivier Lamy (*$^¨%`£) Attachments: add_param_max_post_size.patch For a project we exceeded the default maxPostSize of the Tomcat's connector and could not submit our form data. To fix this we just added the parameter maxPostSize to the tomcat maven plugin and it run as expected. With the attached patch it will be possible to set the maxPostSize within the tomcat-maven-plugin configuration. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-256) Adding maxPostSize to the tomcat connector
[ https://issues.apache.org/jira/browse/MTOMCAT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Günther updated MTOMCAT-256: - Attachment: add_param_max_post_size.patch > Adding maxPostSize to the tomcat connector > -- > > Key: MTOMCAT-256 > URL: https://issues.apache.org/jira/browse/MTOMCAT-256 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat6, tomcat7 >Reporter: Matthias Günther >Assignee: Olivier Lamy (*$^¨%`£) > Attachments: add_param_max_post_size.patch > > > For a project we exceeded the default maxPostSize of the Tomcat's connector > and could not submit our form data. To fix this we just added the parameter > maxPostSize to the tomcat maven plugin and it run as expected. > With the attached patch it will be possible to set the maxPostSize within the > tomcat-maven-plugin configuration. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-256) Adding maxPostSize to the tomcat connector
[ https://issues.apache.org/jira/browse/MTOMCAT-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Günther updated MTOMCAT-256: - Description: For a project we exceeded the default maxPostSize of the Tomcat's connector and could not submit our form data. To fix this we just added the parameter maxPostSize to the tomcat maven plugin and it run as expected. With the attached patch it will be possible to set the maxPostSize within the tomcat-maven-plugin configuration. I used the git trunk (2.3-SNAPSHOT) for the feature implementation. was: For a project we exceeded the default maxPostSize of the Tomcat's connector and could not submit our form data. To fix this we just added the parameter maxPostSize to the tomcat maven plugin and it run as expected. With the attached patch it will be possible to set the maxPostSize within the tomcat-maven-plugin configuration. > Adding maxPostSize to the tomcat connector > -- > > Key: MTOMCAT-256 > URL: https://issues.apache.org/jira/browse/MTOMCAT-256 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat6, tomcat7 >Reporter: Matthias Günther >Assignee: Olivier Lamy (*$^¨%`£) > Attachments: add_param_max_post_size.patch > > > For a project we exceeded the default maxPostSize of the Tomcat's connector > and could not submit our form data. To fix this we just added the parameter > maxPostSize to the tomcat maven plugin and it run as expected. > With the attached patch it will be possible to set the maxPostSize within the > tomcat-maven-plugin configuration. > I used the git trunk (2.3-SNAPSHOT) for the feature implementation. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-322) Use https upload file will fail
蔡英麟 created MTOMCAT-322: --- Summary: Use https upload file will fail Key: MTOMCAT-322 URL: https://issues.apache.org/jira/browse/MTOMCAT-322 Project: Apache Tomcat Maven Plugin Issue Type: Question Components: commons-lib Environment: apache tomcat 8.5 + java 11 Reporter: 蔡英麟 Assignee: Olivier Lamy Use Http upload file (size 38MB) is sucessfuly But use HTTPS upload file is faild error message: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Stream resetorg.apache.catalina.connector.ClientAbortException: java.io.IOException: Stream reset at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:348) at org.apache.catalina.connector.InputBuffer.checkByteBufferEof(InputBuffer.java:663) at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:370) at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:183) at com.oreilly.servlet.multipart.BufferedServletInputStream.fill(BufferedServletInputStream.java:64) at com.oreilly.servlet.multipart.BufferedServletInputStream.readLine(BufferedServletInputStream.java:108) at com.oreilly.servlet.multipart.LimitedServletInputStream.readLine(LimitedServletInputStream.java:60) at com.oreilly.servlet.multipart.PartInputStream.fill(PartInputStream.java:97) at com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:195) at com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:156) at com.oreilly.servlet.multipart.FilePart.write(FilePart.java:208) at com.oreilly.servlet.multipart.FilePart.writeTo(FilePart.java:167) at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:271) at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:110) at org.apache.jsp.management.upload_005ffw_005fact_jsp._jspService(upload_005ffw_005fact_jsp.java:145) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330) at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:668) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http2.StreamProcessor.service(StreamProcessor.java:350) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.http2.StreamProcessor.process(StreamProcessor.java:69) at org.apache.coyote.http2.StreamRunnable.run(StreamRunnable.java:35) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.base/java.lang.Thread.run(Thread.java:834)Caused by: java.io.IOException: Stream reset at org.apache.coyote.http2.Stream$StreamInputBuffer.doRead(Stream.java:1162) at org.apache.coyote.Request.doRead(Request.java:581) at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:344) ... 41 more -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Updated] (MTOMCAT-238) Parameter staticContextDocbase cant be used
[ https://issues.apache.org/jira/browse/MTOMCAT-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Guillopé updated MTOMCAT-238: - Attachment: tomcat7-maven-plugin-2.2.diff Hi, I've attached the diff file based on Laurent Garcia's fix. Could you please have this patch integrated in the next version? Our team recently switched to using this plugin but we had to manually override the jar as per Laurent's suggestion. It's helpful but not ideal. Thanks > Parameter staticContextDocbase cant be used > --- > > Key: MTOMCAT-238 > URL: https://issues.apache.org/jira/browse/MTOMCAT-238 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6, tomcat7 >Affects Versions: 2.0-beta-1, 2.1 >Reporter: Michal Franc >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: moreinfo > > Attachments: AbstractRunMojo.java, tomcat7-maven-plugin-2.2.diff, > tomcat7-maven-plugin-2.2.jar.zip > > > Attribute staticContextDocbase leads to IllegalArgumentException > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo#createStaticContext > is context created from container and at the and added again to server which > leads to java.lang.IllegalArgumentException: addChild: Child name '/' is not > unique -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-255) Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on tomcat:run but not in tomcat:run-war
[
https://issues.apache.org/jira/browse/MTOMCAT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071851#comment-14071851
]
Manuel Pereira González commented on MTOMCAT-255:
-
Hi, if this can help you, I finally solved this issue modifying method
createContext of AbstractRunMojo.java, just before "return context;", you can
add those lines to solve the problem (Adding an alias to the standard context
for "WEB-INF/classes" pointing to the target directory):
if(context instanceof StandardContext) {
((StandardContext) context).setAddWebinfClassesResources(true);
((StandardContext) context).setAliases(
"/WEB-INF/classes=" + project.getBuild().getOutputDirectory());
}
> Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on
> tomcat:run but not in tomcat:run-war
> --
>
> Key: MTOMCAT-255
> URL: https://issues.apache.org/jira/browse/MTOMCAT-255
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
>Affects Versions: 2.2
> Environment: gilberto.andrade@A37710:~$ mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 05:44:56-0300)
> Maven home: /home/gilberto.andrade/bin/maven
> Java version: 1.7.0_45, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.7.0_45/jre
> Default locale: pt_BR, platform encoding: UTF-8
> OS name: "linux", version: "3.7.10-1.24-desktop", arch: "amd64", family:
> "unix"
>Reporter: Gilberto C Andrade
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: MTOMCAT-255.zip
>
>
> Simple JSF 2.2 project with just one manage bean(PessoaMb) and one xhtml page.
> 1 Run mvn clean tomcat7:run
> 2 hitting http://localhost:8080/MTOMCAT-255/pessoaView.xhtml
> 3 enter some value on field or click the consultar button
> The same steps works when using tomcat7:run-war.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-128) The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml option
[
https://issues.apache.org/jira/browse/MTOMCAT-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073182#comment-14073182
]
Manuel Pereira González commented on MTOMCAT-128:
-
Hello, we are in the same situation, we need to use a web.xml not placed in
WEB-INF/classes, in order to use the maven-filtered one, that is available in
"target" directory not in "src/main/webapp" directory.
I just modified tomcat7-maven-plugin to add a new parameter, just adding those
lines to AbstractRunMojo.java:
On variable definitions:
@Parameter( property = "maven.tomcat.webXmlPath" )
private String webXmlPath;
On startContainer() method, after those lines:
embeddedTomcat.setDefaultRealm( memoryRealm );
Context ctx = createContext( embeddedTomcat );
Add those ones:
ServletContext servletContext = ctx.getServletContext();
if (servletContext != null && webXmlPath != null) {
servletContext.setAttribute("org.apache.catalina.deploy.alt_dd", webXmlPath);
}
With those modifications, you can use the new parameter "webXmlPath" con
configuration of your tomcat7-maven-plugin:
org.apache.tomcat.maven
tomcat7-maven-plugin
2.2
${project.build.directory}/Web127/WEB-INF/web.xml
Regards.
> 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.1
>
> Attachments: myproject.zip
>
>
> 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
>
[jira] [Commented] (MTOMCAT-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566475#comment-13566475 ] Sergio Fernández commented on MTOMCAT-187: -- thanks! when will be available as 2.1-SNAPSHOT? > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > Fix For: 2.1 > > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-187) Scan resources executing run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566482#comment-13566482 ] Sergio Fernández commented on MTOMCAT-187: -- That's true! Knowing it I can even you 2.0. Thanks. > Scan resources executing run goal > - > > Key: MTOMCAT-187 > URL: https://issues.apache.org/jira/browse/MTOMCAT-187 > Project: Apache Tomcat Maven Plugin > Issue Type: Question > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Sergio Fernández >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Labels: maven > Fix For: 2.1 > > > I tried to find this detail at the documentation, but sorry but I didn't. > The question is: does the plugin has any way to force the goal tomcat7:run to > scan (and updated when are modified) resources? Something equivalent to > scanIntervalSeconds in the maven jetty plugin. > Thanks in advance. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-143) contextFile and tomcatUsers defined in pom.xml are not used with target tomcat7:run
[
https://issues.apache.org/jira/browse/MTOMCAT-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259772#comment-13259772
]
Hudson commented on MTOMCAT-143:
Integrated in TomcatMavenPlugin-mvn3.x #140 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/140/])
[MTOMCAT-143] contextFile and tomcatUsers defined in pom.xml are not used
with target tomcat7:run
configuring realm must be done before adding context. (Revision 1329339)
Result = SUCCESS
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1329339
Files :
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> 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 (*$^¨%`£)
> Fix For: 2.0
>
>
> 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] [Commented] (MTOMCAT-147) Add help goal
[ https://issues.apache.org/jira/browse/MTOMCAT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264744#comment-13264744 ] Hudson commented on MTOMCAT-147: Integrated in TomcatMavenPlugin-mvn3.x #144 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/144/]) [MTOMCAT-147] Add help goal. (Revision 1332126) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1332126 Files : * /tomcat/maven-plugin/trunk/pom.xml * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/pom.xml * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/pom.xml > Add help goal > - > > Key: MTOMCAT-147 > URL: https://issues.apache.org/jira/browse/MTOMCAT-147 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6, tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Jeff MAURY >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Trivial > Fix For: 2.0 > > > Add an help goal that is found on numerous Mojo now -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-144) resourcePaths returns null
[ https://issues.apache.org/jira/browse/MTOMCAT-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264930#comment-13264930 ] Hudson commented on MTOMCAT-144: Integrated in TomcatMavenPlugin-mvn3.x #145 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/145/]) [MTOMCAT-144] resourcePaths returns null (Revision 1332183) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1332183 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > 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 (*$^¨%`£) > Fix For: 2.0 > > > 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-149) Error deploying on Tomcat 6
costas created MTOMCAT-149: -- Summary: Error deploying on Tomcat 6 Key: MTOMCAT-149 URL: https://issues.apache.org/jira/browse/MTOMCAT-149 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6 Affects Versions: 2.0-beta-1 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_31 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" Reporter: costas Assignee: Olivier Lamy (*$^¨%`£) Deploying on Tomcat 6 throws the following exception: 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) ... 20 more Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry request with a non-repeatable request entity. The cause lists the reason the original request failed. at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923) ... 27 more Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) at org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:825) at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:98) at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108) at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:122) at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:266) at org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:197) at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:257) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:708) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-149) Error deploying on Tomcat 6
[ https://issues.apache.org/jira/browse/MTOMCAT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266695#comment-13266695 ] costas commented on MTOMCAT-149: Latest snapshot provides this: [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke Tomcat manager at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) 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.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.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) at org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:857) at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.ja > Error deploying on Tomcat 6 > --- > > Key: MTOMCAT-149 > URL: https://issues.apache.org/jira/browse/MTOMCAT-149 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0-beta-1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_31 > 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" >Reporter: costas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Deploying on Tomcat 6 throws the following exception: > 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
[jira] [Reopened] (MTOMCAT-149) Error deploying on Tomcat 6
[
https://issues.apache.org/jira/browse/MTOMCAT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
costas reopened MTOMCAT-149:
DEBUG] Configuring mojo
'org.apache.tomcat.maven:tomcat6-maven-plugin:2.0-SNAPSHOT:deploy' -->
[DEBUG] (f) charset = UTF-8
[DEBUG] (f) contextFile =
/Users/m/workspace/app/target/integration-api-1.0-SNAPSHOT/META-INF/context.xml
[DEBUG] (f) ignorePackaging = false
[DEBUG] (f) mode = war
[DEBUG] (f) packaging = war
[DEBUG] (f) password = tomcat
[DEBUG] (f) path = /integration-api
[DEBUG] (f) update = true
[DEBUG] (f) url = http://localhost:8080/manager
[DEBUG] (f) username = tomcat
[DEBUG] (f) version = 2.0-SNAPSHOT
[DEBUG] (f) warFile =
/Users/m/workspace/app/target/integration-api-1.0-SNAPSHOT.war
[DEBUG] -- end configuration --
[INFO] [tomcat6:deploy {execution: default-cli}]
[INFO] Deploying war to http://localhost:8080/integration-api
[DEBUG] No server specified for authentication - using defaults
Uploading:
http://localhost:8080/manager/deploy?path=%2Fintegration-api&update=true
12/21672 KB
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request:
Broken pipe
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: Retrying request
Uploading:
http://localhost:8080/manager/deploy?path=%2Fintegration-api&update=true
12/21672 KB
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request:
Broken pipe
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: Retrying request
Uploading:
http://localhost:8080/manager/deploy?path=%2Fintegration-api&update=true
12/21672 KB
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request:
Broken pipe
May 2, 2012 6:41:25 PM org.apache.http.impl.client.DefaultRequestDirector
tryExecute
INFO: Retrying request
Uploading:
http://localhost:8080/manager/deploy?path=%2Fintegration-api&update=true
> Error deploying on Tomcat 6
> ---
>
> Key: MTOMCAT-149
> URL: https://issues.apache.org/jira/browse/MTOMCAT-149
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
>Affects Versions: 2.0-beta-1
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_31
> 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"
>Reporter: costas
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> Deploying on Tomcat 6 throws the following exception:
> 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)
> ... 20 more
> Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry
> request with a non-repeatable request entity. The cause lists the reason the
> original request failed.
> at
> org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
> at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515)
> at
> org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923)
> ... 27 more
> Caused by: java.net.SocketException: Broken pipe
> at java.net.SocketOutputStream.socketWrite0(Native Method)
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> at java.net.SocketOutputStream.write(SocketOutputSt
[jira] [Commented] (MTOMCAT-149) Error deploying on Tomcat 6
[ https://issues.apache.org/jira/browse/MTOMCAT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266865#comment-13266865 ] costas commented on MTOMCAT-149: Nothing in the logs. A broken pipe exception probably means that the connection somehow ends before writing the file begins but I'm not sure how this happens. Would have expected something in the logs too. Having said that, using the tomcat-manager (web page) to deploy the same war file works correctly. > Error deploying on Tomcat 6 > --- > > Key: MTOMCAT-149 > URL: https://issues.apache.org/jira/browse/MTOMCAT-149 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0-beta-1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_31 > 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" >Reporter: costas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Deploying on Tomcat 6 throws the following exception: > 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) > ... 20 more > Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry > request with a non-repeatable request entity. The cause lists the reason the > original request failed. > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923) > ... 27 more > Caused by: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at > org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) > at > org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) > at > org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:825) > at > org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:98) > at > org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108) > at > org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:122) > at > org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:266) > at > org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:197) > at > org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:257) > at > org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:708) -- 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] [Closed] (MTOMCAT-149) Error deploying on Tomcat 6
[ https://issues.apache.org/jira/browse/MTOMCAT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] costas closed MTOMCAT-149. -- Resolution: Fixed > Error deploying on Tomcat 6 > --- > > Key: MTOMCAT-149 > URL: https://issues.apache.org/jira/browse/MTOMCAT-149 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0-beta-1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_31 > 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" >Reporter: costas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Deploying on Tomcat 6 throws the following exception: > 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) > ... 20 more > Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry > request with a non-repeatable request entity. The cause lists the reason the > original request failed. > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923) > ... 27 more > Caused by: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at > org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) > at > org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) > at > org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:825) > at > org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:98) > at > org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108) > at > org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:122) > at > org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:266) > at > org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:197) > at > org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:257) > at > org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:708) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-149) Error deploying on Tomcat 6
[ https://issues.apache.org/jira/browse/MTOMCAT-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267312#comment-13267312 ] costas commented on MTOMCAT-149: Consider the issue closed, somehow I could not receive yesterday the latest snapshot. Today I was able to receive 2.0-20120430.142050-73 and this one worked better. Thanks for the support. > Error deploying on Tomcat 6 > --- > > Key: MTOMCAT-149 > URL: https://issues.apache.org/jira/browse/MTOMCAT-149 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0-beta-1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_31 > 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" >Reporter: costas >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > Deploying on Tomcat 6 throws the following exception: > 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) > ... 20 more > Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry > request with a non-repeatable request entity. The cause lists the reason the > original request failed. > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682) > at > org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:515) > at > org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:923) > ... 27 more > Caused by: java.net.SocketException: Broken pipe > at java.net.SocketOutputStream.socketWrite0(Native Method) > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > at java.net.SocketOutputStream.write(SocketOutputStream.java:136) > at > org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:163) > at > org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:119) > at > org.apache.tomcat.maven.common.deployer.TomcatManager$RequestEntityImplementation.writeTo(TomcatManager.java:825) > at > org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:98) > at > org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108) > at > org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:122) > at > org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:266) > at > org.apache.http.impl.conn.ManagedClientConnectionImpl.sendRequestEntity(ManagedClientConnectionImpl.java:197) > at > org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:257) > at > org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) > at > org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:708) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-150) expose ports used with tomcat7:run as sys props
[ https://issues.apache.org/jira/browse/MTOMCAT-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268344#comment-13268344 ] Hudson commented on MTOMCAT-150: Integrated in TomcatMavenPlugin-mvn3.x #147 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/147/]) [MTOMCAT-150] expose ports used with tomcat7:run as sys props: feature to dump ports in a property file to be able to use later with a forked surefire execution (Revision 1333929) [MTOMCAT-150] expose ports used with tomcat7:run as sys props: add javadoc (Revision 1333928) [MTOMCAT-150] expose ports used with tomcat7:run as sys props (Revision 1333926) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1333929 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java olamy : http://svn.apache.org/viewvc/?view=rev&rev=1333928 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java olamy : http://svn.apache.org/viewvc/?view=rev&rev=1333926 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java > expose ports used with tomcat7:run as sys props > --- > > Key: MTOMCAT-150 > URL: https://issues.apache.org/jira/browse/MTOMCAT-150 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > For folks using port 0 (auto allocation), they need to know which port is > really use. > Do exposing sys props > * tomcat.maven.http.port > * tomcat.maven.https.port > * tomcat.maven.ajp.port -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-151) Empty password prevents preemptive authentication headers from being sent
[
https://issues.apache.org/jira/browse/MTOMCAT-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273601#comment-13273601
]
Hudson commented on MTOMCAT-151:
Integrated in TomcatMavenPlugin-mvn3.x #149 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/149/])
[MTOMCAT-151] Empty password prevents preemptive authentication headers
from being sent (Revision 1337356)
Result = SUCCESS
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1337356
Files :
*
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java
> Empty password prevents preemptive authentication headers from being sent
> -
>
> Key: MTOMCAT-151
> URL: https://issues.apache.org/jira/browse/MTOMCAT-151
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: commons-lib
>Affects Versions: 2.0-beta-1
>Reporter: Peter lynch
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> Default username for auth is *admin*, default password is "" ( empty string ).
> Problem is when password is empty string, TomcatManager.java does not send
> auth headers, so deploy and deploy-only goals fail with 401 after appearing
> to upload the war successfully.
> Seems to have been introduced by
> [this|http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java?r1=1178619&r2=1212685&pathrev=1301824&diff_format=h].
> The line in question is 171 of which decides what to do about auth.
> {noformat}
> if ( StringUtils.isNotEmpty( username ) && StringUtils.isNotEmpty( password )
> )
> {noformat}
> Workaround: set a non-empty password for the user accessing /manager/text.
> Expected: blank password to trigger preemptive auth headers.
> {noformat:title=Proof that TomcatManager didn't send auth headers
> pre-emptively for empty password(default)}
> > mvn -Pstaging tomcat7:deploy-only
> > -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
> > -Dorg.apache.commons.logging.simplelog.showdatetime=true
> > -Dorg.apache.commons.logging.simplelog.log.org.apache.http=DEBUG
> > -Dorg.apache.commons.logging.simplelog.log.org.apache.http.wire=INFO
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building My WAR 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- tomcat7-maven-plugin:2.0-SNAPSHOT:deploy-only (default-cli) @
> my-webapp ---
> [INFO] Deploying war to http://172.16.2.16:18080/my-webapp
> 2012/05/11 11:16:21:623 NDT [DEBUG] PoolingClientConnectionManager -
> Connection request: [route: {}->http://172.16.2.16:18080][total kept alive:
> 0; route allocated: 0 of 2; total allocated: 0 of 5]
> 2012/05/11 11:16:21:650 NDT [DEBUG] PoolingClientConnectionManager -
> Connection leased: [id: 0][route: {}->http://172.16.2.16:18080][total kept
> alive: 0; route allocated: 1 of 2; total allocated: 1 of 5]
> 2012/05/11 11:16:21:655 NDT [DEBUG] DefaultClientConnectionOperator -
> Connecting to 172.16.2.16:18080
> 2012/05/11 11:16:21:761 NDT [DEBUG] RequestAddCookies - CookieSpec selected:
> best-match
> 2012/05/11 11:16:21:775 NDT [DEBUG] RequestAuthCache - Auth cache not set in
> the context
> 2012/05/11 11:16:21:776 NDT [DEBUG] RequestTargetAuthentication - Target auth
> state: UNCHALLENGED
> 2012/05/11 11:16:21:777 NDT [DEBUG] RequestProxyAuthentication - Proxy auth
> state: UNCHALLENGED
> 2012/05/11 11:16:21:777 NDT [DEBUG] DefaultHttpClient - Attempt 1 to execute
> request
> 2012/05/11 11:16:21:777 NDT [DEBUG] DefaultClientConnection - Sending
> request: PUT /manager/text/deploy?path=%2Fmy-webapp&update=true HTTP/1.1
> 2012/05/11 11:16:21:779 NDT [DEBUG] headers - >> PUT
> /manager/text/deploy?path=%2Fmy-webapp&update=true HTTP/1.1
> 2012/05/11 11:16:21:780 NDT [DEBUG] headers - >> User-Agent: Apache Tomcat
> Maven Plugin/2.0-SNAPSHOT
> 2012/05/11 11:16:21:780 NDT [DEBUG] headers - >> Content-Length: 13269693
> 2012/05/11 11:16:21:780 NDT [DEBUG] headers - >> Host: 172.16.2.16:18080
> 2012/05/11 11:16:21:780 NDT [DEBUG] headers - >> Connection: Keep-Alive
> Uploading:
> http://172.16.2.16:18080/manager/text/deploy
[jira] [Commented] (MTOMCAT-153) align all Maven dependency versions to 2.0.11
[ https://issues.apache.org/jira/browse/MTOMCAT-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280017#comment-13280017 ] Hudson commented on MTOMCAT-153: Integrated in TomcatMavenPlugin-mvn3.x #150 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/150/]) [MTOMCAT-153] align all Maven dependency versions to 2.0.11 Submitted by Peter lynch. (Revision 1340916) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1340916 Files : * /tomcat/maven-plugin/trunk/pom.xml > align all Maven dependency versions to 2.0.11 > - > > Key: MTOMCAT-153 > URL: https://issues.apache.org/jira/browse/MTOMCAT-153 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: align-maven-versions.patch > > > There are several different, old versions of Maven artifact dependencies in > use. > Attached patch align's all of these to 2.0.11 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-154) support exec-war war run dependencies with classifiers
[ https://issues.apache.org/jira/browse/MTOMCAT-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280018#comment-13280018 ] Hudson commented on MTOMCAT-154: Integrated in TomcatMavenPlugin-mvn3.x #150 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/150/]) [MTOMCAT-154] support exec-war war run dependencies with classifiers Submitted by Peter Lynch. (Revision 1340918) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1340918 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java > support exec-war war run dependencies with classifiers > -- > > Key: MTOMCAT-154 > URL: https://issues.apache.org/jira/browse/MTOMCAT-154 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat7 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: support-warRunDependency-classifier.patch > > > Specifying war run dependency with a classifier is not resolved. > Current code does not specify the classifier when resolving the war run > dependency artifact. Attached patch supports resolving wars with classifiers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-156) exec-war should allow creation of exec-war in projects with any packaging type
[ https://issues.apache.org/jira/browse/MTOMCAT-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280040#comment-13280040 ] Hudson commented on MTOMCAT-156: Integrated in TomcatMavenPlugin-mvn3.x #151 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/151/]) [MTOMCAT-156] exec-war should allow creation of exec-war in projects with any packaging type Submitted by Peter Lynch. (Revision 1340932) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1340932 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java > exec-war should allow creation of exec-war in projects with any packaging type > -- > > Key: MTOMCAT-156 > URL: https://issues.apache.org/jira/browse/MTOMCAT-156 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: exec-war-any-packaging.patch > > > Currently exec-wars in tomcat7 can only be created in projects with packaging > 'pom' or 'war'. > There are scenarios where one could want to use another packaging type and > still create an exec-war. This restriction should be removed. > Attached patch removes this restriction. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-155) allow exec-war war run dependencies that are generated in current mvn execution, but not yet installed to maven repo
[ https://issues.apache.org/jira/browse/MTOMCAT-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284495#comment-13284495 ] Hudson commented on MTOMCAT-155: Integrated in TomcatMavenPlugin-mvn3.x #156 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/156/]) [MTOMCAT-155] allow exec-war war run dependencies that are generated in current mvn execution, but not yet installed to maven repo Submitted by Peter Lynch. (Revision 1343301) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1343301 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java > allow exec-war war run dependencies that are generated in current mvn > execution, but not yet installed to maven repo > > > Key: MTOMCAT-155 > URL: https://issues.apache.org/jira/browse/MTOMCAT-155 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Peter lynch >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: warRunDependency-in-current-execution.patch > > > If a war run dependency ( used in exec-war) was generated as part of current > mvn execution maven module as executing tomcat plugin, then artifact file > will be in target dir and not yet installed into maven repo yet ( since > install phase has not been run) - so copy from ./target to > ./target/(pluginWorkDirectory) to allow modifying war run dependency to avoid > potential attempt of current code to overrite existing target dir exec-war. > See attached patch file fo fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-160) "Skipping non-war project" should not happen if using
[
https://issues.apache.org/jira/browse/MTOMCAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294640#comment-13294640
]
Hudson commented on MTOMCAT-160:
Integrated in TomcatMavenPlugin-mvn3.x #159 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/159/])
[MTOMCAT-160] "Skipping non-war project" should not happen if using
(Revision 1349997)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1349997
Files :
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> "Skipping non-war project" should not happen if using
>
> -
>
> Key: MTOMCAT-160
> URL: https://issues.apache.org/jira/browse/MTOMCAT-160
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1, 2.0-beta-1
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> For build pipelines,
> true is often used in
> projects which contain just the acceptance tests.
> If the project packaging is set as JAR, we get:
> [INFO] [tomcat:run {execution: start-tomcat}]
> [INFO] Skipping non-war project
> I can see reasons why the skip logic is there, but this should not happen
> when addContextWarDependencies (or any cleaner successor) is enabled.
> Any chance of this getting tweaked for beta2/rc1 ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395947#comment-13395947 ] Hudson commented on MTOMCAT-162: Integrated in TomcatMavenPlugin-mvn3.x #161 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/161/]) [MTOMCAT-162] SaxException when deploying multiple WARs Submitted by Neale Upstone. (Revision 1351375) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351375 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Attachments: SaxExceptionFix.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395946#comment-13395946
]
Hudson commented on MTOMCAT-60:
---
Integrated in TomcatMavenPlugin-mvn3.x #161 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/161/])
[MTOMCAT-60] Multiple-War-Deployment in configuration section. (Revision
1351368)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351368
Files :
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Priority: Minor
> Attachments: maven-tomcat-plugin.patch.txt, patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plus you can configure an contextPath different from the artifactId.
> This solution was inspired by the 'maven-dependency-plugin' and uses some
> code-snippets from it.
> Jörg Bellmann
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-160) "Skipping non-war project" should not happen if using
[
https://issues.apache.org/jira/browse/MTOMCAT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395987#comment-13395987
]
Hudson commented on MTOMCAT-160:
Integrated in TomcatMavenPlugin-mvn3.x #162 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/162/])
[MTOMCAT-160] "Skipping non-war project" should not happen if using
fix logic. (Revision 1351394)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351394
Files :
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> "Skipping non-war project" should not happen if using
>
> -
>
> Key: MTOMCAT-160
> URL: https://issues.apache.org/jira/browse/MTOMCAT-160
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
>Affects Versions: 1.1, 2.0-beta-1
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.0
>
>
> For build pipelines,
> true is often used in
> projects which contain just the acceptance tests.
> If the project packaging is set as JAR, we get:
> [INFO] [tomcat:run {execution: start-tomcat}]
> [INFO] Skipping non-war project
> I can see reasons why the skip logic is there, but this should not happen
> when addContextWarDependencies (or any cleaner successor) is enabled.
> Any chance of this getting tweaked for beta2/rc1 ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-162) SaxException when deploying multiple WARs
[ https://issues.apache.org/jira/browse/MTOMCAT-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396781#comment-13396781 ] Hudson commented on MTOMCAT-162: Integrated in TomcatMavenPlugin-mvn3.x #165 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/165/]) [MTOMCAT-162] for tomcat7 Submitted by Neale Upstone. (Revision 1351716) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351716 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java > SaxException when deploying multiple WARs > - > > Key: MTOMCAT-162 > URL: https://issues.apache.org/jira/browse/MTOMCAT-162 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-1 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Fix For: 2.0 > > Attachments: SaxExceptionFix.patch, > tomcat7-maven-plugin-MTOMCAT-162.patch > > > When deploying multiple WARs, a file is created in /tmp by the plugin, but is > empty when tomcat starts, thus causing a parsing exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-60) Multiple-War-Deployment in configuration section.
[
https://issues.apache.org/jira/browse/MTOMCAT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396869#comment-13396869
]
Hudson commented on MTOMCAT-60:
---
Integrated in TomcatMavenPlugin-mvn3.x #166 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/166/])
[MTOMCAT-60] Multiple-War-Deployment in configuration section.
Patch for tomcat7
Submitted by Neale Upstone. (Revision 1351742)
[MTOMCAT-60] Multiple-War-Deployment in configuration section.
extract beans to reuse those with tomcat7 plugin.
Submitted by Neale Upstone. (Revision 1351741)
Result = FAILURE
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351742
Files :
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/Webapp.java
olamy : http://svn.apache.org/viewvc/?view=rev&rev=1351741
Files :
*
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/config
*
/tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/config/AbstractWebapp.java
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/Webapp.java
> Multiple-War-Deployment in configuration section.
> -
>
> Key: MTOMCAT-60
> URL: https://issues.apache.org/jira/browse/MTOMCAT-60
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
>Reporter: Joerg Bellmann
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Fix For: 2.0
>
> Attachments: additionalwebapps-tomcat7-unproven.patch,
> extract-AbstractWebapp.patch, maven-tomcat-plugin.patch.txt,
> patch-for-tomcat6.patch
>
>
> When a user want to deploy multiple webapps with the plugin it uses all
> project-war-dependencies with scope 'tomcat'. Maven 3 shows the following
> message at project-processing:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for de.jbellmann.failsafe:de.jbellmann.failsafe.web:war:0.0.1-SNAPSHOT
> [WARNING] 'dependencies.dependency.scope' for
> org.springframework.samples:mvc-showcase:war must be one of [provided,
> compile, runtime, test, system] but is 'tomcat'. @
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> {code}
> Configuring the additional webapps in the configuration section like this for
> example :
> {code}
>
> org.codehaus.mojo
> tomcat-maven-plugin
> 1.1-SNAPSHOT
>
>
>
> start-tomcat-integration-tests
>
> run
>
>
> pre-integration-test
>
> true
>
> true
>
>
>
>
> org.springframework.samples
>
> mvc-showcase
>
> 1.0.0-BUILD-SNAPSHOT
>
> /mvc-showcase2
>
>
>
>
>
>
>
>
> {code}
> avoids the warnings and makes maven 3 happy.
> As a plu
[jira] [Commented] (MTOMCAT-164) Add french translation
[ https://issues.apache.org/jira/browse/MTOMCAT-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398433#comment-13398433 ] Hudson commented on MTOMCAT-164: Integrated in TomcatMavenPlugin-mvn3.x #169 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/169/]) [MTOMCAT-164] Add french translation. Submitted by Tony Chemit. (Revision 1352530) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1352530 Files : * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/resources/org/apache/tomcat/maven/common/messages/messages_en.properties * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/resources/org/apache/tomcat/maven/common/messages/messages_fr.properties > Add french translation > -- > > Key: MTOMCAT-164 > URL: https://issues.apache.org/jira/browse/MTOMCAT-164 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: commons-lib >Affects Versions: 2.0-beta-1 >Reporter: Tony Chemit >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: MTOMCAT-164-2.diff, MTOMCAT-164.diff > > Original Estimate: 1h > Remaining Estimate: 1h > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-171) Multiple executions (i.e. sep tomcats clash due to identical JMX naming)
[ https://issues.apache.org/jira/browse/MTOMCAT-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425118#comment-13425118 ] Hudson commented on MTOMCAT-171: Integrated in TomcatMavenPlugin-mvn3.x #184 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/184/]) [MTOMCAT-171] Multiple executions (i.e. sep tomcats clash due to identical JMX naming) Submitted by Neale Upstone. (Revision 1367193) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367193 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java > Multiple executions (i.e. sep tomcats clash due to identical JMX naming) > > > Key: MTOMCAT-171 > URL: https://issues.apache.org/jira/browse/MTOMCAT-171 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: mtomcat-171.patch > > > If two executions are configured, for example to create two tomcat instances > running on separate ports, these do not behave independently, as they get > identified to JMX using the same names. > Some disambiguation is required, for which the httpPort might be enough (this > works for me for tomcat6) > // create engine > Engine engine = container.createEngine(); > -engine.setName( "localEngine" ); > +engine.setName( "localEngine-" + port); > engine.addChild( host ); > engine.setDefaultHost( host.getName() ); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-169) Unable to Deploy WAR Defined via "webapps" Declaration
[ https://issues.apache.org/jira/browse/MTOMCAT-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425584#comment-13425584 ] Hudson commented on MTOMCAT-169: Integrated in TomcatMavenPlugin-mvn3.x #185 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/185/]) [MTOMCAT-169] Unable to Deploy WAR Defined via "webapps" Declaration Submitted by Josh Harness. Patch modified to preserve backward comp. (Revision 1367432) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367432 Files : * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/config/AbstractWebapp.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Unable to Deploy WAR Defined via "webapps" Declaration > -- > > Key: MTOMCAT-169 > URL: https://issues.apache.org/jira/browse/MTOMCAT-169 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 > Environment: MAC OSX >Reporter: Josh Harness >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.0 > > Attachments: MTOMCAT-169.patch > > > Web app does not deploy via embedded tomcat (tomat7:run) when I define the > following in my plugin config: > > > com.company > mywebapp > 1.0 > war > > > I only see the following and am unable to use the web application: > [INFO] Deploy warfile: > /Users/joshar1/.m2/repository/com/company/mywebapp//1.0/mywebapp-1.0.war to > contextPath: /mywebapp > I have a patch I'll attach to this ticket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-170) Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration
[ https://issues.apache.org/jira/browse/MTOMCAT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425585#comment-13425585 ] Hudson commented on MTOMCAT-170: Integrated in TomcatMavenPlugin-mvn3.x #185 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/185/]) [MTOMCAT-170] Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration Submitted by Josh Harness. (Revision 1367433) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367433 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Unable to Specify Additional Classpath for WAR Defined via "webapps" > Declaration > > > Key: MTOMCAT-170 > URL: https://issues.apache.org/jira/browse/MTOMCAT-170 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Josh Harness >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.0 > > Attachments: MTOMCAT-170.patch > > > I need the ability for web application defined in the "webapps" portion of > the plugin configuration to have the ability to use the classpath of the main > plugin configuration. A reasonable approach might be to allow the webapp to > inherit the additional classpath of the main web application config. > I'll apply a patch shortly for feedback/review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-172) configuring aliases with tomcat7:run
[ https://issues.apache.org/jira/browse/MTOMCAT-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425608#comment-13425608 ] Hudson commented on MTOMCAT-172: Integrated in TomcatMavenPlugin-mvn3.x #186 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/186/]) [MTOMCAT-172] configuring aliases with tomcat7:run (Revision 1367441) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367441 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > configuring aliases with tomcat7:run > > > Key: MTOMCAT-172 > URL: https://issues.apache.org/jira/browse/MTOMCAT-172 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > > adding configuration like > > foo.com > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-157) use new Maven Plugins annotations
[ https://issues.apache.org/jira/browse/MTOMCAT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425909#comment-13425909 ] Hudson commented on MTOMCAT-157: Integrated in TomcatMavenPlugin-mvn3.x #187 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/187/]) [MTOMCAT-157] use new Maven Plugins annotations. done for tomcat7 mojos. (Revision 1367641) [MTOMCAT-157] use new Maven Plugins annotations. done for tomcat6 mojos. (Revision 1367640) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367641 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/AbstractCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/AbstractTomcat7Mojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/AbstractWarCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/AbstractDeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/AbstractDeployWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ShutdownMojo.java olamy : http://svn.apache.org/viewvc/?view=rev&rev=1367640 Files : * /tomcat/maven-plugin/trunk/pom.xml * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/pom.xml * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractDeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractDeployWarMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractI18NTomcat6Mojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractWarCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ExplodedMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/InplaceMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ListMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ReloadMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ResourcesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RolesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.jav
[jira] [Commented] (MTOMCAT-124) tomcat-maven-archetype unused generation parameters
[ https://issues.apache.org/jira/browse/MTOMCAT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428856#comment-13428856 ] Hudson commented on MTOMCAT-124: Integrated in TomcatMavenPlugin-mvn3.x #192 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/192/]) [MTOMCAT-124] tomcat-maven-archetype unused generation parameters Submitted by Patrick Garcia. (Revision 1369603) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1369603 Files : * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/java/api * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/java/api/impl * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/java/api/impl/DefaultHelloService.java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/resources * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/resources/META-INF * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/main/resources/META-INF/spring-context.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/test * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/test/java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/test/java/api * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/test/java/api/impl * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api-impl/src/test/java/api/impl/TestDefaultHelloService.java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/java/api * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-api/src/main/java/api/HelloService.java * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-exec * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-exec/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/src * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/src/test * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/src/test/context.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-r
[jira] [Commented] (MTOMCAT-174) tomcatConfigurationFilesDirectory is not implemented
[ https://issues.apache.org/jira/browse/MTOMCAT-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450108#comment-13450108 ] Hudson commented on MTOMCAT-174: Integrated in TomcatMavenPlugin-mvn3.x #201 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/201/]) [MTOMCAT-174] tomcatConfigurationFilesDirectory is not implemented Submitted by Robin Böhm. (Revision 1381781) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1381781 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java > tomcatConfigurationFilesDirectory is not implemented > > > Key: MTOMCAT-174 > URL: https://issues.apache.org/jira/browse/MTOMCAT-174 > Project: Apache Tomcat Maven Plugin > Issue Type: Task > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Robin Böhm >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.0 > > Attachments: patch.diff > > > Hey Ya :) > the property "tomcatConfigurationFilesDirectory" is not implemented yet. > There is just a field declaration without any handling. > Ive written a quick patch for my own project that i assign on this issue. > Maybe someone can take this as base for the implementation... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-175) warDirectory property has wrong standard value in release version 2.0
[ https://issues.apache.org/jira/browse/MTOMCAT-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457052#comment-13457052 ] Hudson commented on MTOMCAT-175: Integrated in TomcatMavenPlugin-mvn3.x #204 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/204/]) [MTOMCAT-175] warDirectory property has wrong standard value in release version 2.0. (Revision 1386612) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1386612 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunWarMojo.java > warDirectory property has wrong standard value in release version 2.0 > - > > Key: MTOMCAT-175 > URL: https://issues.apache.org/jira/browse/MTOMCAT-175 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0 >Reporter: Florian Maertl >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Labels: build, maven > Fix For: 2.1 > > Attachments: Re warDirectory property wrong evaluated in release > version 2.0 .txt > > > The standard value for the maven property "warDirectory" has the wrong value. > To be more precisier, the closing "}" is missing. > This causes an exception at the start of the embedded Tomcat version. > Error is here: > http://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunWarMojo.java > See also attached mail -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators 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-178) additionalClasspathDirs doesn't seem to be used
Craig created MTOMCAT-178:
-
Summary: additionalClasspathDirs doesn't seem to be used
Key: MTOMCAT-178
URL: https://issues.apache.org/jira/browse/MTOMCAT-178
Project: Apache Tomcat Maven Plugin
Issue Type: Bug
Components: tomcat7
Affects Versions: 2.0
Environment: Maven 3.0.3 / Linux / OpenJDK 7
Reporter: Craig
Assignee: Olivier Lamy (*$^¨%`£)
Using the plugin like this:
org.apache.tomcat.maven
tomcat7-maven-plugin
2.0
${project.build.directory}/../../../mits-common-parent/common-ui/src/main/resource$
${project.build.directory}/../src/main/webapp
I run Tomcat like this:
mvn tomcat7:run
The application starts and runs fine. But, when the classloader loads a
resource that is in one of the additionalClasspathDir entries, it loads it from
the .war, not from the additionalClasspathDir location. Nothing I do seems to
make Tomcat use the additionalClasspathDir entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-179) Null pointer dereference in RunMojo
[ https://issues.apache.org/jira/browse/MTOMCAT-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477044#comment-13477044 ] Hudson commented on MTOMCAT-179: Integrated in TomcatMavenPlugin-mvn3.x #208 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/208/]) [MTOMCAT-179] Null pointer dereference in RunMojo (Revision 1398816) [MTOMCAT-179] Null pointer dereference in RunMojo (Revision 1398815) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1398816 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java olamy : http://svn.apache.org/viewvc/?view=rev&rev=1398815 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java > Null pointer dereference in RunMojo > --- > > Key: MTOMCAT-179 > URL: https://issues.apache.org/jira/browse/MTOMCAT-179 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.1 > > > Line 195 references fw, which is null: > fw.write( sb.toString() ); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-180) Allow hostName and alias to be configured for tomcat6:run etc
[ https://issues.apache.org/jira/browse/MTOMCAT-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477122#comment-13477122 ] Hudson commented on MTOMCAT-180: Integrated in TomcatMavenPlugin-mvn3.x #209 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/209/]) [MTOMCAT-180] Allow hostName and alias to be configured for tomcat6:run . Submitted by Neale Upstone. (Revision 1398856) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1398856 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java > Allow hostName and alias to be configured for tomcat6:run etc > - > > Key: MTOMCAT-180 > URL: https://issues.apache.org/jira/browse/MTOMCAT-180 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0 >Reporter: Neale Upstone >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.1 > > Attachments: 0001-Add-hostName-and-aliases-support.patch > > > Support for the following in Tomcat6 as is done in Tomcat 7 > bar > > foo.com > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-185) change phase for tomcat6/7:run to process-classes
[ https://issues.apache.org/jira/browse/MTOMCAT-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497111#comment-13497111 ] Hudson commented on MTOMCAT-185: Integrated in TomcatMavenPlugin-mvn3.x #219 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/219/]) [MTOMCAT-185] change phase for tomcat6/7:run to process-classes (Revision 1409194) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1409194 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java > change phase for tomcat6/7:run to process-classes > - > > Key: MTOMCAT-185 > URL: https://issues.apache.org/jira/browse/MTOMCAT-185 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Jiri Peinlich >Assignee: Olivier Lamy (*$^¨%`£) > Labels: maven, newbie > Fix For: 2.1 > > > Hello, > I do not know enough about maven+tomcat and related technologies to know if > the following is bug, or if I just missed some setting somewhere. > We have in our project dependencies, that inject some byte-code into compiled > classes in the process-classes maven phase. I was trying to use maven > tomcat7 plugin in version 2.0 to see how is our application working. When > executing mvn tomcat7:run i run into problems because the maven phase > process-classes was not executed before deploying on tomcat. > After some research we found that there is plugin.xml file in the tomcat7 > plugin jar that maven downloads > (org.apache.tomcat.maven.tomcat7-maven-plugin) (META_INF/maven/plugin.xml). > In this file i found mojo with run and in this mojo there i > found compile. I think that the execution phase > should be set to process-classes phase and not compile phase. > My problems disappeared When I manually edited the xml and tried the mvn > tomcat7:run afterwards. This makes me think that the phase is wrongly set in > the jar. > I checked the sources and to me it seams that the phase should be set here: > http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java?view=markup > The execution phase is set there to be compile (curretnly line 60) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-188) Allow for the creation of a war that is both executable and deployable
[ https://issues.apache.org/jira/browse/MTOMCAT-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512123#comment-13512123 ] Hudson commented on MTOMCAT-188: Integrated in TomcatMavenPlugin-mvn3.x #222 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/222/]) [MTOMCAT-188] Allow for the creation of a war that is both executable and deployable Submitted by Mitch Kyle Patch applied with reformating code (Revision 1418074) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1418074 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractStandaloneWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-war-runner/src/main/java/org/apache/tomcat/maven/runner/Tomcat7Runner.java > Allow for the creation of a war that is both executable and deployable > -- > > Key: MTOMCAT-188 > URL: https://issues.apache.org/jira/browse/MTOMCAT-188 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat7 >Affects Versions: 2.0-beta-1 >Reporter: Mitch Kyle >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.1 > > Attachments: tomcat-maven-plugin_standalone-war-goal_05122012.patch > > > Currently with the exec-war/-only goals, a jar or war is created that is > executable but not deployable to an existing tomcat meaning two release > artifacts would be required to take this approach. > Ideally, a new goal would be added for creating war files that can be > deployed to an existing tomcat or excuted directly. > Steps > a. Allow tomcat7-war-runner to copy the running war to the webapps folder if > some property is set > b. Add a goal to build some war with tomcat7-war-runner overlayed and add a > manifest with main-class set. > If this sounds interesting, I can have a patch available soon and any > feedback would be great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-192) Website text cleanup
[ https://issues.apache.org/jira/browse/MTOMCAT-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512124#comment-13512124 ] Hudson commented on MTOMCAT-192: Integrated in TomcatMavenPlugin-mvn3.x #222 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/222/]) [MTOMCAT-192] Website text cleanup Submitted by Glen Mazza. (Revision 1418085) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1418085 Files : * /tomcat/maven-plugin/trunk/src/site/apt/archetype.apt.vm * /tomcat/maven-plugin/trunk/src/site/apt/container-goals.apt * /tomcat/maven-plugin/trunk/src/site/apt/context-goals.apt * /tomcat/maven-plugin/trunk/src/site/apt/executable-war-jar.apt.vm * /tomcat/maven-plugin/trunk/src/site/apt/how-to-contribute.apt.vm * /tomcat/maven-plugin/trunk/src/site/apt/index.apt.vm * /tomcat/maven-plugin/trunk/src/site/apt/run-mojo-features.apt.vm > Website text cleanup > > > Key: MTOMCAT-192 > URL: https://issues.apache.org/jira/browse/MTOMCAT-192 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Reporter: Glen Mazza >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.1 > > Attachments: WebsiteChanges.patch > > > Patch makes various grammatical fixes to the Tomcat Maven Plugin website. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-191) Return the "redeploy" goal to the Maven plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512125#comment-13512125 ] Hudson commented on MTOMCAT-191: Integrated in TomcatMavenPlugin-mvn3.x #222 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/222/]) [MTOMCAT-191] Return the "redeploy" goal to the Maven plugin (Revision 1418084) Result = FAILURE olamy : http://svn.apache.org/viewvc/?view=rev&rev=1418084 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployMojo.java > Return the "redeploy" goal to the Maven plugin > -- > > Key: MTOMCAT-191 > URL: https://issues.apache.org/jira/browse/MTOMCAT-191 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement >Affects Versions: 2.0-beta-1, 2.0 >Reporter: Glen Mazza >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.1 > > > Best to add the "redeploy" goal to the tomcat7 plugin, to eliminate the need > for the user to have to remember/google the "-Dmaven.tomcat.update=true" > string or have to inefficiently call mvn tomcat7:undeploy and mvn > tomcat7:deploy sequentially. mvn tomcat:redeploy generally gets much more > use during testing/debugging/development than mvn tomcat:deploy, and also > acts like mvn tomcat:deploy if the WAR isn't there anyway. > This would also benefit archetype/tutorial writers by no longer requiring > them to hardcode the true configuration setting in the > pom.xml for the deploy goal at a risk of overriding a potential safety > mechanism of having tomcat7:deploy fail if the WAR is already there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-99) Make redeploy goal consistent with deploy goals
[ https://issues.apache.org/jira/browse/MTOMCAT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525795#comment-13525795 ] Hudson commented on MTOMCAT-99: --- Integrated in TomcatMavenPlugin-mvn3.x #224 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/224/]) [MTOMCAT-99] Make redeploy goal consistent with deploy goals fix tomcat7 part (Revision 1418097) [MTOMCAT-99] Make redeploy goal consistent with deploy goals fix tomcat6 part (Revision 1418095) Result = SUCCESS olamy : http://svn.apache.org/viewvc/?view=rev&rev=1418097 Files : * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployOnlyMojo.java olamy : http://svn.apache.org/viewvc/?view=rev&rev=1418095 Files : * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployOnlyMojo.java > 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.1 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-50) add support for JNDI datasource JDBC driver jar dependencies for the run goal
[ https://issues.apache.org/jira/browse/MTOMCAT-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100369#comment-13100369 ] jieryn commented on MTOMCAT-50: --- Yah, I don't think this is something the Maven plugin ought to solve. Proper use of Maven's dependency mechanism is the real solution here. Please close this JIRA. > add support for JNDI datasource JDBC driver jar dependencies for the run goal > - > > Key: MTOMCAT-50 > URL: https://issues.apache.org/jira/browse/MTOMCAT-50 > Project: Maven 2.x Tomcat Plugin > Issue Type: Improvement >Affects Versions: 1.0-beta-1 > Environment: os x 10.6.2, java 1.6.0_17, Maven 2.2.1 (r801777; > 2009-08-06 12:16:01-0700) >Reporter: Jonathan Russell >Priority: Minor > > I get a ClassNotFoundException for Oracle driver classes unless I drop the > jdbc driver jar into Java's extension directory when executing "mvn > tomcat:run-war" for my project. (see below) > If I were using an installed tomcat instance I know I could add the jar to > the /usr/local/tomcat/apache-tomcat-7.0.21/lib directory. I don't know if it > isn't supported, or if I just haven't found good documentation on this, but I > can't get this error to go away unless I add the jar into a Java extension > directory. > pom.xml excerpts: > > org.codehaus.mojo > tomcat-maven-plugin > > / > both > > > ... > > com.oracle > ojdbc14 > 10.2.0.4.0 > runtime > > context.xml excerpt: > > path="/" > docBase=".war" > debug="1" > reloadable="true" > crossContext="true" > > > type="javax.sql.DataSource" > maxActive="4" maxIdle="2" maxWait="6" > removeAbandoned="true" logAbandoned="true" > driverClassName="" > url="" > username="" password="" > NetworkProtocol="tcp" > DataSourceName="oracle.jdbc.xa.client.OracleXADataSource" > NativeXA="true" > allowLocalTransactions="true" > LoginTimeout="0" > ExplicitCachingEnabled="false" > ImplicitCachingEnabled="false" > MaxStatements="0" > /> > ... > > Stack trace: > ... > Caused by: org.hibernate.exception.GenericJDBCException: Cannot open > connection > at > org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) > at > org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) > at > org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) > at > org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52) > at > org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449) > at > org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167) > at > org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161) > at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577) > at org.hibernate.loader.Loader.doQuery(Loader.java:696) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) > at org.hibernate.loader.Loader.doList(Loader.java:2232) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129) > at org.hibernate.loader.Loader.list(Loader.java:2124) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) > at > org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363) > at > org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) > at com.ssn.dm.service.DM.query(DM.java:616) > ... 48 more > Caused by: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC > driver class 'oracle.jdbc.OracleDriver' > at > org.apache.tomcat.dbcp.dbcp.BasicDataSourc
[jira] [Commented] (MTOMCAT-87) Make http protocol configurable for the embedded Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102280#comment-13102280 ] Sebb commented on MTOMCAT-87: - @Adrien C The patch was attached without granting the ASF license. Please could you re-attach, this time granting the license (if you agree)? @Adam yes, there seems to be a problem with finding the attachment; I'll raise an issue with our infrastructure. > Make http protocol configurable for the embedded Tomcat > --- > > Key: MTOMCAT-87 > URL: https://issues.apache.org/jira/browse/MTOMCAT-87 > Project: Maven 2.x Tomcat Plugin > Issue Type: New Feature >Reporter: Adrien C > Attachments: http-protocol.patch > > > tomcat maven plugin 1.1 sets HTTP connector with default HTTP/1.1 protocol. > Being able to set another protocol (ex: > org.apache.coyote.http11.Http11NioProtocol) would be useful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-87) Make http protocol configurable for the embedded Tomcat
[ https://issues.apache.org/jira/browse/MTOMCAT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102507#comment-13102507 ] Hudson commented on MTOMCAT-87: --- Integrated in TomcatMavenPlugin #8 (See [https://builds.apache.org/job/TomcatMavenPlugin/8/]) [MTOMCAT-87] Make http protocol configurable for the embedded Tomcat Submitted by Adrien C olamy : http://svn.apache.org/viewvc/?view=rev&rev=1169647 Files : * /tomcat/maven-plugin/trunk/tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/AbstractRunMojo.java > Make http protocol configurable for the embedded Tomcat > --- > > Key: MTOMCAT-87 > URL: https://issues.apache.org/jira/browse/MTOMCAT-87 > Project: Maven 2.x Tomcat Plugin > Issue Type: New Feature >Reporter: Adrien C >Assignee: Olivier Lamy > Fix For: 2.0 > > Attachments: http-protocol.patch > > > tomcat maven plugin 1.1 sets HTTP connector with default HTTP/1.1 protocol. > Being able to set another protocol (ex: > org.apache.coyote.http11.Http11NioProtocol) would be useful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-97) rename current tomcat maven plugin to tomcat6 and add tomcat7
[ https://issues.apache.org/jira/browse/MTOMCAT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105742#comment-13105742 ] Hudson commented on MTOMCAT-97: --- Integrated in TomcatMavenPlugin #9 (See [https://builds.apache.org/job/TomcatMavenPlugin/9/]) [MTOMCAT-97] rename current tomcat maven plugin to tomcat6 and add tomcat7 : fix artifactId and project name, fix other pom samples [MTOMCAT-97] rename current tomcat maven plugin to tomcat6 and add tomcat7 rename current plugin to tomcat6 olamy : http://svn.apache.org/viewvc/?view=rev&rev=1171296 Files : * /tomcat/maven-plugin/trunk/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-plugin-it/src/test/project-resources/simple-war-project/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-plugin-it/src/test/project-resources/tomcat-run-multi-config/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-plugin-it/src/test/project-resources/usage-contextpath/pom.xml * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/pom.xml * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/examples/add-system-properties.apt.vm * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/examples/adjust-embedded-tomcat-version.apt.vm * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/examples/deployment-tomcat7.apt.vm * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/examples/deployment.apt.vm * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/usage.apt.vm olamy : http://svn.apache.org/viewvc/?view=rev&rev=1171292 Files : * /tomcat/maven-plugin/trunk/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-plugin * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin > rename current tomcat maven plugin to tomcat6 and add tomcat7 > -- > > Key: MTOMCAT-97 > URL: https://issues.apache.org/jira/browse/MTOMCAT-97 > Project: Maven 2.x Tomcat Plugin > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 2.0 > > > To prevent confusion for users, I'd like to rename the current version which > supports tomcat 6 to tomcat6 and add tomcat 7 support in tomcat7. > users will have now to use tomcat6:run instead tomcat:run. > Btw users will have to add a pluginGroup entry in ~/.m2/settings.xml as the > used groupId is not automatically discovered by maven core. > Any objections ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-195) Plugin uploads WAR file twice
[
https://issues.apache.org/jira/browse/MTOMCAT-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977815#comment-14977815
]
Raza commented on MTOMCAT-195:
--
I am also facing the similar issue:
[INFO] --- maven-war-plugin:2.6:war (default-war) @ EVOKE-Scraping ---
[INFO] Packaging webapp
[INFO] Assembling webapp [EVOKE-Scraping] in [E:\New Git
Space\EVOKE-Scraping\EVOKE-Scraping\target\EVOKE-Scraping]
[INFO] Processing war project
[INFO] Copying webapp resources [E:\New Git
Space\EVOKE-Scraping\EVOKE-Scraping\WebContent]
[INFO] Webapp assembled in [931 msecs]
[INFO] Building war: E:\softs\apache-tomcat-2\webapps\EVOKE-Scraping-war.war
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
EVOKE-Scraping ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] Copying 12 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ EVOKE-Scraping
---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
EVOKE-Scraping ---
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory E:\New Git
Space\EVOKE-Scraping\EVOKE-Scraping\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
EVOKE-Scraping ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ EVOKE-Scraping ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-war-plugin:2.6:war (default-war) @ EVOKE-Scraping ---
[INFO] Packaging webapp
[INFO] Assembling webapp [EVOKE-Scraping] in [E:\New Git
Space\EVOKE-Scraping\EVOKE-Scraping\target\EVOKE-Scraping]
[INFO] Processing war project
[INFO] Copying webapp resources [E:\New Git
Space\EVOKE-Scraping\EVOKE-Scraping\WebContent]
[INFO] Webapp assembled in [466 msecs]
[INFO] Building war: E:\softs\apache-tomcat-2\webapps\EVOKE-Scraping-war.war
[INFO]
[INFO] --- maven-install-plugin:2.4:install (default-install) @ EVOKE-Scraping
---
[INFO] No primary artifact to install, installing attached artifacts instead.
[INFO] Installing E:\New Git Space\EVOKE-Scraping\EVOKE-Scraping\pom.xml to
C:\Users\raza\.m2\repository\com\jocata\EVOKE-Scraping\1.0-SNAPSHOT\EVOKE-Scraping-1.0-SNAPSHOT.pom
[INFO] Installing E:\softs\apache-tomcat-2\webapps\EVOKE-Scraping-war.war to
C:\Users\raza\.m2\repository\com\jocata\EVOKE-Scraping\1.0-SNAPSHOT\EVOKE-Scraping-1.0-SNAPSHOT-war.war
[INFO] Installing E:\softs\apache-tomcat-2\webapps\EVOKE-Scraping-war.war to
C:\Users\raza\.m2\repository\com\jocata\EVOKE-Scraping\1.0-SNAPSHOT\EVOKE-Scraping-1.0-SNAPSHOT-war.war
[INFO]
[INFO] BUILD SUCCESS
> Plugin uploads WAR file twice
> -
>
> Key: MTOMCAT-195
> URL: https://issues.apache.org/jira/browse/MTOMCAT-195
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6
>Affects Versions: 2.0
> Environment: Win7/64, Maven 3.0.4
>Reporter: George Smith
>Assignee: Olivier Lamy (*$^¨%`£)
>
> When I deploy my WAR using maven, the target war (exact the same one) is
> being uploaded to the server twice. Can someone explain that?
> I am using this on my module:
> {code}clean install org.apache.tomcat.maven:tomcat6-maven-plugin:2.0:redeploy
> {code}
> From the Log file
> {code =xml}
> [INFO] --- maven-war-plugin:2.1.1:war (default-war) @ mobile-server ---
> [INFO] Packaging webapp
> [INFO] Assembling webapp [mobile-server] in
> [C:\develope\mobile\mobile-server\target\mobile-server]
> [INFO] Processing war project
> [INFO] Copying webapp resources
> [C:\develope\mobile\mobile-server\src\main\webapp]
> [INFO] Webapp assembled in [241 msecs]
> [INFO] Building war: C:\develope\mobile\mobile-server\target\mobile-server.war
> [INFO]
> [INFO] <<< tomcat6-maven-plugin:2.0:redeploy (default-cli) @ mobile-server <<<
> [INFO]
> [INFO] --- tomcat6-maven-plugin:2.0:redeploy (default-cli) @ mobile-server
> ---
> [INFO] Deploying war to http://myserver.eu/pra-mobile-server
> Uploading:
> http://myserver.eu/manager-test/deploy?path=%2Fmobile-server&update=true
> Uploaded:
> http://myserver.eu/manager-test/deploy?path=%2Fmobile-server&update=true
> (12678 KB at 49.3 KB/sec)
> Uploading:
> http://myserver.eu/manager-test/deploy?path=%2Fmobile-server&update=true
> Uploaded:
> http://myserver.eu/manager-test/deploy?path=%2Fmobile-server&update=true
> {code}
>
[jira] [Commented] (MTOMCAT-305) shutdown not correct working if embedded tomcat is started twice in same maven build
[ https://issues.apache.org/jira/browse/MTOMCAT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197389#comment-15197389 ] v_iftodi_oodrive commented on MTOMCAT-305: -- Hello, This merge request https://github.com/apache/tomcat-maven-plugin/pull/17 has existed for a while and claim (looking at the code it seems as well) to fix this issue. Will this be merged? I have encountered the same issue and it took a while for me to find the reason. > shutdown not correct working if embedded tomcat is started twice in same > maven build > > > Key: MTOMCAT-305 > URL: https://issues.apache.org/jira/browse/MTOMCAT-305 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.2 > Environment: multi-module project >Reporter: Oriel Maute >Assignee: Olivier Lamy (*$^¨%`£) > Labels: maven > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > We have a multi-module project with the modules A and B. > In module A we start and stop an embedded tomcat server within our > integration tests; same in module B. > The integration-tests for module A work perfectly. But after this, the start > of the embedded tomcat server for module B is not working because the port > 8080 is still in use from the integration test of module A. > The reason is that the shutdown on module A invokes on the Catalina Container > the "stop()" method, this method does not unbind the port 8080. > I think - specially in this scenario - the shutdown mojo should also invoke > the "destroy()" method after the "stop()" method on the Catalina Container. > If this is not possible in every case, it would be great to have a parameter > for the shutdown goal to specify if "stop" or "stop & destroy" should be > called on the Catalina Container. > > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.2 > > > tomcat-run > > run-war-only > > pre-integration-test > > > tomcat-shutdown > > shutdown > > post-integration-test > > > > 8080 > true > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-306) Allow port reuse when invoking plugin repeatedly in build
[ https://issues.apache.org/jira/browse/MTOMCAT-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225564#comment-15225564 ] Hudson commented on MTOMCAT-306: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x-windows #9 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x-windows/9/]) [MTOMCAT-306] Allow port reuse when invoking plugin repeatedly in build fixes #17 Signed-off-by: olivier lamy (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1737760]) * common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/EmbeddedRegistry.java > Allow port reuse when invoking plugin repeatedly in build > - > > Key: MTOMCAT-306 > URL: https://issues.apache.org/jira/browse/MTOMCAT-306 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: commons-lib >Affects Versions: 2.2 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.3 > > > see https://github.com/apache/tomcat-maven-plugin/pull/17 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-306) Allow port reuse when invoking plugin repeatedly in build
[ https://issues.apache.org/jira/browse/MTOMCAT-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225568#comment-15225568 ] Hudson commented on MTOMCAT-306: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #293 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/293/]) [MTOMCAT-306] Allow port reuse when invoking plugin repeatedly in build fixes #17 Signed-off-by: olivier lamy (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1737760]) * common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/EmbeddedRegistry.java > Allow port reuse when invoking plugin repeatedly in build > - > > Key: MTOMCAT-306 > URL: https://issues.apache.org/jira/browse/MTOMCAT-306 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: commons-lib >Affects Versions: 2.2 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.3 > > > see https://github.com/apache/tomcat-maven-plugin/pull/17 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-274) Tomcat8 integration tests fail with JDK 7 / Maven 3.2.2
[ https://issues.apache.org/jira/browse/MTOMCAT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421980#comment-15421980 ] Hudson commented on MTOMCAT-274: FAILURE: Integrated in Jenkins build TomcatMavenPlugin-mvn3.x-windows #10 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x-windows/10/]) 1. Fix: MTOMCAT-274 (updated maven-war-plugin version). 2. Fix: access_log.* files excluded from apache-rat-plugin configuration. These are generated during Tomcat run and should not be checked. (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756446]) * (edit) pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/deploy-only-war-project/pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/deploy-war-project/pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/simple-war-project/pom.xml > Tomcat8 integration tests fail with JDK 7 / Maven 3.2.2 > --- > > Key: MTOMCAT-274 > URL: https://issues.apache.org/jira/browse/MTOMCAT-274 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: OS name: "mac os x", version: "10.9.4", arch: "x86_64", > family: "mac" > Java version: 1.7.0_67, vendor: Oracle Corporation > Maven 3.2.2 >Reporter: Envious Guest > > When running integration tests for Tomcat8, like that: > mvn clean verify -pl :tomcat8-maven-plugin -am -P run-its > The build fails with following exception: > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2:war (default-war) > on project simple-war-project: Execution default-war of goal > org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2:war failed: Cannot > construct org.apache.maven.plugin.war.util.WebappStructure as it does not > have a no-args constructor > Debugging information > message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > cause-exception : > com.thoughtworks.xstream.converters.reflection.ObjectAccessException > cause-message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > class : org.apache.maven.plugin.war.util.WebappStructure > required-type : org.apache.maven.plugin.war.util.WebappStructure > path: /webapp-structure > line number : 1 > --- > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > 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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:364) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:198) > 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:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > 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:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.m
[jira] [Commented] (MTOMCAT-234) Tomcat8 Maven Plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421979#comment-15421979 ] Hudson commented on MTOMCAT-234: FAILURE: Integrated in Jenkins build TomcatMavenPlugin-mvn3.x-windows #10 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x-windows/10/]) Fix: MTOMCAT-234 (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756447]) * (edit) tomcat8-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat8/run/AbstractRunMojo.java * (edit) tomcat8-maven-plugin/src/test/java/org/apache/tomcat/maven/it/Tomcat8RunMultiConfigIT.java * (edit) tomcat8-maven-plugin/src/test/java/org/apache/tomcat/maven/it/Tomcat8SimpleWarProjectIT.java MTOMCAT-234 Classloading issues (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756445]) * (edit) tomcat8-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat8/run/RunMojo.java > Tomcat8 Maven Plugin > > > Key: MTOMCAT-234 > URL: https://issues.apache.org/jira/browse/MTOMCAT-234 > Project: Apache Tomcat Maven Plugin > Issue Type: Dependency upgrade >Affects Versions: 2.0, 2.1, 2.2 > Environment: Maven 3.1, Tomcat8.0RC1, Oracle JDK7u25 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Blocker > Fix For: 3.0 > > > Please provide initial version of Tomcat8 Maven Plugin. > I tried the recommendations in > http://tomcat.10.x6.nabble.com/Tomcat-8-Tomcat-Maven-Plugin-2-2-Tomcat8-Maven-Plugin-td4995858.html#none > but the guideline > http://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html > does not work for Tomcat8 . > The problem is in changed Tomcat 8 API, the maven throws folloving exception: > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:142) > ... 20 more > by: java.lang.NoSuchMethodError: > org.apache.catalina.startup.Tomcat.setDefaultRealm(Lorg/apache/catalina/Realm;)V > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:999) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:514) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more > The method setDefaultRealm is deprecated in Tomcat7 and was removed in > Tomcat8 as described in documentation: > http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html#setDefaultRealm(org.apache.catalina.Realm) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-234) Tomcat8 Maven Plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422022#comment-15422022 ] Hudson commented on MTOMCAT-234: FAILURE: Integrated in Jenkins build TomcatMavenPlugin-mvn3.x #294 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/294/]) Fix: MTOMCAT-234 (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756447]) * (edit) tomcat8-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat8/run/AbstractRunMojo.java * (edit) tomcat8-maven-plugin/src/test/java/org/apache/tomcat/maven/it/Tomcat8RunMultiConfigIT.java * (edit) tomcat8-maven-plugin/src/test/java/org/apache/tomcat/maven/it/Tomcat8SimpleWarProjectIT.java MTOMCAT-234 Classloading issues (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756445]) * (edit) tomcat8-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat8/run/RunMojo.java > Tomcat8 Maven Plugin > > > Key: MTOMCAT-234 > URL: https://issues.apache.org/jira/browse/MTOMCAT-234 > Project: Apache Tomcat Maven Plugin > Issue Type: Dependency upgrade >Affects Versions: 2.0, 2.1, 2.2 > Environment: Maven 3.1, Tomcat8.0RC1, Oracle JDK7u25 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Blocker > Fix For: 3.0 > > > Please provide initial version of Tomcat8 Maven Plugin. > I tried the recommendations in > http://tomcat.10.x6.nabble.com/Tomcat-8-Tomcat-Maven-Plugin-2-2-Tomcat8-Maven-Plugin-td4995858.html#none > but the guideline > http://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html > does not work for Tomcat8 . > The problem is in changed Tomcat 8 API, the maven throws folloving exception: > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:142) > ... 20 more > by: java.lang.NoSuchMethodError: > org.apache.catalina.startup.Tomcat.setDefaultRealm(Lorg/apache/catalina/Realm;)V > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:999) > at > org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:514) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) > ... 20 more > The method setDefaultRealm is deprecated in Tomcat7 and was removed in > Tomcat8 as described in documentation: > http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/startup/Tomcat.html#setDefaultRealm(org.apache.catalina.Realm) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-274) Tomcat8 integration tests fail with JDK 7 / Maven 3.2.2
[ https://issues.apache.org/jira/browse/MTOMCAT-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422023#comment-15422023 ] Hudson commented on MTOMCAT-274: FAILURE: Integrated in Jenkins build TomcatMavenPlugin-mvn3.x #294 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/294/]) 1. Fix: MTOMCAT-274 (updated maven-war-plugin version). 2. Fix: access_log.* files excluded from apache-rat-plugin configuration. These are generated during Tomcat run and should not be checked. (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1756446]) * (edit) pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/deploy-only-war-project/pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/deploy-war-project/pom.xml * (edit) tomcat8-maven-plugin/src/test/resources/simple-war-project/pom.xml > Tomcat8 integration tests fail with JDK 7 / Maven 3.2.2 > --- > > Key: MTOMCAT-274 > URL: https://issues.apache.org/jira/browse/MTOMCAT-274 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: OS name: "mac os x", version: "10.9.4", arch: "x86_64", > family: "mac" > Java version: 1.7.0_67, vendor: Oracle Corporation > Maven 3.2.2 >Reporter: Envious Guest > > When running integration tests for Tomcat8, like that: > mvn clean verify -pl :tomcat8-maven-plugin -am -P run-its > The build fails with following exception: > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2:war (default-war) > on project simple-war-project: Execution default-war of goal > org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2:war failed: Cannot > construct org.apache.maven.plugin.war.util.WebappStructure as it does not > have a no-args constructor > Debugging information > message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > cause-exception : > com.thoughtworks.xstream.converters.reflection.ObjectAccessException > cause-message : Cannot construct > org.apache.maven.plugin.war.util.WebappStructure as it does not have a > no-args constructor > class : org.apache.maven.plugin.war.util.WebappStructure > required-type : org.apache.maven.plugin.war.util.WebappStructure > path: /webapp-structure > line number : 1 > --- > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224) > 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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:364) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:198) > 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:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > 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:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExi
[jira] [Commented] (MTOMCAT-277) ailed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc (compile-protoc) on project hadoop-common: org.apache.maven.plugin.MojoExecutionException: pr
[ https://issues.apache.org/jira/browse/MTOMCAT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116840#comment-15116840 ] yys commented on MTOMCAT-277: - @Annies V Jose ,did you resolve this error? I am getting the same message: [ERROR] Failed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.6.3:prot oc (compile-protoc) on project hadoop-common: org.apache.maven.plugin.MojoExecut ionException: 'protoc --version' did not return a version -> [Help 1] I see that protobuf is installed and 'protoc --version' gives 'libprotoc 2.6.1',but this error happened again when i tried again. ps:I compiled hadoop on windows 64 > ailed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc > (compile-protoc) on project hadoop-common: > org.apache.maven.plugin.MojoExecutionException: protoc failure > > > Key: MTOMCAT-277 > URL: https://issues.apache.org/jira/browse/MTOMCAT-277 > Project: Apache Tomcat Maven Plugin > Issue Type: Question >Reporter: Annies V Jose >Assignee: Olivier Lamy (*$^¨%`£) > > I was trying to install hadoop > mvn package -DskipTests -Dtar -Pdist,native > when i executed instruction > i got error > Failed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc > (compile-protoc) on project hadoop-common: > org.apache.maven.plugin.MojoExecutionException: protoc failure > my installed protoc version is 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-277) ailed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc (compile-protoc) on project hadoop-common: org.apache.maven.plugin.MojoExecutionException: pr
[ https://issues.apache.org/jira/browse/MTOMCAT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116958#comment-15116958 ] yys commented on MTOMCAT-277: - I resovled my problem,it was caused by the 64-bit-windows and the version of jdk(1.8) is too high for hadoop.I replaced the jdk_1.8 with jdk_1.7，then copy thebinary file protoc.exe to C:\Windows\SysWOW64,rebuild it ,then it worked! thanks. > ailed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc > (compile-protoc) on project hadoop-common: > org.apache.maven.plugin.MojoExecutionException: protoc failure > > > Key: MTOMCAT-277 > URL: https://issues.apache.org/jira/browse/MTOMCAT-277 > Project: Apache Tomcat Maven Plugin > Issue Type: Question >Reporter: Annies V Jose >Assignee: Olivier Lamy (*$^¨%`£) > > I was trying to install hadoop > mvn package -DskipTests -Dtar -Pdist,native > when i executed instruction > i got error > Failed to execute goal org.apache.hadoop:hadoop-maven-plugins:2.4.1:protoc > (compile-protoc) on project hadoop-common: > org.apache.maven.plugin.MojoExecutionException: protoc failure > my installed protoc version is 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-255) Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on tomcat:run but not in tomcat:run-war
[ https://issues.apache.org/jira/browse/MTOMCAT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149815#comment-15149815 ] Hudson commented on MTOMCAT-255: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x-windows #7 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x-windows/7/]) [MTOMCAT-255] (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1730784]) * tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on > tomcat:run but not in tomcat:run-war > -- > > Key: MTOMCAT-255 > URL: https://issues.apache.org/jira/browse/MTOMCAT-255 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.2 > Environment: gilberto.andrade@A37710:~$ mvn -version > Apache Maven 3.0.4 (r1232337; 2012-01-17 05:44:56-0300) > Maven home: /home/gilberto.andrade/bin/maven > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_45/jre > Default locale: pt_BR, platform encoding: UTF-8 > OS name: "linux", version: "3.7.10-1.24-desktop", arch: "amd64", family: > "unix" >Reporter: Gilberto C Andrade >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.3 > > Attachments: MTOMCAT-255.patch, MTOMCAT-255.zip > > > Simple JSF 2.2 project with just one manage bean(PessoaMb) and one xhtml page. > 1 Run mvn clean tomcat7:run > 2 hitting http://localhost:8080/MTOMCAT-255/pessoaView.xhtml > 3 enter some value on field or click the consultar button > The same steps works when using tomcat7:run-war. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-255) Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on tomcat:run but not in tomcat:run-war
[ https://issues.apache.org/jira/browse/MTOMCAT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149852#comment-15149852 ] Hudson commented on MTOMCAT-255: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #291 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/291/]) [MTOMCAT-255] (olamy: [http://svn.apache.org/viewvc/?view=rev&rev=1730784]) * tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Getting "Target Unreachable, identifier 'pessoaBean' resolved to null" on > tomcat:run but not in tomcat:run-war > -- > > Key: MTOMCAT-255 > URL: https://issues.apache.org/jira/browse/MTOMCAT-255 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.2 > Environment: gilberto.andrade@A37710:~$ mvn -version > Apache Maven 3.0.4 (r1232337; 2012-01-17 05:44:56-0300) > Maven home: /home/gilberto.andrade/bin/maven > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: /usr/java/jdk1.7.0_45/jre > Default locale: pt_BR, platform encoding: UTF-8 > OS name: "linux", version: "3.7.10-1.24-desktop", arch: "amd64", family: > "unix" >Reporter: Gilberto C Andrade >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.3 > > Attachments: MTOMCAT-255.patch, MTOMCAT-255.zip > > > Simple JSF 2.2 project with just one manage bean(PessoaMb) and one xhtml page. > 1 Run mvn clean tomcat7:run > 2 hitting http://localhost:8080/MTOMCAT-255/pessoaView.xhtml > 3 enter some value on field or click the consultar button > The same steps works when using tomcat7:run-war. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-288) Tomcat cluster deployment?
Sbremal created MTOMCAT-288: --- Summary: Tomcat cluster deployment? Key: MTOMCAT-288 URL: https://issues.apache.org/jira/browse/MTOMCAT-288 Project: Apache Tomcat Maven Plugin Issue Type: Wish Reporter: Sbremal Would it be possible that add a feature to deploy WARs on multiple Tomcat instances building a Tomcat cluster? As cluster is the feature of Tomcat I would assume there is a feature for cluster deployment as well. The closest I found was FarmWarDeployer, does not look PRD ready. 1. We do not want to restructure our Jenkins jobs to accommodate cluster deployment (cut jobs half, introduce loops etc.) 2. We want to keep the cluster deployment as close to Tomcat as possible. 3. Tomcat manager is running on each Tomcat instance, i.e. there is no cluster manager. (?) 4. Apparently the best place for this feature would be the Maven Tomcat plug-in. The URL Maven passes to the plug-in would be a comma separated list of Tomcat instances, and the plug-in would iterate through this list performing deployment on each Tomcat. What do you think? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-176) Make deploy/redeploy (upload) less verbose for --batch-mode / --quiet
[ https://issues.apache.org/jira/browse/MTOMCAT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801425#comment-13801425 ] Hudson commented on MTOMCAT-176: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #257 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/257/]) [MTOMCAT-176] Make deploy/redeploy (upload) less verbose for --batch-mode / --quiet (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1534451) * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/deployer/TomcatManager.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractI18NTomcat6Mojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/AbstractCatalinaMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/AbstractTomcat7Mojo.java > Make deploy/redeploy (upload) less verbose for --batch-mode / --quiet > - > > Key: MTOMCAT-176 > URL: https://issues.apache.org/jira/browse/MTOMCAT-176 > Project: Apache Tomcat Maven Plugin > Issue Type: Wish > Components: commons-lib >Affects Versions: 2.0 >Reporter: Thomas GL >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.2 > > Attachments: > MTOMCAT-176__Do_not_show_transfer_progress_when_Maven_is_running_in_batch_mode.patch > > > Hi, > Using maven-tomcat-plugin:2.0 for integration testing deployments results in > some Jenkins job logs where 99% of the lines comes from the upload "progress > meter" (implemented in > "TomcatManager.RequestEntityImplementation.transferProgressed"). > In some other plugins with similar HTTP activity, this kind of output can be > turned off by launching Maven with "-B/--batch-mode" (and probably "--quiet" > too, although I never do that). This seems to be standard behavior for > plugins which uses Wagon or Aether. Would it be possible to implement a > similar behavior in the maven-tomcat-plugin? > Actually, I gave it a try today, but I couldn't find how to get the Maven > batch/quiet options through the plugin API. My other attempt was to reuse > the Wagon "TransferListener" instance (the implementation, which can be a > verbose or quiet progress meter, seems to be chosen depending on the Maven > CLI option), but I couldn't find a path to there neither. But it's my first > time in some Maven code, I probably have missed something. > Sure, if it's actually not possible to implement a quiet mode based on the > Maven CLI options, then an alternative would be to add a plugin-specific > parameter. But I think it would be a bit less convenient. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-239) jar can't use tomcat maven plugin
[ https://issues.apache.org/jira/browse/MTOMCAT-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801424#comment-13801424 ] Hudson commented on MTOMCAT-239: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #257 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/257/]) [MTOMCAT-239] src/main/webapp must not be mandatory when running a jar so create a fake one (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1534436) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java [MTOMCAT-239] when running a jar with tomcat7:run ServletContainerInitializer is ignored fix an issue with reactor containing a jar module with ServletContainerInitializer and running the webapp (target/classes from the jar is ignored during scanning) (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1534433) * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java * /tomcat/maven-plugin/trunk/pom.xml * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java > jar can't use tomcat maven plugin > - > > Key: MTOMCAT-239 > URL: https://issues.apache.org/jira/browse/MTOMCAT-239 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Romain Manni-Bucau >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > Attachments: jart7.zip > > > See > http://tomcat.10.x6.nabble.com/tomcat-mvn-plugin-amp-jar-lib-handling-td5004752.html -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-244) Upgrade Archetype Webapp IT Project to Selenium 2.x
[ https://issues.apache.org/jira/browse/MTOMCAT-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805072#comment-13805072 ] Hudson commented on MTOMCAT-244: UNSTABLE: Integrated in TomcatMavenPlugin-mvn3.x #258 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/258/]) [MTOMCAT-244] Upgrade Archetype Webapp IT Project to Selenium 2.x Submitted by Ryan Highley (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1535623) * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/pom.xml * /tomcat/maven-plugin/trunk/tomcat-maven-archetype/src/main/resources/archetype-resources/__rootArtifactId__-webapp-it/src/test/java/webapp/test/SimpleTest.java > Upgrade Archetype Webapp IT Project to Selenium 2.x > --- > > Key: MTOMCAT-244 > URL: https://issues.apache.org/jira/browse/MTOMCAT-244 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: commons-lib >Affects Versions: 2.1 >Reporter: Ryan Highley >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Attachments: tomcat-maven-plugin.patch > > > The generated webapp integration tests use the Selenium 1 Java API requiring > some additional work migrating to Selenium 2 WebDriver to use its additional > features. > The Selenium migration is relatively straightforward in the webapp-it > templates and pom should updating Selenium be desirable. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-245) Missing useBodyEncodingForURI parameter on connector
[ https://issues.apache.org/jira/browse/MTOMCAT-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811052#comment-13811052 ] Hudson commented on MTOMCAT-245: UNSTABLE: Integrated in TomcatMavenPlugin-mvn3.x #259 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/259/]) [MTOMCAT-245] Missing useBodyEncodingForURI parameter on connector Submitted by Cédric Dutoit for tomcat6 plugin too (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1537807) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java [MTOMCAT-245] Missing useBodyEncodingForURI parameter on connector Submitted by Cédric Dutoit (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1537804) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Missing useBodyEncodingForURI parameter on connector > > > Key: MTOMCAT-245 > URL: https://issues.apache.org/jira/browse/MTOMCAT-245 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6, tomcat7 >Affects Versions: 2.2 >Reporter: Cédric Dutoit >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Critical > Fix For: 2.2 > > Original Estimate: 1h > Remaining Estimate: 1h > > UseBodyEncodingForURI is unsupported yet (25 oct 2013) in 2.2-SNAPSHOT. > Please add it: > tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > @Parameter( property = "maven.tomcat.useBodyEncodingForURI", defaultValue = > "false" ) > private boolean useBodyEncodingForURI; > then next to "connector.setURIEncoding( uriEncoding );", add > connector.setUseBodyEncodingForURI( useBodyEncodingForURI ); > then next to "ajpConnector.setURIEncoding( uriEncoding );", add > ajpConnector.setUseBodyEncodingForURI( useBodyEncodingForURI ); -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-207) Allow truststoreFile in plugin configuration
[
https://issues.apache.org/jira/browse/MTOMCAT-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811051#comment-13811051
]
Hudson commented on MTOMCAT-207:
UNSTABLE: Integrated in TomcatMavenPlugin-mvn3.x #259 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/259/])
[MTOMCAT-207] Allow truststoreFile in plugin configuration
for tomcat7 plugin (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1537821)
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
[MTOMCAT-207] Allow truststoreFile in plugin configuration
for tomcat6 plugin (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1537820)
*
/tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java
> Allow truststoreFile in plugin configuration
>
>
> Key: MTOMCAT-207
> URL: https://issues.apache.org/jira/browse/MTOMCAT-207
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: tomcat7
>Affects Versions: 2.1
>Reporter: Marcel Silberhorn
>Assignee: Olivier Lamy (*$^¨%`£)
> Labels: connector
> Fix For: 2.2
>
>
> follow up MTOMCAT-56
> We can define keystoreFile but not the trustStore used for client SSL
> Certificate handshakes.
> See
> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_BIO_and_NIO
> => {{truststoreFile}}
> This affects functionality of MTOMCAT-190
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-217) configure a pre define http port for standalone jar
[ https://issues.apache.org/jira/browse/MTOMCAT-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811064#comment-13811064 ] Hudson commented on MTOMCAT-217: UNSTABLE: Integrated in TomcatMavenPlugin-mvn3.x #260 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/260/]) [MTOMCAT-217] configure a pre define http port for standalone jar (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1537827) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-war-runner/src/main/java/org/apache/tomcat/maven/runner/Tomcat7Runner.java * /tomcat/maven-plugin/trunk/tomcat7-war-runner/src/main/java/org/apache/tomcat/maven/runner/Tomcat7RunnerCli.java > configure a pre define http port for standalone jar > --- > > Key: MTOMCAT-217 > URL: https://issues.apache.org/jira/browse/MTOMCAT-217 > Project: Apache Tomcat Maven Plugin > Issue Type: New Feature > Components: tomcat7 >Affects Versions: 2.0-beta-1, 2.1 > Environment: Windows7, maven2.2.1, JDK-Oracle 7.0_u15 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > > I use maven-tomcat-plugin to create war-exec.jar with following definition: > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.2-SNAPSHOT > > src/main/tomcat/server.xml > > > > create-exec-war > > exec-war-only > > package > > > > But when the server.xml is specified - to configure some defaults for server > like NIO, etc. than the CLI parameters are ignored: > java -jar war-exec.jar -httpPort > does not change the the server port. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-241) Documentation needed for config element
[
https://issues.apache.org/jira/browse/MTOMCAT-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811186#comment-13811186
]
Hudson commented on MTOMCAT-241:
SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #262 (See
[https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/262/])
[MTOMCAT-241] Documentation needed for config element
Submitted by Neale Upstone. (olamy:
http://svn.apache.org/viewvc/?view=rev&rev=1537893)
*
/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java
> Documentation needed for config element
> -
>
> Key: MTOMCAT-241
> URL: https://issues.apache.org/jira/browse/MTOMCAT-241
> Project: Apache Tomcat Maven Plugin
> Issue Type: Documentation
> Components: tomcat6, tomcat7
>Reporter: Neale Upstone
>Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.2
>
>
> The following could/should be the documentation for the two
> AbstractRunMojo.webapps fields, so that documentation is more useful to end
> users.
> {code:java}
> /**
> * Collection of webapp artifacts to be deployed. Elements are
> <webapp> and contain
> * usual GAVC plus contextPath and/or contextFile elements.
> * @see {@link Webapp}
> * @since 2.0
> */
> @Parameter
> private List webapps;
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-224) Tomcat Maven Plugin is not marked @threadSafe
[ https://issues.apache.org/jira/browse/MTOMCAT-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812589#comment-13812589 ] Hudson commented on MTOMCAT-224: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #263 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/263/]) [MTOMCAT-224] Tomcat Maven Plugin is not marked @threadSafe (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1538483) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ExplodedMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/InplaceMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ListMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RedeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ReloadMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ResourcesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RolesMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/RunWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ServerInfoMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/SessionsMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ShutdownMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StartMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/StopMojo.java * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/UndeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/DeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/RedeployOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/deploy/UndeployMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ExecWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/RunWarOnlyMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/ShutdownMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/StandaloneWarOnlyMojo.java > Tomcat Maven Plugin is not marked @threadSafe > - > > Key: MTOMCAT-224 > URL: https://issues.apache.org/jira/browse/MTOMCAT-224 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6 >Affects Versions: 2.1 >Reporter: Diego Lemos >Assignee: Olivier Lamy (*$^¨%`£) > Labels: build, maven > Fix For: 2
[jira] [Commented] (MTOMCAT-159) WAR dependencies extracted every run
[ https://issues.apache.org/jira/browse/MTOMCAT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812688#comment-13812688 ] Hudson commented on MTOMCAT-159: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #264 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/264/]) [MTOMCAT-159] WAR dependencies extracted every run Submitted by Robert Hollencamp (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1538504) * /tomcat/maven-plugin/trunk/common-tomcat-maven-plugin/src/main/java/org/apache/tomcat/maven/common/run/DefaultClassLoaderEntriesCalculator.java > WAR dependencies extracted every run > > > Key: MTOMCAT-159 > URL: https://issues.apache.org/jira/browse/MTOMCAT-159 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: commons-lib >Affects Versions: 2.0 >Reporter: Robert Hollencamp >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.2 > > Attachments: MTOMCAT-159-1.diff > > > If there is a WAR dependency, it is extracted to > target/apache-tomcat-maven-plugin/ARTIFACT_NAME. This directory is deleted > and re-created every invocation of the plugin, meaning that all WAR > dependencies are re-extracted every run. > Do not delete these extracted directories. Instead check the last modified > timestamp of the directory against the last modified timestamp of the WAR > dependency, and re-extract only if the WAR is newer -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13812689#comment-13812689 ] Hudson commented on MTOMCAT-92: --- SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #264 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/264/]) [MTOMCAT-92] Bind tomcat to a self-chosen network interface (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1538502) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Bind tomcat to a self-chosen network interface > -- > > Key: MTOMCAT-92 > URL: https://issues.apache.org/jira/browse/MTOMCAT-92 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Björn Michael >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > > Tomcat is bound to 0.0.0.0 (all interfaces) by default. I feel the need to > change this binding to e.g. localhost (127.0.0.1) or another interface by > adding a 127.0.0.1 to plugin configuration in pom.xml. This is > often necessary for security or firewall reasons during the development of > web applications. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13814469#comment-13814469 ] Hudson commented on MTOMCAT-92: --- SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #267 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/267/]) [MTOMCAT-92] setup for https and ajp connectors too (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539186) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractRunMojo.java > Bind tomcat to a self-chosen network interface > -- > > Key: MTOMCAT-92 > URL: https://issues.apache.org/jira/browse/MTOMCAT-92 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Björn Michael >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > > Tomcat is bound to 0.0.0.0 (all interfaces) by default. I feel the need to > change this binding to e.g. localhost (127.0.0.1) or another interface by > adding a 127.0.0.1 to plugin configuration in pom.xml. This is > often necessary for security or firewall reasons during the development of > web applications. > Thanks in advance. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-84) tomcat:reload logs the wrong message
[ https://issues.apache.org/jira/browse/MTOMCAT-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814470#comment-13814470 ] Hudson commented on MTOMCAT-84: --- SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #267 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/267/]) [MTOMCAT-84] tomcat:reload logs the wrong message Submitted by Michael Osipov. (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539191) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/ReloadMojo.java > tomcat:reload logs the wrong message > > > Key: MTOMCAT-84 > URL: https://issues.apache.org/jira/browse/MTOMCAT-84 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Michael Osipov >Assignee: Olivier Lamy (*$^¨%`£) >Priority: Minor > Fix For: 2.2 > > Attachments: ASF.LICENSE.NOT.GRANTED--MTOMCAT-84.patch, > MTOMCAT-84.patch > > > Instead of emitting "Reloading app", it emits "Redeploying app". I have > patched the issue. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-196) Add the possiblilty to search warRunDepencies and extraDependcies throug the dependencyManagement
[ https://issues.apache.org/jira/browse/MTOMCAT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814758#comment-13814758 ] Hudson commented on MTOMCAT-196: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #268 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/268/]) [MTOMCAT-196] for warRunDependencies too (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539227) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractStandaloneWarMojo.java [MTOMCAT-196] Add the possiblilty to search warRunDepencies and extraDependcies throug the dependencyManagement (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539226) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java > Add the possiblilty to search warRunDepencies and extraDependcies throug the > dependencyManagement > - > > Key: MTOMCAT-196 > URL: https://issues.apache.org/jira/browse/MTOMCAT-196 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat7 >Affects Versions: 2.0 >Reporter: Guillaume Soing >Assignee: Olivier Lamy (*$^¨%`£) > Labels: features > Fix For: 2.2 > > > It wiil be nice to do not specify the version of the warRunDepency and > extraDependency, it will be easier to handle war version during the release > process. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-161) Executable WAR: extraDependencies (JARs) should not be extracted but used directly
[ https://issues.apache.org/jira/browse/MTOMCAT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814760#comment-13814760 ] Hudson commented on MTOMCAT-161: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #268 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/268/]) [MTOMCAT-161] add a filter to exclude some files from jars when building self executable war/jar (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539220) * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java * /tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractStandaloneWarMojo.java > Executable WAR: extraDependencies (JARs) should not be extracted but used > directly > -- > > Key: MTOMCAT-161 > URL: https://issues.apache.org/jira/browse/MTOMCAT-161 > Project: Apache Tomcat Maven Plugin > Issue Type: Improvement > Components: tomcat6, tomcat7 >Affects Versions: 2.0-beta-1 > Environment: tomcat7, windows, maven3 >Reporter: Manuel Hartl >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > > When i create exec-war to create a a self-executable webapp, dependencies (at > least extraDependencies) war extracted and added directly to the resulting > JAR. > the resulting jar contains a META-INF with lots of duplicate MANIFEST files, > etc. > this at least breaks signed JARs (e.g. JCE providers) -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-211) The .war file is not extracted from executable war
[ https://issues.apache.org/jira/browse/MTOMCAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814759#comment-13814759 ] Hudson commented on MTOMCAT-211: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #268 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/268/]) [MTOMCAT-211] The .war file is not extracted from executable war (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539209) * /tomcat/maven-plugin/trunk/tomcat7-war-runner/src/main/java/org/apache/tomcat/maven/runner/Tomcat7Runner.java > The .war file is not extracted from executable war > -- > > Key: MTOMCAT-211 > URL: https://issues.apache.org/jira/browse/MTOMCAT-211 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.2 > Environment: Windows 7 64bit, Oracle JDK-1.7.0.11, Maven-2.2 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > Attachments: maven-tomcat-test-0.0.1-SNAPSHOT-war-exec.jar, > maven-tomcat-test.zip > > > I create simple web-app project, build it by mvn clean package. > Than I try to execute the created JAR, but the following exception was thrown: > java -jar maven-tomcat-test-0.0.1-SNAPSHOT-war-exec.jar > Exception in thread "main" java.io.FileNotFoundException: > .extract\webapps\ctx\test.war (The system cannot find the path specified) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:212) > at java.io.FileOutputStream.(FileOutputStream.java:165) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.expand(Tomcat7Runner.java:680) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.extract(Tomcat7Runner.java:555) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:200) > at > org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:204) > When I look at ".extract\webapps\ctx\" , the folder is empty. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-248) 404 links in http://tomcat.apache.org/maven-plugin-2.2/tomcat6-maven-plugin/index.html
[ https://issues.apache.org/jira/browse/MTOMCAT-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817095#comment-13817095 ] Hudson commented on MTOMCAT-248: SUCCESS: Integrated in TomcatMavenPlugin-mvn3.x #270 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/270/]) [MTOMCAT-248] fix broken links (olamy: http://svn.apache.org/viewvc/?view=rev&rev=1539919) * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/examples/add-system-properties.apt.vm * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/index.apt * /tomcat/maven-plugin/trunk/tomcat6-maven-plugin/src/site/apt/index.apt.vm > 404 links in > http://tomcat.apache.org/maven-plugin-2.2/tomcat6-maven-plugin/index.html > -- > > Key: MTOMCAT-248 > URL: https://issues.apache.org/jira/browse/MTOMCAT-248 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Olivier Lamy (*$^¨%`£) >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 3.0 > > -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Commented] (MTOMCAT-211) The .war file is not extracted from executable war
[ https://issues.apache.org/jira/browse/MTOMCAT-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817342#comment-13817342 ] Hudson commented on MTOMCAT-211: FAILURE: Integrated in TomcatMavenPlugin-mvn3.x #271 (See [https://builds.apache.org/job/TomcatMavenPlugin-mvn3.x/271/]) https://issues.apache.org/jira/browse/MTOMCAT-211 Followup to r1539920 Introduce a local variable to cache the object created by expandFile.getParentFile() call. (kkolinko: http://svn.apache.org/viewvc/?view=rev&rev=1539956) * /tomcat/maven-plugin/trunk/tomcat7-war-runner/src/main/java/org/apache/tomcat/maven/runner/Tomcat7Runner.java > The .war file is not extracted from executable war > -- > > Key: MTOMCAT-211 > URL: https://issues.apache.org/jira/browse/MTOMCAT-211 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat7 >Affects Versions: 2.2 > Environment: Windows 7 64bit, Oracle JDK-1.7.0.11, Maven-2.2 >Reporter: Petr Novak >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: 2.2 > > Attachments: maven-tomcat-test-0.0.1-SNAPSHOT-war-exec.jar, > maven-tomcat-test.zip > > > I create simple web-app project, build it by mvn clean package. > Than I try to execute the created JAR, but the following exception was thrown: > java -jar maven-tomcat-test-0.0.1-SNAPSHOT-war-exec.jar > Exception in thread "main" java.io.FileNotFoundException: > .extract\webapps\ctx\test.war (The system cannot find the path specified) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:212) > at java.io.FileOutputStream.(FileOutputStream.java:165) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.expand(Tomcat7Runner.java:680) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.extract(Tomcat7Runner.java:555) > at > org.apache.tomcat.maven.runner.Tomcat7Runner.run(Tomcat7Runner.java:200) > at > org.apache.tomcat.maven.runner.Tomcat7RunnerCli.main(Tomcat7RunnerCli.java:204) > When I look at ".extract\webapps\ctx\" , the folder is empty. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-251) User is not logged in as current user
ram created MTOMCAT-251: --- Summary: User is not logged in as current user Key: MTOMCAT-251 URL: https://issues.apache.org/jira/browse/MTOMCAT-251 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6 Reporter: ram Assignee: Olivier Lamy (*$^¨%`£) Priority: Minor -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Created] (MTOMCAT-252) User is not logged in as current user
ram created MTOMCAT-252: --- Summary: User is not logged in as current user Key: MTOMCAT-252 URL: https://issues.apache.org/jira/browse/MTOMCAT-252 Project: Apache Tomcat Maven Plugin Issue Type: Bug Components: tomcat6 Affects Versions: 2.0-beta-1 Reporter: ram Assignee: Olivier Lamy (*$^¨%`£) Fix For: backlog -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
[jira] [Resolved] (MTOMCAT-252) User is not logged in as current user
[ https://issues.apache.org/jira/browse/MTOMCAT-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ram resolved MTOMCAT-252. - Resolution: Fixed Fix Version/s: 2.0-beta-1 where you fixed > User is not logged in as current user > - > > Key: MTOMCAT-252 > URL: https://issues.apache.org/jira/browse/MTOMCAT-252 > Project: Apache Tomcat Maven Plugin > Issue Type: Bug > Components: tomcat6 >Affects Versions: 2.0-beta-1 >Reporter: ram >Assignee: Olivier Lamy (*$^¨%`£) > Fix For: backlog, 2.0-beta-1 > > -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
