Re: tomcat8-maven-plugin
Hi,
I started a branch called tc8.x ( see
https://github.com/apache/tomcat-maven-plugin )
or in svn https://svn.apache.org/repos/asf/tomcat/maven-plugin/branches/tc8.x/
The tomcat8 plugin is currently working except if you use jsp. ATM
because of low bandwith I don't have to have a look to fix that. Maybe
in the next few weeks.
But if you have time to help that will be a pleasure for me to
integrate your fix :P
Cheers
Olivier
On 11 October 2014 20:32, LG Optimusv wrote:
> Hi All,
>
> I know that there's no tomcat8-maven-plugin (yet) and using tomcat8 with
> tomcat7-maven-plugin like this:
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.2
>
>
> org.apache.tomcat.embed
> tomcat-embed-core
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-util
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-coyote
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-api
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-jdbc
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-dbcp
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-servlet-api
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-jsp-api
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-jasper
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-jasper-el
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-el-api
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-catalina
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-tribes
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-catalina-ha
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-annotations-api
> ${tomcat8.version}
>
>
> org.apache.tomcat
> tomcat-juli
> ${tomcat8.version}
>
>
> org.apache.tomcat.embed
> tomcat-embed-logging-juli
> ${tomcat8.version}
>
>
> org.apache.tomcat.embed
> tomcat-embed-logging-log4j
> ${tomcat8.version}
>
>
>
>
> doesn't work. The error is when mvn tomcat7:run is executed is:
>
> [ERROR] Failed to execute goal
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:run (default-cli) on
> project webapp: Execution default-cli of goal
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:run failed: An API
> incompatibility was encountered while executing
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:run:
> java.lang.NoSuchMethodError:
> org.apache.catalina.startup.Tomcat.setDefaultRealm(Lorg/apache/catalina/Realm;)V
>
> Is there anyway to get around this?
>
> Thanks.
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
[ANN] Apache Tomcat Maven plugin 2.2
Hi, The Apache Tomcat is pleased to announce the release of the 2.2 version. This plugin can used to run your war project inside an embeded Apache Tomcat and to deploy your project to a running Apache Tomcat instance. Documentation available: http://tomcat.apache.org/maven-plugin-2.2/index.html Release Notes - Apache Tomcat Maven Plugin - Version 2.2 ** Bug * [MTOMCAT-84] - tomcat:reload logs the wrong message * [MTOMCAT-92] - Bind tomcat to a self-chosen network interface * [MTOMCAT-165] - http status 401 reported as success * [MTOMCAT-203] - org.apache.jasper.JasperException tags not found in classes/META-INF/*.tld * [MTOMCAT-211] - The .war file is not extracted from executable war * [MTOMCAT-214] - Default attachArtifactClassifierType for AbstractStandaloneWarMojo should be war * [MTOMCAT-215] - Multiple manifests under META-INF, two Main-Class entries * [MTOMCAT-231] - tomcat6:run fail with jdk1.5 because commons-io-2.4 requires jdk1.6 * [MTOMCAT-233] - 404 links at http://tomcat.apache.org/maven-plugin-2.0/modules.html * [MTOMCAT-236] - tomcat-maven-archetype creates project with failing test * [MTOMCAT-239] - jar can't use tomcat maven plugin * [MTOMCAT-240] - Artifacts with same artifactID but different groupID are skipped ** Documentation * [MTOMCAT-241] - Documentation needed for config element ** Improvement * [MTOMCAT-159] - WAR dependencies extracted every run * [MTOMCAT-161] - Executable WAR: extraDependencies (JARs) should not be extracted but used directly * [MTOMCAT-196] - Add the possiblilty to search warRunDepencies and extraDependcies throug the dependencyManagement * [MTOMCAT-207] - Allow truststoreFile in plugin configuration * [MTOMCAT-212] - Missing "skip" configuration option * [MTOMCAT-224] - Tomcat Maven Plugin is not marked @threadSafe * [MTOMCAT-245] - Missing useBodyEncodingForURI parameter on connector ** New Feature * [MTOMCAT-217] - configure a pre define http port for standalone jar Have Fun, -- The Apache Tomcat Team. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Embedding Tomcat
On 23 October 2013 08:58, Pïd stèr wrote: > Hello, > > To scratch an itch I've been working on an alternative means to embed > Tomcat: > > https://github.com/pidster-dot-org/embed-apache-tomcat > > There's a core utility for embedding Tomcat[1] and a JUnit Rule[2] for > testing that uses it, e.g. > > 1. > https://github.com/pidster-dot-org/embed-apache-tomcat/blob/master/embed-apache-tomcat-core/src/test/java/org/pidster/tomcat/embed/TomcatSimpleTest.java > > 2. > https://github.com/pidster-dot-org/embed-apache-tomcat/blob/master/embed-apache-tomcat-test/src/test/java/org/pidster/tomcat/embed/junit/TomcatServerRuleTest.java > Interesting. But is there any way to use port 0 (I mean using random port instead of hardcoded one) ? > I've snuck it into Maven Central here: > > http://search.maven.org/#search%7Cga%7C1%7Corg.pidster > > I'd be interested to hear feedback from the list. > > > p -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: regarding maven sleep plugin
That's not a Tomcat related question. BTW I don't know this sleep plugin and cannot find it. You need to ensure it's available tru the repository manager instance you are using On 24 October 2013 16:18, Irfan Sayed wrote: > hi, > > i need to use maven sleep plugin to have delay for some seconds in the war > deployment > i am facing following error while running command > > C:\workspace\ua_final\DataIntegration\di-services>mvn > org.jboss.maven.plugins:maven-sleep-plugin:1.0:helpmojo > [INFO] Scanning for projects... > [WARNING] The POM for org.jboss.maven.plugins:maven-sleep-plugin:jar:1.0 is > missing, no dependency information available > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 0.284s > [INFO] Finished at: Wed Oct 23 21:59:29 PDT 2013 > [INFO] Final Memory: 3M/15M > [INFO] > > [ERROR] Plugin org.jboss.maven.plugins:maven-sleep-plugin:1.0 or one of its > dependencies could not be resolved: Failed to read artifact descriptor for > org.j > 0: Failure to find org.jboss.maven.plugins:maven-sleep-plugin:pom:1.0 in > http://10.211.162.106:8081/nexus/content/groups/public was cached in the > local repo > ntil the update interval of nexus has elapsed or updates are forced -> > [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException > C:\workspace\ua_final\DataIntegration\di-services> > > have someone used this plugin before ? > please suggest > > regards, -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: regarding maven tomcat7 plugin
no.
On 24 October 2013 16:28, Irfan Sayed wrote:
> is there any tomcat7:start goal, i have seen tomcat7:shutdown goal but not
> the start goal
>
> please suggest
>
> regards
>
>
>
> On Thu, Oct 24, 2013 at 9:43 AM, Irfan Sayed wrote:
>
>> thanks awesome !
>> really appreciate
>>
>> regards
>>
>>
>>
>> On Thu, Oct 24, 2013 at 7:53 AM, Olivier Lamy wrote:
>>
>>> Have a look at the goal names list here:
>>>
>>> http://tomcat.apache.org/maven-plugin-2.1/tomcat7-maven-plugin/plugin-info.html
>>>
>>> HTH,
>>> --
>>> Olivier
>>>
>>> On 24 October 2013 02:37, Irfan Sayed wrote:
>>> > it worked. i haven't restarted the tomcat.
>>> > ok. now is there any plugin/goal which will redeploy the existing war
>>> file
>>> > and redeploy ?
>>> >
>>> > i am using tomcat7 plugin and there is no any redeploy goal
>>> > please suggest
>>> >
>>> > regards
>>> >
>>> >
>>> >
>>> >
>>> > On Wed, Oct 23, 2013 at 5:42 PM, Konstantin Kolinko
>>> > wrote:
>>> >
>>> >> 2013/10/23 Irfan Sayed :
>>> >> > hi,
>>> >> >
>>> >> > i am facing issues while deploying war file using tomcat7 plugin.
>>> tomcat
>>> >> as
>>> >> > application is running fine . i can manually deploy files but not
>>> through
>>> >> > maven plugin
>>> >> >
>>> >> > following are my files :
>>> >> >
>>> >> > *.m2 (settings.xml)*
>>> >> >
>>> >> >
>>> >> > TomcatServer
>>> >> > admin
>>> >> > password
>>> >> >
>>> >> >
>>> >> > *pom.xml contents:*
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >org.apache.tomcat.maven
>>> >> >tomcat7-maven-plugin
>>> >> >2.1
>>> >> >
>>> >> >http://localhost:8080/manager/text
>>> >> >TomcatServer
>>> >> > /${project.build.finalName}
>>> >> >
>>> >> >
>>> >> >
>>> >> > di
>>> >> >
>>> >> >
>>> >> >
>>> >> > *tomcat-users.xml*
>>> >> > *
>>> >> > *
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > >> >> > roles="admin-script,admin-gui,standard,manager-gui"/>
>>> >> >
>>> >> >
>>> >> > i have gone lots of Google search and implemented most of the
>>> suggestion,
>>> >> > still not working
>>> >> > please suggest . i am stuck
>>> >> >
>>> >>
>>> >> >http://localhost:8080/manager/text
>>> >>
>>> >> 1. Is your server running at localhost?
>>> >>
>>> >> 2. What is in Tomcat's access log?
>>> >> (Does Tomcat log that Maven tries to access it?)
>>> >>
>>> >> 3. How it fails? What is reported by Maven?
>>> >>
>>> >> 4. Have you restarted the server after editing tomcat-users.xml ?
>>> >>
>>> >> Best regards,
>>> >> Konstantin Kolinko
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> >> For additional commands, e-mail: users-h...@tomcat.apache.org
>>> >>
>>> >>
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Ecetera: http://ecetera.com.au
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: regarding maven tomcat7 plugin
Have a look at the goal names list here:
http://tomcat.apache.org/maven-plugin-2.1/tomcat7-maven-plugin/plugin-info.html
HTH,
--
Olivier
On 24 October 2013 02:37, Irfan Sayed wrote:
> it worked. i haven't restarted the tomcat.
> ok. now is there any plugin/goal which will redeploy the existing war file
> and redeploy ?
>
> i am using tomcat7 plugin and there is no any redeploy goal
> please suggest
>
> regards
>
>
>
>
> On Wed, Oct 23, 2013 at 5:42 PM, Konstantin Kolinko
> wrote:
>
>> 2013/10/23 Irfan Sayed :
>> > hi,
>> >
>> > i am facing issues while deploying war file using tomcat7 plugin. tomcat
>> as
>> > application is running fine . i can manually deploy files but not through
>> > maven plugin
>> >
>> > following are my files :
>> >
>> > *.m2 (settings.xml)*
>> >
>> >
>> > TomcatServer
>> > admin
>> > password
>> >
>> >
>> > *pom.xml contents:*
>> >
>> >
>> >
>> >
>> >org.apache.tomcat.maven
>> >tomcat7-maven-plugin
>> >2.1
>> >
>> >http://localhost:8080/manager/text
>> >TomcatServer
>> > /${project.build.finalName}
>> >
>> >
>> >
>> > di
>> >
>> >
>> >
>> > *tomcat-users.xml*
>> > *
>> > *
>> >
>> >
>> >
>> >
>> >
>> >
>> > > > roles="admin-script,admin-gui,standard,manager-gui"/>
>> >
>> >
>> > i have gone lots of Google search and implemented most of the suggestion,
>> > still not working
>> > please suggest . i am stuck
>> >
>>
>> >http://localhost:8080/manager/text
>>
>> 1. Is your server running at localhost?
>>
>> 2. What is in Tomcat's access log?
>> (Does Tomcat log that Maven tries to access it?)
>>
>> 3. How it fails? What is reported by Maven?
>>
>> 4. Have you restarted the server after editing tomcat-users.xml ?
>>
>> Best regards,
>> Konstantin Kolinko
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Deploying war from dependency with tomcat7-maven-plugin
for 1) your jars must be in the plugin dependencies section (see jdbc driver here http://tomcat.apache.org/maven-plugin-trunk/run-mojo-features.html ) for 2) I understand you simply want to run a war (and maybe run unit tests) so unpacking with the dependency looks to be the solution. HTH Olivier On 9 September 2013 13:18, Greg Amerson wrote: > Hello all, > > I'm trying to use the tomcat7-maven-plugin, specifically running the *mvn > tomcat7:run* command. > > However, in my case I have two requirements that are different than the > documentation provides for and I'm wondering if it is possible with the > current tomcat7-maven-plugin. > > 1. need to deploy several jars to the global tomcat classpath (i.e. same as > copying them into /lib/ext/ folder in a standalone install). > 2. need to deploy a war to the ROOT context but instead of packaging the > current project from source, I just need to point to an existing WAR as a > dependency. > > So in my project there will be no webapp source. I simply want to run a > tomcat with some extra jars in /lib/ext/ directory and also deploy a war > that is obtained via a with war type instead of packaged from > source. > > Thanks in advance for any help! > > -- > Greg Amerson > Liferay Developer Tools > Liferay, Inc. www.liferay.com -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Re:[OT] tomcat 7 maven plugin run on a installed tomcat not embedded
2013/7/18 fachhoch : > tomcat7 maven plugin goal tomcat7:run, documentation says its starts > an embedded tomcat , is it possible to configure this goal to use use an > installed server ? I want to use an installed server as > my app has dependency on other app which should run on the same > tomcat Not possible > > > > -- > View this message in context: > http://tomcat.10.x6.nabble.com/tomcat-7-maven-plugin-run-on-a-installed-tomcat-not-embedded-tp5001919p5001937.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Maven plugin for Tomcat 8?
Currently no idea. That will probably need an other module (tomcat8). 2013/5/21 Rossen Stoyanchev : > Is there any way to use the Tomcat maven plugin with Tomcat 8 (i.e. trunk > snapshots)? The documentation lists how to configure Tomcat 6 and 7 only > [1]. > > Rossen > > [1] http://tomcat.apache.org/maven-plugin-trunk/ -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 8 + Tomcat Maven Plugin 2.2 + Tomcat8 Maven Plugin?
Hi, Apologize for delayed response. I have not tested that. I don't know if embedder trunk (i.e tomcat8) is compatible. Did you try using tomcat8 snapshot as described here: http://tomcat.apache.org/maven-plugin-trunk/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html 2013/3/14 Nick Williams : > https://repository.apache.org/content/repositories/snapshots/org/apache/tomcat/maven/ > > In snapshots there is only tomcat6-maven-plugin and tomcat7-maven-plugin. So, > even though my Maven dependencies are on Tomcat 8.0-SNAPSHOT, any "executable > war" I build with the plugin has Tomcat 7 classes in it, meaning the > application won't run (NoClassDefFound, etc.). > > What needs to be done to get a tomcat8-maven-plugin snapshot started? Is this > a whole new project that hasn't been started yet? Or does a new build > configuration just need to be created? -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin: Build on executable war file
2013/2/28 Timothy Astle : > I'll chime in here :) We create the artifact that we want, but we have two. > The WAR created by the maven war plugin, and the overlay war that is > standalone. But we still need the war to package it in the standalone artifact. And all the logic to create a war is in the maven war plugin. And frankly I don't want to copy/paste all this logic to clone it in the tomcat plugin (doesn't make sense IMHO) Maybe what you can try is to use pom packaging (instead of the one you are probably currently using war packaging) and then use the war plugin to package the war which need to be included in the standalone. As it the generated war won't be an attached artifact and won't be deploy. NOTE: It's a solution I didn't test :-) > > We were hoping to only deploy the tomcat overlay war since it does > everything that the other war does, plus contain tomcat. By doing this, we > hope to avoid confusion from staff that may grab the wrong war file from our > artifact repository (Nexus) and accidentally provide it to customers. So > we're trying to be proactively safe. > > Additionally, we have a Selenium grid set up. When our Jenkins build system > makes a build, cargo to grabs the war and failsafe runs our selenium > integration tests. All tests must pass before any artifact is deployed to > Nexus. So in a sense, it feels like cheating to have the tests all pass on > the non-standalone artifact, but we ship the standalone one. I've thought > about using maven tomcat plugin as a means to possibly shore this up, but > there is still a part of me that likes the aspect of being able to deploy to > any type of container via cargo. I haven't had a chance to dig into this > yet, perhaps Rich has, but any expert advice is always much appreciated. > > Tim > > > > > > > On 27/02/2013 6:46 PM, Olivier Lamy wrote: >> >> 2013/2/27 Richard McAleer : >>> >>> Hi, >>> We're using tomcat7-maven-plugin 2.1 to build an executable war using the >>> standalone-war-only goal. The maven build still generates the normal war >>> file as well as the executable .war created by the plugin. However, >>> since >>> the standalone-war-only goal generates a war that is both executable and >>> deployable, we really don't need to generate the normal war file. >>> >>> Is there a good way of generating just the executable war's using the >>> plugin? We could probably have maven delete the original .war file and >>> rename the executable .war to the normal webapp name, but that doesn't >>> seem >>> like the best way of doing it. >> >> Currently no. As the generated executable war/jar contains this war >> (not an exploded war) so it's mandatory to have it. >> BTW what is your use case ? >>> >>> Thanks, >>> Richard >>> >>> -- >>> Richard McAleer >>> Developer >>> Web Development Team >>> >>> *CARIS* <http://www.caris.com> >>> 115 Waggoners Lane >>> Fredericton, New Brunswick >>> CanadaE3B 2L4 >>> Tel: +1.506.458.8533 Fax: +1.506.459.3849 >>> www.caris.com <http://www.caris.com> >>> >>> *Connect with CARIS* >>> Twitter <http://www.twitter.com/CARIS_GIS> | LinkedIn >>> <http://www.linkedin.com/groups?mostPopular=&gid=3217878> | Facebook >>> >>> <https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878> >>> | Google+ >>> >>> <https://plus.google.com/b/114389770462919844434/114389770462919844434/posts> >>> | YouTube <http://www.youtube.com/user/CARISGIS> >>> >>> Download your free copy of CARIS Easy View today! >>> www.caris.com/easyview <http://www.caris.com/easyview> >>> >>> _ >>> This email and any files transmitted with it are confidential and >>> intended >>> only for the addressee(s). If you are not the intended recipient(s) >>> please >>> notify us by email reply. You should not use, disclose, distribute or >>> copy >>> this communication if received in error. >>> >>> Any views or opinions expressed in this email are solely those of the >>> author >>> and do not necessarily represent those of the company. No binding >>> contract >>> will result from this email until such time as a written document is >>> signed >>> on behalf of the company. >>> >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] tomcat7-maven-plugin
2013/2/28 Jose María Zaragoza : > Hello: > > How is it possible that tomcat7-maven-plugin has got a 'deploy' goal > but not 'undeploy' goal ? sure ? http://tomcat.apache.org/maven-plugin-2.1/tomcat7-maven-plugin/undeploy-mojo.html :-) > > Regards > > > 2013/2/27 Olivier Lamy : >> 2013/2/27 Richard McAleer : >>> Hi, >>> We're using tomcat7-maven-plugin 2.1 to build an executable war using the >>> standalone-war-only goal. The maven build still generates the normal war >>> file as well as the executable .war created by the plugin. However, since >>> the standalone-war-only goal generates a war that is both executable and >>> deployable, we really don't need to generate the normal war file. >>> >>> Is there a good way of generating just the executable war's using the >>> plugin? We could probably have maven delete the original .war file and >>> rename the executable .war to the normal webapp name, but that doesn't seem >>> like the best way of doing it. >> Currently no. As the generated executable war/jar contains this war >> (not an exploded war) so it's mandatory to have it. >> BTW what is your use case ? >>> >>> Thanks, >>> Richard >>> >>> -- >>> Richard McAleer >>> Developer >>> Web Development Team >>> >>> *CARIS* <http://www.caris.com> >>> 115 Waggoners Lane >>> Fredericton, New Brunswick >>> CanadaE3B 2L4 >>> Tel: +1.506.458.8533 Fax: +1.506.459.3849 >>> www.caris.com <http://www.caris.com> >>> >>> *Connect with CARIS* >>> Twitter <http://www.twitter.com/CARIS_GIS> | LinkedIn >>> <http://www.linkedin.com/groups?mostPopular=&gid=3217878> | Facebook >>> <https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878> >>> | Google+ >>> <https://plus.google.com/b/114389770462919844434/114389770462919844434/posts> >>> | YouTube <http://www.youtube.com/user/CARISGIS> >>> >>> Download your free copy of CARIS Easy View today! >>> www.caris.com/easyview <http://www.caris.com/easyview> >>> >>> _ >>> This email and any files transmitted with it are confidential and intended >>> only for the addressee(s). If you are not the intended recipient(s) please >>> notify us by email reply. You should not use, disclose, distribute or copy >>> this communication if received in error. >>> >>> Any views or opinions expressed in this email are solely those of the author >>> and do not necessarily represent those of the company. No binding contract >>> will result from this email until such time as a written document is signed >>> on behalf of the company. >>> >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin: Build on executable war file
2013/2/27 Richard McAleer : > Hi, > We're using tomcat7-maven-plugin 2.1 to build an executable war using the > standalone-war-only goal. The maven build still generates the normal war > file as well as the executable .war created by the plugin. However, since > the standalone-war-only goal generates a war that is both executable and > deployable, we really don't need to generate the normal war file. > > Is there a good way of generating just the executable war's using the > plugin? We could probably have maven delete the original .war file and > rename the executable .war to the normal webapp name, but that doesn't seem > like the best way of doing it. Currently no. As the generated executable war/jar contains this war (not an exploded war) so it's mandatory to have it. BTW what is your use case ? > > Thanks, > Richard > > -- > Richard McAleer > Developer > Web Development Team > > *CARIS* <http://www.caris.com> > 115 Waggoners Lane > Fredericton, New Brunswick > CanadaE3B 2L4 > Tel: +1.506.458.8533 Fax: +1.506.459.3849 > www.caris.com <http://www.caris.com> > > *Connect with CARIS* > Twitter <http://www.twitter.com/CARIS_GIS> | LinkedIn > <http://www.linkedin.com/groups?mostPopular=&gid=3217878> | Facebook > <https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878> > | Google+ > <https://plus.google.com/b/114389770462919844434/114389770462919844434/posts> > | YouTube <http://www.youtube.com/user/CARISGIS> > > Download your free copy of CARIS Easy View today! > www.caris.com/easyview <http://www.caris.com/easyview> > > _ > This email and any files transmitted with it are confidential and intended > only for the addressee(s). If you are not the intended recipient(s) please > notify us by email reply. You should not use, disclose, distribute or copy > this communication if received in error. > > Any views or opinions expressed in this email are solely those of the author > and do not necessarily represent those of the company. No binding contract > will result from this email until such time as a written document is signed > on behalf of the company. > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
[ANN] Apache Tomcat Maven plugin 2.1
Hi, The Apache Tomcat is pleased to announce the release of the 2.1 version. This plugin can used to run your war project inside an embeded Apache Tomcat and to deploy your project to a running Apache Tomcat instance. Documentation available: http://tomcat.apache.org/maven-plugin-2.1/index.html Release Notes - Apache Tomcat Maven Plugin - Version 2.1 ** Bug * [MTOMCAT-61] - maven tomcat:run ignores the useSeperateTomcatClassloaded when using serverXml property * [MTOMCAT-119] - tomcat7:run-war fails because it expects META-INF\context.xml * [MTOMCAT-128] - The plugin ignores and/or parses web.xml incorrectally when using tomcatWebXml option * [MTOMCAT-173] - Direct dependencies are not added to classpath * [MTOMCAT-175] - warDirectory property has wrong standard value in release version 2.0 * [MTOMCAT-179] - Null pointer dereference in RunMojo * [MTOMCAT-180] - Allow hostName and alias to be configured for tomcat6:run etc * [MTOMCAT-182] - Typo in Tomcat6 AbstractRunWarMojo MOJO * [MTOMCAT-185] - change phase for tomcat6/7:run to process-classes * [MTOMCAT-186] - Closing executable JAR does not call ServletContextListener.contextDestroyed() * [MTOMCAT-194] - Odd error message in switching from Codehaus to Maven Tomcat6 plugin * [MTOMCAT-197] - tomcat7:undeploy goal not ignoring non-war projects * [MTOMCAT-198] - Fix base classes for redeploy and redeploy-only goals * [MTOMCAT-206] - Runtime dependencies within multi module projects are not loaded. ** Improvement * [MTOMCAT-99] - Make redeploy goal consistent with deploy goals * [MTOMCAT-188] - Allow for the creation of a war that is both executable and deployable * [MTOMCAT-190] - Client Certificate settings for connector * [MTOMCAT-191] - Return the "redeploy" goal to the Maven plugin * [MTOMCAT-192] - Website text cleanup * [MTOMCAT-199] - Text cleanup of goal definitions * [MTOMCAT-200] - Tomcat7:redeploy * [MTOMCAT-208] - JaCoCo instrumentation errors when running StandaloneWarMojo ** New Feature * [MTOMCAT-163] - No undeploy goal ** Question * [MTOMCAT-187] - Scan resources executing run goal Have Fun, -- The Apache Tomcat Team. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat WAR Plugin - target release date for 2.1?
Hi, My plan was starting a release process around late next week. 2013/2/1 Timothy Astle : > I'm planning a software release that uses a feature added to the > 2.1-SNAPSHOT of the Tomcat WAR Plugin. > > Does anyone know when 2.1 would be released, or if there is going to be a > tagged deployment released to the Apache Maven repository (alpha or beta) in > the near future? > > Tim > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.34 and ecj 3.7.2/4.2.1
Huge Thanks for you effort on that !! 2013/1/31 Ralph Schaer : > The bundle got accepted. ecj 4.2.1 is now available from the maven central > repository. > > Ralph > > On Sat, Jan 26, 2013 at 7:42 AM, Ralph Schaer wrote: > >> I started the process of uploading the ecj 4.2.1 artefacts to the maven >> central repository. >> I followed the description from Ian. >> http://ianbrandt.com/2011/10/10/ecj-3-7-1-published-to-maven-central/ >> >> According to this documentation >> >> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository >> the process is in the last stage "My Bundle is Uploaded. What Next?". >> So I have to wait for the sonatype people and see if they approve the >> bundle. >> >> The files are in this staging repository: >> https://oss.sonatype.org/content/repositories/central_bundles-274/ >> >> Ralph >> >> >> On Mon, Jan 21, 2013 at 11:33 AM, Ralph Schaer wrote: >> >>> You find the ecj jar on this site: >>> http://download.eclipse.org/eclipse/downloads/drops4/R-4.2.1-201209141800/ >>> >>> Section: >>> JDT Core Batch Compiler >>> >>> >>> Ralph >>> >>> On Mon, Jan 21, 2013 at 11:23 AM, Supun Malinga wrote: >>> >>>> Hi Guys, >>>> >>>> Where can I find the ecj 4.2.1 jar?, except from the tomcat >>>> distribution. >>>> >>>> thank you. >>>> >>>> >>>> On Fri, Jan 11, 2013 at 1:47 PM, Konstantin Kolinko >>>> wrote: >>>> >>>> > 2013/1/11 Ralph Schaer : >>>> > > Hi >>>> > > >>>> > > Tomcat 7.0.34 bumped ecj to version 4.2.1. But the pom file >>>> > > of tomcat-embed-jasper still points to version 3.7.2 of ecj. >>>> > > Is it safe to use ecj 3.7.2 with Tomcat 7.0.34? >>>> > > It's unfortunately not possible to override this, because I haven't >>>> found >>>> > > the 4.2.1 artifact in the central repository. >>>> > > >>>> > >>>> > 1. Thank you for reporting the issue. I fixed this in svn, but 7.0.35 >>>> > has already been tagged several hours ago. >>>> > >>>> > 2. Absence of ecj 4.2.1 in central repository is not a stopper. It >>>> > happened before and is expected to happen in the future. You can >>>> > install it locally. >>>> > >>>> > http://markmail.org/message/xyw3bv2flmbhsdt4 >>>> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=283745 >>>> > >>>> > 3. I personally would recommend to go with 4.2.1. >>>> > >>>> > It is known that Eclipse 3.7.2 fails to compile the current Tomcat >>>> > trunk sources (the compiler crashes), 4.2.1 works fine. >>>> > >>>> > There was report by Jess Holle on a crash with 4.2.1, but what causes >>>> > the crash is unknown and I have not observed anything like that. >>>> > http://tomcat.markmail.org/thread/oe5wwu3dm2zcjp4m >>>> > >>>> > Anyway, if you are in doubt, you may try to run precompilation for >>>> > your JSPs with JspC just to make sure that everything compiles nicely. >>>> > (I do not suggest to actually use the compiled classes. I mean just to >>>> > run a compilation to check that they are compilable). >>>> > >>>> > 4. The bump of ecj version included a change in one of java classes. >>>> > >>>> > @Override is a compile-time annotation. You should still be able to >>>> > run with 3.7.2. >>>> > http://svn.apache.org/viewvc?view=revision&revision=1411587 >>>> > >>>> > Best regards, >>>> > Konstantin Kolinko >>>> > >>>> > - >>>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>>> > For additional commands, e-mail: users-h...@tomcat.apache.org >>>> > >>>> > >>>> >>>> >>>> -- >>>> Supun Malinga >>>> >>> >>> >> -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat common and webapp classloader
2012/12/17 Antonio Manuel Muñiz Martín : > Hi Olivier, > > My fault, I found the problem, I had two spring versions in my dependencies. > However I have another question, could I use dependencies from > non-central repository in the plugin dependencies? It seems like the > plugin only search for dependencies at central. > Must work if you declare your repository in section. > Thanks, > Antonio. > > 2012/12/17 Olivier Lamy : >> Any sample project you could share ? Attach it in a new jira issue. >> That will help for debugging your use case. >> Thanks >> >> 2012/12/16 Antonio Manuel Muñiz Martín : >>> Hello. >>> >>> I'm giving a try to tomcat6-maven-plugin. Good work guys, it's great! >>> >>> I'm getting some extrange behavior with classloaders, I think that >>> tomcat common classloader is interfering in webapp classloader. I have >>> Spring 2.5.5 artifacts at tomcat level (tomcat lib) and Spring 3.1.1 >>> at webapp level (WEB-INF/lib), and I'm getting errors because 2.5.5 is >>> loaded before in the webapp. >>> >>> I tried to use "delegate = false" in the plugin config in order to get >>> first the webapp artifacts, but the behavior is the same. >>> >>> My plugin config: >>> >>> org.apache.tomcat.maven >>> tomcat6-maven-plugin >>> 2.0 >>> >>> 8080 >>> /app >>> src/main/config/server.xml >>> >>> src/main/config/tomcat-conf >>> >>> >>> -Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.conf >>> >>> false >>> >>> >>> >>> es.klicap.clinker >>> josso-tomcat60-agent >>> 1.3.0 >>> >>> >>> >>> >>> Note that josso-tomcat60-agent is the dependency that I want at tomcat >>> level and it gets Spring 2.5.5 transitively. >>> >>> Am I using "delegate" correctly? >>> >>> Thanks! >>> >>> -- >>> Antonio Manuel Muñiz Martín >>> Software Developer at klicap - ingeniería del puzle >>> >>> work phone + 34 954 894 322 >>> www.klicap.es | blog.klicap.es >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > > -- > Antonio Manuel Muñiz Martín > Software Developer at klicap - ingeniería del puzle > > work phone + 34 954 894 322 > www.klicap.es | blog.klicap.es > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat common and webapp classloader
Any sample project you could share ? Attach it in a new jira issue. That will help for debugging your use case. Thanks 2012/12/16 Antonio Manuel Muñiz Martín : > Hello. > > I'm giving a try to tomcat6-maven-plugin. Good work guys, it's great! > > I'm getting some extrange behavior with classloaders, I think that > tomcat common classloader is interfering in webapp classloader. I have > Spring 2.5.5 artifacts at tomcat level (tomcat lib) and Spring 3.1.1 > at webapp level (WEB-INF/lib), and I'm getting errors because 2.5.5 is > loaded before in the webapp. > > I tried to use "delegate = false" in the plugin config in order to get > first the webapp artifacts, but the behavior is the same. > > My plugin config: > > org.apache.tomcat.maven > tomcat6-maven-plugin > 2.0 > > 8080 > /app > src/main/config/server.xml > > src/main/config/tomcat-conf > > > -Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.conf > > false > > > > es.klicap.clinker > josso-tomcat60-agent > 1.3.0 > > > > > Note that josso-tomcat60-agent is the dependency that I want at tomcat > level and it gets Spring 2.5.5 transitively. > > Am I using "delegate" correctly? > > Thanks! > > -- > Antonio Manuel Muñiz Martín > Software Developer at klicap - ingeniería del puzle > > work phone + 34 954 894 322 > www.klicap.es | blog.klicap.es > > --------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin
2012/12/13 Josh Gooding : > On Wed, Dec 12, 2012 at 6:05 PM, Olivier Lamy wrote: > >> Good detailed description :-). >> > > Hey even I get it right once in a while... ;) > > >> I just wonder about the cli you are using ? >> > > cli as in command line interface? - Win 7, CentOS, and Ubuntu terminals, > and yes I get my fair share of flack for not letting Eclipse "just do it". > Of course I'm a control freak when it comes to my code... :-) I mean mvn tomcat7:deploy or something else ? or you bind deploy to a lifecycle phase ? > >> >> 2012/12/12 Josh Gooding : >> > I didn't want to come here to ask as I always hate to bother anyone, but >> > maybe I should have come here first. I'm coming up short on answers and >> > ideas. I'm having an issue with using maven and the tomcat7 plugin. >> > >> > Maven version -3.0.4 >> > Tomcat version - 7.0.29 >> > .jdk version - 1.6 >> > tomcat7-maven-plugin version - 2.0 >> > >> > Hey group, I am having an issue here with using the tomcat7-maven-plugin >> > in conjunction with the tomcat 7 manager. here's what I have so far. >> > >> > tomcat-users.xml - >> > >> > >> > >> > >> > >> > > > roles="manager-gui,manager-script,admin"/> >> > >> > >> > in my M2_HOME/conf/settings.xml: (note not in my .m2/ directory) >> > (I'll get to this definition in a minute) >> > >> > org.apache.tomcat.maven >> > >> > >> > >> > >> > LocalTomcatServer >> > localTomcatAdmin >> > password >> > >> > >> > >> > now for the last piece, in my pom-deploy.xml (parent) I have this: >> > >> > >> > org.apache.tomcat.maven >> > tomcat7-maven-plugin >> > 2.0 >> > >> > LocalTomcatServer >> > /TripTixRX >> > 8080 >> > >> > >> > >> > I have verified that the manager works with the applied credentials, I >> can >> > login and supply the credentials to my local /manager/html. >> > >> > The problem is that when I deploy through maven as mvn tomcat7:deploy and >> > returns me the dreaded 401 - Unauthorized page with the same credentials. >> > It's almost like maven is not parsing the configuration for the plugin >> > maybe? >> > >> > At this point I don't know what to do. I've turned on verbose output in >> > maven and it shows what appears that the plugin is attempting to upload >> the >> > war file twice and returns the 401 page. >> > >> > >> > I also have a question as to getting this to work initially. I added the >> > org.apache.tomcat.maven to my >> conf/settings.xml >> > to get the tomcat7 plugin to download and work, is this normal or should >> I >> > not have to define it here? I mean having to change and version maven >> > settings.xml files seems a bit counter intuitive for preserving maximum >> > portability right, or am I looking at this from the wrong angle? >> > >> > Any information anyone can provide as to where to look or what could be >> > causing this issue, I would be greatly appreciated. >> > >> > Warmest regards, >> > >> > - Josh >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin
Good detailed description :-). I just wonder about the cli you are using ? 2012/12/12 Josh Gooding : > I didn't want to come here to ask as I always hate to bother anyone, but > maybe I should have come here first. I'm coming up short on answers and > ideas. I'm having an issue with using maven and the tomcat7 plugin. > > Maven version -3.0.4 > Tomcat version - 7.0.29 > .jdk version - 1.6 > tomcat7-maven-plugin version - 2.0 > > Hey group, I am having an issue here with using the tomcat7-maven-plugin > in conjunction with the tomcat 7 manager. here's what I have so far. > > tomcat-users.xml - > > > > > > roles="manager-gui,manager-script,admin"/> > > > in my M2_HOME/conf/settings.xml: (note not in my .m2/ directory) > (I'll get to this definition in a minute) > > org.apache.tomcat.maven > > > > > LocalTomcatServer > localTomcatAdmin > password > > > > now for the last piece, in my pom-deploy.xml (parent) I have this: > > > org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0 > > LocalTomcatServer > /TripTixRX > 8080 > > > > I have verified that the manager works with the applied credentials, I can > login and supply the credentials to my local /manager/html. > > The problem is that when I deploy through maven as mvn tomcat7:deploy and > returns me the dreaded 401 - Unauthorized page with the same credentials. > It's almost like maven is not parsing the configuration for the plugin > maybe? > > At this point I don't know what to do. I've turned on verbose output in > maven and it shows what appears that the plugin is attempting to upload the > war file twice and returns the 401 page. > > > I also have a question as to getting this to work initially. I added the > org.apache.tomcat.maven to my conf/settings.xml > to get the tomcat7 plugin to download and work, is this normal or should I > not have to define it here? I mean having to change and version maven > settings.xml files seems a bit counter intuitive for preserving maximum > portability right, or am I looking at this from the wrong angle? > > Any information anyone can provide as to where to look or what could be > causing this issue, I would be greatly appreciated. > > Warmest regards, > > - Josh -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 Maven Plugin - set MaxPermSize
2012/12/11 David Miller :
> I'm using the tomcat-maven plugin to set a value for MaxPermSize but it's
> not working.
>
> You can see in the below plugin my setting for JAVA_OPTS - I've also tried
> MAVEN_OPTS and CATALINA_OPTS.
>
> I can see that it's not working using jvisualvm (can also tell because my
> app eventually craps out).
>
> The only way that I can get an increase in perm gen size is to explicitly
> set it like this:
> MAVEN_OPTS="-XX:MaxPermSize=1024m"
>
> Is it possible to use the tomcat-maven plugin to specify MaxPermSize size?
Nope that's the only way as running tomcat with the plugin is not done
in a jvm forked mode but in the same jvm as maven.
>
> Thanks!
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0
>
>
> -XX:MaxPermSize=1024M
>
> 5
>
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
> /xyz
>
>
>
> com.sun.faces
> jsf-api
> 2.0.9
>
>
> com.sun.faces
> jsf-impl
> 2.0.9
>
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: warDirectory property wrong evaluated in release version 2.0 ?
Thanks it's now fixed.
2012/9/17 Florian Maertl :
> Jira is raised:
>
> https://issues.apache.org/jira/browse/MTOMCAT-175
>
> Thanks
> Florian
>
> -Original Message-
> From: Olivier Lamy [mailto:ol...@apache.org]
> Sent: Montag, 17. September 2012 15:19
> To: Tomcat Users List
> Subject: Re: warDirectory property wrong evaluated in release version
> 2.0 ?
>
> Hi,
> yup there is an issue here:
> http://svn.apache.org/repos/asf/tomcat/maven-plugin/trunk/tomcat6-maven-
> plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunW
> arMojo.java
> only for tomcat6 mojo.
>
> can you load a jira entry for that ?
> Thanks,
> --
> Olivier
>
> 2012/9/17 Florian Maertl :
>> Hi all
>>
>>
>>
>> Today I updated the tomcat6-maven-plugin version in my project from
>> 2.0-beta-1 to 2.0.
>>
>> Since then I got this exceptions when I'm starting the embedded tomcat
>> instance:
>>
>>
>>
>> Sep 17, 2012 2:17:15 PM org.apache.catalina.startup.Embedded start
>>
>> INFO: Starting tomcat server
>>
>> Sep 17, 2012 2:17:15 PM org.apache.catalina.core.StandardEngine start
>>
>> INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
>>
>> Sep 17, 2012 2:17:15 PM org.apache.catalina.core.StandardContext
>> resourcesStart
>>
>> SEVERE: Error starting static Resources
>>
>> java.lang.IllegalArgumentException: Document base
>>
> /data/local/dvimgde/workspaces/classic.flo/daffiM2/trunk/daffi.core/targ
>> et/${project.build.finalName does not exist or is not a readable
>> directory
>>
>> at
>>
> org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav
>> a:142)
>>
>> at
>>
> org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.
>> java:4319)
>>
>> at
>>
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4488
>> )
>>
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>>
>> at
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
>>
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>>
>> at
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>>
>> at
>> org.apache.catalina.startup.Embedded.start(Embedded.java:825)
>>
>> at
>>
> org.apache.tomcat.maven.plugin.tomcat6.AbstractRunMojo.startContainer(Ab
>> stractRunMojo.java:850)
>>
>> at
>>
> org.apache.tomcat.maven.plugin.tomcat6.AbstractRunMojo.execute(AbstractR
>> unMojo.java:429)
>>
>> at
>>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui
>> ldPluginManager.java:101)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
>> va:209)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
>> va:153)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
>> va:145)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
>> LifecycleModuleBuilder.java:84)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
>> LifecycleModuleBuilder.java:59)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild
>> (LifecycleStarter.java:183)
>>
>> at
>>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleSt
>> arter.java:161)
>>
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>
>> at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>
>> at
>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>
>> at
>> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>
>> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>
>> at
>>
> sun.reflect.NativeMethodAccessorImpl.inv
Re: warDirectory property wrong evaluated in release version 2.0 ?
Hi,
yup there is an issue 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
only for tomcat6 mojo.
can you load a jira entry for that ?
Thanks,
--
Olivier
2012/9/17 Florian Maertl :
> Hi all
>
>
>
> Today I updated the tomcat6-maven-plugin version in my project from
> 2.0-beta-1 to 2.0.
>
> Since then I got this exceptions when I'm starting the embedded tomcat
> instance:
>
>
>
> Sep 17, 2012 2:17:15 PM org.apache.catalina.startup.Embedded start
>
> INFO: Starting tomcat server
>
> Sep 17, 2012 2:17:15 PM org.apache.catalina.core.StandardEngine start
>
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
>
> Sep 17, 2012 2:17:15 PM org.apache.catalina.core.StandardContext
> resourcesStart
>
> SEVERE: Error starting static Resources
>
> java.lang.IllegalArgumentException: Document base
> /data/local/dvimgde/workspaces/classic.flo/daffiM2/trunk/daffi.core/targ
> et/${project.build.finalName does not exist or is not a readable
> directory
>
> at
> org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.jav
> a:142)
>
> at
> org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.
> java:4319)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4488
> )
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
>
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>
> at
> org.apache.catalina.startup.Embedded.start(Embedded.java:825)
>
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractRunMojo.startContainer(Ab
> stractRunMojo.java:850)
>
> at
> org.apache.tomcat.maven.plugin.tomcat6.AbstractRunMojo.execute(AbstractR
> unMojo.java:429)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui
> ldPluginManager.java:101)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:209)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.ja
> va:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
> LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
> LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild
> (LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleSt
> arter.java:161)
>
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>
> at
> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>
> at
> org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche
> r.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2
> 30)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc
> her.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352
> )
>
> Sep 17, 2012 2:17:15 PM org.apache.catalina.core.StandardContext start
>
> SEVERE: Error in resourceStart()
>
>
>
> Please note the missing closing "}" after project.build.finalName.
>
>
>
> But if I explicitely define the "warDirectory&q
[ANN] Apache Tomcat Maven Plugin 2.0
Hi, The Apache Tomcat is pleased to announce the release of the 2.0 version. This plugin can used to run your war project inside an embeded Apache Tomcat and to deploy your project to a running Apache Tomcat instance. Documentation available: http://tomcat.apache.org/maven-plugin-2.0/index.html Release Notes - Apache Tomcat Maven Plugin - Version 2.0 ** Bug * [MTOMCAT-116] - NonRepeatableRequestException when executing goal tomcat6:deploy * [MTOMCAT-118] - tomcat7:run wont accept additionalClasspathDir arguments * [MTOMCAT-123] - Can't add test scoped dependency filters to web.xml * [MTOMCAT-129] - Regression of MTOMCAT-54 in tomcat7-maven-plugin * [MTOMCAT-133] - Servlet mapping to "/" does not work * [MTOMCAT-134] - Empty additionalClasspathDir causes NPE in RunMojo.java * [MTOMCAT-135] - tomcat7:run does not load HandlesTypes in application classes * [MTOMCAT-136] - Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal * [MTOMCAT-138] - Cannot define the embedded Tomcat version * [MTOMCAT-139] - All static resources gives error 404 * [MTOMCAT-141] - Context root "/" not working for Tomcat 7 Run * [MTOMCAT-142] - contextFile path="..." ignored when using tomcat7:run * [MTOMCAT-143] - contextFile and tomcatUsers defined in pom.xml are not used with target tomcat7:run * [MTOMCAT-144] - resourcePaths returns null * [MTOMCAT-145] - [2.0-beta-1] Unable to deploy * [MTOMCAT-149] - Error deploying on Tomcat 6 * [MTOMCAT-151] - Empty password prevents preemptive authentication headers from being sent * [MTOMCAT-157] - use new Maven Plugins annotations * [MTOMCAT-160] - "Skipping non-war project" should not happen if using * [MTOMCAT-162] - SaxException when deploying multiple WARs * [MTOMCAT-166] - Cannot invoke Tomcat manager:Cannot retry request with a non-repeatable request entity * [MTOMCAT-169] - Unable to Deploy WAR Defined via "webapps" Declaration * [MTOMCAT-170] - Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration * [MTOMCAT-171] - Multiple executions (i.e. sep tomcats clash due to identical JMX naming) * [MTOMCAT-172] - configuring aliases with tomcat7:run ** Improvement * [MTOMCAT-60] - Multiple-War-Deployment in configuration section. * [MTOMCAT-120] - Support "skip" parameter * [MTOMCAT-122] - add all plugin dependencies to the tomcat class loader * [MTOMCAT-124] - tomcat-maven-archetype unused generation parameters * [MTOMCAT-137] - Adding a static context to tomcat for static files like images, js, html etc. * [MTOMCAT-140] - Allow specifying the classloader to use for loading webapps. * [MTOMCAT-147] - Add help goal * [MTOMCAT-150] - expose ports used with tomcat7:run as sys props * [MTOMCAT-153] - align all Maven dependency versions to 2.0.11 * [MTOMCAT-154] - support exec-war war run dependencies with classifiers * [MTOMCAT-155] - allow exec-war war run dependencies that are generated in current mvn execution, but not yet installed to maven repo * [MTOMCAT-156] - exec-war should allow creation of exec-war in projects with any packaging type * [MTOMCAT-164] - Add french translation * [MTOMCAT-167] - Add the ability to specify context.xml files for each additional Webapp being deployed ** New Feature * [MTOMCAT-126] - Add support for keystoreType ** Task * [MTOMCAT-174] - tomcatConfigurationFilesDirectory is not implemented Have Fun, -- The Apache Tomcat Team. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin 2.0-SNAPSHOT:deploy ignores server configuration
vote started see: http://markmail.org/message/ewcp3ukbcoogtswh 2012/9/12 Gert van Spijker : > On 11/09/12 20:34, Olivier Lamy wrote: >> Hi, >> >> Some issues has been fixed regarding that. >> Is there any logs on server side. >> Did you try a recent snapshot or build yourself ? > > No, I didn't. > But I googled a bit more and found this: > > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html > I added the repositories as described and tested. > The current snapshot does indeed solve the problem. > > Thanks. > > This seems like a fairly fundamental issue. Are the main stream > repositories going to be updated soon? Or would it otherwise be a good > idea to make a note about this in the documentation? > > Gert > > >> >> >> 2012/9/11 Gert van Spijker : >>> Hi, >>> >>> If this is not the correct list to ask about the Tomcat Maven plugins >>> then I apologize in advance. I have been googiling for better places, >>> but to no avail. >>> >>> I have a Maven Web application project and am trying to deploy to a >>> local Tomcat 7 server on http://localhost:8080. I can access this server >>> with my browser and deploy the web app manually. I also set the correct >>> credentials in the maven settings.xml configuration file. >>> >>> I follow the documentation about the tomcat7:deploy goal: >>> >>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/deploy-mojo.html >>> >>> Although the server is running on the plugin's default URL I get a 403 >>> HTTP error. I have tried to add the ".text" using the parameter, >>> but this is completely ignored (I can see in the plugin output that it >>> always uses the default URL) >>> >>> I also set the parameter to match the id in mavens settings.xml >>> but the behavior does not change. >>> >>> It seems that tomcat7-maven-plugin 2.0-SNAPSHOT ignores its parameters. >>> >>> Or am I doing something wrong? >>> >>> Gert >>> >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> >> > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin 2.0-SNAPSHOT:deploy ignores server configuration
Hi, Some issues has been fixed regarding that. Is there any logs on server side. Did you try a recent snapshot or build yourself ? 2012/9/11 Gert van Spijker : > Hi, > > If this is not the correct list to ask about the Tomcat Maven plugins > then I apologize in advance. I have been googiling for better places, > but to no avail. > > I have a Maven Web application project and am trying to deploy to a > local Tomcat 7 server on http://localhost:8080. I can access this server > with my browser and deploy the web app manually. I also set the correct > credentials in the maven settings.xml configuration file. > > I follow the documentation about the tomcat7:deploy goal: > > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/deploy-mojo.html > > Although the server is running on the plugin's default URL I get a 403 > HTTP error. I have tried to add the ".text" using the parameter, > but this is completely ignored (I can see in the plugin output that it > always uses the default URL) > > I also set the parameter to match the id in mavens settings.xml > but the behavior does not change. > > It seems that tomcat7-maven-plugin 2.0-SNAPSHOT ignores its parameters. > > Or am I doing something wrong? > > Gert > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Maven Plugin - Executable jar context loading and shutdown
A bit weird.
Can you have a look at this project which works fine with empty path
https://github.com/olamy/tomcat-foo-artifact
2012/9/4 Sérgio Areias :
> On 4 September 2012 09:26, Olivier Lamy wrote:
>>
>> 2012/9/3 Sérgio Areias :
>> > Hi.
>> >
>> > On 31 August 2012 21:24, Olivier Lamy wrote:
>> >
>> >> 2012/8/27 Sérgio :
>> >> > Hi.
>> >> >
>> >> > I am trying to use the Tomcat Maven Plugin to create an executable jar
>> >> file
>> >> > with an embedded Tomcat7, but I am having two issues when trying to do
>> >> so.
>> >> >
>> >> > The first one, is that I am not getting how I can stop my executable
>> >> jar. I
>> >> > want to run it in from a script (like the shutdown.sh/bat from tomcat).
>> >> I
>> >> > was not able to find any documentation about that particular issue.
>> >> nope not supported.
>> >>
>> > Can you give me some pointers of where I should look at if I decide to
>> > implement it? I could kill the process but that does not look a solution
>> > but a workaround instead.
>> >
>> >
>> >> >
>> >> > The second issue, is that when I run my executable jar it loads my
>> >> > webapp
>> >> > context twice (it tries because it will not be able to do it as I use a
>> >> > derby db, and it will give an error when trying to have the lock again).
>> >> It
>> >> > creates a folder .extract, and the webapp works fine, but I do not want
>> >> my
>> >> > context to be loaded twice. I am using the configurations I have found
>> >> here
>> >> > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html .
>> >> >
>> >> > What am I missing here?
>> >> Do you have a sample project as I cannot reproduce.
>> >> What is the content of .extract/webapps
>> >>
>> >> Did you try java- jar pathtoyourjar -resetExtract (or cleanup .extract
>> >> directory before) ?
>> >>
>> >
>> > After taking a look to the plugin source code, I understood that I cannot
>> > use "/" as context, and that is why I was having the context loaded twice
>> > (ROOT and .war). Is it supported by the plugin to have a webapp running
>> > with no context when trying to have an executable jar? I ask this question
>> > because when I try to use ROOT (/ROOT), I do not have the "/"
>> > context but "/ROOT" instead.
>> > (Also after studying the lines 264-272 from
>> > http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java?view=markup
>> > )
>>
>> Did you simply try:
>> :-)
>>
> I have tried now, and the context was set to the artifact id. I also
> took a look to the source code and I think that it is the expected
> behaviour (defaultValue = "${project.artifactId}").
>
> Well, after a few more tests I found new info about my problem.
> I was trying to use my server.xml file, when I remove it everything
> works fine (except one thing but I will address it later on this
> mail), even with "/" as context (does not seem valid following line
> 107 of the AbstractExecWarMojo class but it is working). When I try to
> use the server.xml it loads the context twice. Why that happens, I do
> not know yet.
>
> I really do not need my custom server.xml, but when I do not use it
> the configuration 50001 in my pom.xml is not reflected
> when I try to run the jar. It runs always in the port 8080 without my
> server.xml.
>
> NOTE: I have attached my server.xml.
>
> Thanks for your attention and sorry for the taken time.
> Best regards,
> Sérgio Areias
>
>>
>> >
>> >
>> >> >
>> >> > Info about the project:
>> >> > - Maven project;
>> >> > - pom.xml with packaging war using the build found here
>> >> > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html ;
>> >> > - Running in Ubuntu 11.04;
>> >> > - Using: org.apache.tomcat.maven
>> >> > tomcat7-maven-plugin
>> >> > 2.0-beta-1
>> >> >
>> >> > Thanks in advance.
>> >> >
>> >> > Best regards,
>> >> > Sérgio Areias
>> >>
>> >> --
&g
Re: Tomcat Maven Plugin - Executable jar context loading and shutdown
2012/9/3 Sérgio Areias : > Hi. > > On 31 August 2012 21:24, Olivier Lamy wrote: > >> 2012/8/27 Sérgio : >> > Hi. >> > >> > I am trying to use the Tomcat Maven Plugin to create an executable jar >> file >> > with an embedded Tomcat7, but I am having two issues when trying to do >> so. >> > >> > The first one, is that I am not getting how I can stop my executable >> jar. I >> > want to run it in from a script (like the shutdown.sh/bat from tomcat). >> I >> > was not able to find any documentation about that particular issue. >> nope not supported. >> > Can you give me some pointers of where I should look at if I decide to > implement it? I could kill the process but that does not look a solution > but a workaround instead. > > >> > >> > The second issue, is that when I run my executable jar it loads my webapp >> > context twice (it tries because it will not be able to do it as I use a >> > derby db, and it will give an error when trying to have the lock again). >> It >> > creates a folder .extract, and the webapp works fine, but I do not want >> my >> > context to be loaded twice. I am using the configurations I have found >> here >> > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html . >> > >> > What am I missing here? >> Do you have a sample project as I cannot reproduce. >> What is the content of .extract/webapps >> >> Did you try java- jar pathtoyourjar -resetExtract (or cleanup .extract >> directory before) ? >> > > After taking a look to the plugin source code, I understood that I cannot > use "/" as context, and that is why I was having the context loaded twice > (ROOT and .war). Is it supported by the plugin to have a webapp running > with no context when trying to have an executable jar? I ask this question > because when I try to use ROOT (/ROOT), I do not have the "/" > context but "/ROOT" instead. > (Also after studying the lines 264-272 from > http://svn.apache.org/viewvc/tomcat/maven-plugin/trunk/tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/run/AbstractExecWarMojo.java?view=markup > ) Did you simply try: :-) > > >> > >> > Info about the project: >> > - Maven project; >> > - pom.xml with packaging war using the build found here >> > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html ; >> > - Running in Ubuntu 11.04; >> > - Using: org.apache.tomcat.maven >> > tomcat7-maven-plugin >> > 2.0-beta-1 >> > >> > Thanks in advance. >> > >> > Best regards, >> > Sérgio Areias >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > Thanks for you reply and your attention. > Best regards, > Sérgio Areias -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Maven Plugin - Executable jar context loading and shutdown
2012/8/27 Sérgio : > Hi. > > I am trying to use the Tomcat Maven Plugin to create an executable jar file > with an embedded Tomcat7, but I am having two issues when trying to do so. > > The first one, is that I am not getting how I can stop my executable jar. I > want to run it in from a script (like the shutdown.sh/bat from tomcat). I > was not able to find any documentation about that particular issue. nope not supported. > > The second issue, is that when I run my executable jar it loads my webapp > context twice (it tries because it will not be able to do it as I use a > derby db, and it will give an error when trying to have the lock again). It > creates a folder .extract, and the webapp works fine, but I do not want my > context to be loaded twice. I am using the configurations I have found here > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html . > > What am I missing here? Do you have a sample project as I cannot reproduce. What is the content of .extract/webapps Did you try java- jar pathtoyourjar -resetExtract (or cleanup .extract directory before) ? > > Info about the project: > - Maven project; > - pom.xml with packaging war using the build found here > http://tomcat.apache.org/maven-plugin-2/executable-war-jar.html ; > - Running in Ubuntu 11.04; > - Using: org.apache.tomcat.maven > tomcat7-maven-plugin > 2.0-beta-1 > > Thanks in advance. > > Best regards, > Sérgio Areias -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin doesn't understand Maven filtering of context files?
2012/8/30 Knute Snortum :
> See below:
>
>> -Original Message-
>> From: Knute Snortum [mailto:ksnor...@catalystitservices.com]
>> Sent: Wednesday, August 29, 2012 3:05 PM
>> To: Tomcat Users List
>> Subject: RE: tomcat7-maven-plugin doesn't understand Maven filtering of
>> context files?
>>
>>
>>
>> > -Original Message-
>> > From: Olivier Lamy [mailto:ol...@apache.org]
>> > Sent: Wednesday, August 29, 2012 9:32 AM
>> > To: Tomcat Users List
>> > Subject: Re: tomcat7-maven-plugin doesn't understand Maven filtering
>> > of context files?
>>
>> [section deleted]
>>
>> > >
>> > >> What cli are you using ?
>> > >
>> > > If I understand you, it's this:
>> > >
>> > > mvn clean install tomcat:run -P development
>> > >
>> > > I'm making that up because it's actually run from an Eclipse form.
>> > When I run that from the command line in the project folder, I get the
>> > same results so I think it's right...
>> > >
>> > > I just noticed that the CLI should be:
>> > >
>> > > mvn clean install tomcat7:run -P development
>> > >
>> > > ...with "tomcat7" not "tomcat". This gives me the Tomcat 2.0-beta-1
>> > version that we were excepting. I also notice the debug flag (-e?)
>> > and that gives me a ton of info. Should I repost the output, or some
>> of it?
>> > Add as an attachment?
>> > Regarding the flag have a look at what mvn -h says :-) (-X is for full
>> > debug trace)
>> > >
>> > Maybe in a jira issue yes but not sure that will help
>> > >> BTW do you have any sample project to reproduce your issue ?
>> > >
>> > > It would be complex to do this, but I'm going to try. I'm not sure
>> > how I would post that.
>> > Just share a project via bitbucket or github.
>
> Is there anything else I should do? I don't want to report this as a bug if
> it's working as designed. But I was hoping I wouldn't have to setup my own,
> private Tomcat server to do development.
Thanks for the project that helps me to understand your problem :-)
The filtering here is done by the maven-war-plugin so the tomcat7
doesn't have any idea of that !
The plugin use warSourceDirectory
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#warSourceDirectory
So by default web.xml is src/main/webapp/WEB-INF/web.xml and the file
is not filtered
In your case you can add
${project.build.directory}/${project.artifactId}-${project.version}
to the tomcat7 plugin configuration
and run: mvn clean install tomcat7:run
and it looks it works no more debug mode and it will use the filtered file.
HTH
>
>> I created a test project in Github:
>>
>> https://github.com/ksnortum/Tomcat7MavenPluginTester
>>
>> It demonstrates what I believe is a bug in tomcat7-maven-plugin. The
>> Tomcat server that is created does not use the configuration files
>> (e.g.: web.xml) in the war file or the war directory that is created.
>> It uses the "project" files, that is, the ones in src/main/webapp/WEB-
>> INF. If you use Maven web resource filtering, the war file is changed
>> but the "project" file isn't. This is correct. But if tomcat7-maven-
>> plugin doesn't use the war configuration files, then how can you
>> properly test the war file?
>>
>>
>> > >
>> > >
>> > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > > For additional commands, e-mail: users-h...@tomcat.apache.org
>> > >
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> > For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin doesn't understand Maven filtering of context files?
2012/8/29 Knute Snortum :
> [part of message deleted]
>
>> >> > [INFO]
>> >> > [INFO] >>> tomcat-maven-plugin:1.1:run (default-cli) @ dpt >>>
>> >>
>> >> you are using an old version here ? Don't you have duplicate entries
>> >> in your pom ?
>> >
>> > There's no duplicate. The one I have looks like this:
>> >
>> >
>> > org.apache.tomcat.maven
>> > tomcat7-maven-plugin
>> > ${tomcat7MavenPlugin}
>> > ...
>> >
>> > And my properties look like:
>> >
>> > 2.0-beta-1
>> >
>> Ok but the logs doesn't says that :-)
>
> True. I'm not sure why. I'll fool with it some.
>
>> What cli are you using ?
>
> If I understand you, it's this:
>
> mvn clean install tomcat:run -P development
>
> I'm making that up because it's actually run from an Eclipse form. When I
> run that from the command line in the project folder, I get the same results
> so I think it's right...
>
> I just noticed that the CLI should be:
>
> mvn clean install tomcat7:run -P development
>
> ...with "tomcat7" not "tomcat". This gives me the Tomcat 2.0-beta-1 version
> that we were excepting. I also notice the debug flag (-e?) and that gives me
> a ton of info. Should I repost the output, or some of it? Add as an
> attachment?
Regarding the flag have a look at what mvn -h says :-) (-X is for full
debug trace)
>
Maybe in a jira issue yes but not sure that will help
>> BTW do you have any sample project to reproduce your issue ?
>
> It would be complex to do this, but I'm going to try. I'm not sure how I
> would post that.
Just share a project via bitbucket or github.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin doesn't understand Maven filtering of context files?
2012/8/29 Knute Snortum :
>
>
>> -Original Message-----
>> From: Olivier Lamy [mailto:ol...@apache.org]
>> Sent: Tuesday, August 28, 2012 2:17 PM
>> To: Tomcat Users List
>> Subject: Re: tomcat7-maven-plugin doesn't understand Maven filtering of
>> context files?
>>
>> Hi,
>> Inline
>>
>> 2012/8/28 Knute Snortum :
>> > If this is the wrong mailing list for tomcat7-maven-plugin, could
>> someone direct me to the right place?
>> >
>> > I'm developing a Vaadin web app in Eclipse Juno on Windows 7 and I'm
>> using the tomcat7-maven-plugin 2.0-beta-1 to help in development by
>> running the app in Tomcat inside of the IDE -- or I'm trying. The error
>> I'm getting is:
>> >
>> > org.springframework.beans.factory.BeanDefinitionStoreException:
>> > Invalid bean definition with name 'dataSource' defined in
>> > ServletContext resource [/WEB-INF/applicationContext.xml]: Could not
>> > resolve placeholder 'db.driverClassName' in string value
>> > [${db.driverClassName}]
>> >
>> > "applicationContext.xml" is my Spring context file. I have
>> placeholders in it to point to the correct database based on Maven
>> profiles and filtering. So a piece of applicationContext.xml looks like
>> this:
>> >
>> > > class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
>> > > value="${db.driverClassName}" />
>> >
>> > > value="${db.username}" />
>> > > value="${db.password}" />
>> >
>> >
>> >
>> >
>> > As you can see, Tomcat (or Spring?) is finding the dataSource bean
>> that does not have the placeholders replaced yet.
>> >
>> > The odd thing is that in the war file and the directory under target
>> that the war file is created from, all the place holders have been
>> correctly substituted. I can see them in an editor. The context file
>> with the placeholders is the one still sitting in my development folder.
>> >
>> > So my question is, why isn't the Tomcat plugin seeing the context file
>> in the war file or folder? And if it looks in the development folder
>> for the file, can Maven filtering work with the plugin?.
>> >
>> as you are using gwt maven plugin, I'm not sure that works.
>> Something you can do is using sys properties in tomcat7/6-maven-plugin
>> (spring placeholder resolves against sys props too).
>> Add you sys props as it:
>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-
>> plugin/examples/add-system-properties.html
>
> Well, I'm using Maven filtering, and the reason for that is my client
> requires that I use Maven profiling to set the development and the production
> environments. So I'd have to a Maven Tomcat plugin in each profile -- which
> maybe I'll do.
>
> I need the GWT plugin because this is a Vaadin project and Vaadin uses GWT.
>
>> > Below is part of the messages created by Maven et al in my IDE
>> console. I've left out the clean and testing messages and most of the
>> stacktrace, which I think is from Spring anyway:
>> >
>> > [INFO]
>> > [INFO] --- gwt-maven-plugin:2.4.0:compile (default) @ dpt --- [INFO]
>> > auto discovered modules
>> > [com.catalystitservices.nike.dpt.widgetset.DptWidgetset]
>> > [INFO] com.catalystitservices.nike.dpt.widgetset.DptWidgetset is up to
>> > date. GWT compilation skipped [INFO] [INFO] ---
>> > maven-war-plugin:2.2:war (default-war) @ dpt --- [INFO] Packaging
>> > webapp [INFO] Assembling webapp [dpt] in [C:\Projects\DPT\target\dpt]
>> > [INFO] Processing war project [INFO] Copying webapp webResources
>> > [C:\Projects\DPT\src/main/webapp/] to [C:\Projects\DPT\target\dpt]
>> > [INFO] Copying webapp resources [C:\Projects\DPT\src\main\webapp]
>> > [INFO] Webapp assembled in [1442 msecs] [INFO] Building war:
>> > C:\Projects\DPT\target\dpt.war [INFO] [INFO] ---
>> > tomcat7-maven-plugin:2.0-beta-1:exec-war-only (tomcat-run) @ dpt ---
>> > [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install)
>> > @ dpt --- [INFO] Installing C:\Projects\DPT\target\dpt.war to
>> > C:\Users\ksnortum\.m2\repository\com\nike\dpt\dpt\1.1-SNAPSHOT\dpt-1.1
>> > -SNAPSHOT.war [INFO] Installing C:\Projects\DPT\pom.xml to
&
Re: tomcat7-maven-plugin doesn't understand Maven filtering of context files?
andardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 > Aug 28, 2012 10:14:00 AM org.apache.catalina.core.ApplicationContext log > INFO: Set web app root system property: 'webapp.root' = > [C:\Projects\DPT\src\main\webapp\] > Aug 28, 2012 10:14:00 AM org.apache.catalina.core.ApplicationContext log > INFO: Initializing log4j from [classpath:log4j.properties] > Aug 28, 2012 10:14:00 AM org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > 28.08.2012 10:14:00 INFO (ContextLoader.java:272) - Root > WebApplicationContext: initialization started > 28.08.2012 10:14:00 INFO (AbstractApplicationContext.java:500) - Refreshing > Root WebApplicationContext: startup date [Tue Aug 28 10:14:00 PDT 2012]; root > of context hierarchy > 28.08.2012 10:14:00 INFO (XmlBeanDefinitionReader.java:315) - Loading XML > bean definitions from ServletContext resource > [/WEB-INF/applicationContext.xml] > 28.08.2012 10:14:01 INFO (XmlBeanDefinitionReader.java:315) - Loading XML > bean definitions from ServletContext resource > [/WEB-INF/applicationContext-security.xml] > 28.08.2012 10:14:01 INFO (SpringSecurityCoreVersion.java:33) - You are > running with Spring Security Core 3.1.0.RELEASE > 28.08.2012 10:14:01 INFO (SecurityNamespaceHandler.java:57) - Spring > Security 'config' module version is 3.1.0.RELEASE > 28.08.2012 10:14:01 INFO (HttpSecurityBeanDefinitionParser.java:229) - > Checking sorted filter chain: [Root bean: class > [org.springframework.security.web.context.SecurityContextPersistenceFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 300, Root bean: class > [org.springframework.security.web.authentication.logout.LogoutFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 400, > , > order = 800, Root bean: class > [org.springframework.security.web.authentication.www.BasicAuthenticationFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1200, Root bean: class > [org.springframework.security.web.savedrequest.RequestCacheAwareFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1300, Root bean: class > [org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1400, Root bean: class > [org.springframework.security.web.authentication.AnonymousAuthenticationFilter]; > scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1700, Root bean: class > [org.springframework.security.web.session.SessionManagementFilter]; scope=; > abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1800, Root bean: class > [org.springframework.security.web.access.ExceptionTranslationFilter]; scope=; > abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0; > autowireCandidate=true; primary=false; factoryBeanName=null; > factoryMethodName=null; initMethodName=null; destroyMethodName=null, order = > 1900, > , > order = 2000] > 28.08.2012 10:14:01 INFO (PropertiesLoaderSupport.java:177) - Loading > properties file from file [C:\Projects\DPT\target\classes\log4j.properties] > 28.08.2012 10:14:01 INFO (DefaultSingletonBeanRegistry.java:433) - > Destroying singletons in > org.springframework.beans.factory.support.DefaultListableBeanFactory@378c3efb: > defining beans > [org.springframework.context.support.PropertySourcesPlaceholderConfigurer#0, list of beans removed>]; root of factory hierarchy > 28.08.2012 10:14:01 ERROR (ContextLoader.java:307) - Context initialization >
Re: tomcat maven plugin + configuring virtual host for the embedded tomcat ?
documentation added here: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#aliases 2012/7/31 Albert Kam : > Sorry, forgot to mention a suggestion to document this feature in : > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/run-mojo-features.html > > Regards, > Albert > > On Tue, Jul 31, 2012 at 4:01 PM, Albert Kam wrote: >> Wow, so fast ! It worked flawlessly : >> >> After adding this in the tomcat maven plugin's configuration .. >> >> mydomain1.com >> mydomain2.com >> >> >> These work with tomcat7:run : >> http://localhost:8080 >> http://mydomain1.com:8080 >> http://mydomain2.com:8080 >> >> Bye2 tomcat:deploy ! >> >> Thanks ! >> >> On Tue, Jul 31, 2012 at 3:19 PM, Olivier Lamy wrote: >>> Try last SNAPSHOT (see how here: >>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html >>> ) >>> >>> If any issue using this new feature, feel free to reopen: >>> https://issues.apache.org/jira/browse/MTOMCAT-172 >>> >>> HTH, >>> -- >>> Olivier >>> >>> 2012/7/31 Albert Kam : >>>> Hi, >>>> >>>> I have been developing with tomcat7:run happily for some months now. >>>> >>>> But then i am currently expanding the development where different >>>> domains would provide different behaviour for the same webapp (imagine >>>> multitenancy and ACLs based on the domain or the server name) >>>> >>>> To make this work in the development mode, >>>> i would have to modify the hosts file, mapping several .com domains to >>>> localhost + add some to the localhost's >>>> >>>> Currently i am using the standalone tomcat, doing : >>>> - go to the parent module, install all modules, which results in the >>>> newest WAR for the webapp >>>> - go to the webapp project and tomcat7:deploy to it .. >>>> >>>> Not as fast-development-mode as tomcat7:run (which doesnt include >>>> installing the modules + WAR building), but this will do :-) >>>> >>>> I may be too hopeful, but is this useful enough to be added as a new >>>> feature of tomcat maven plugin ? >>>> I imagine putting these aliases in the plugin's configuration in the >>>> pom.xml .. >>>> >>>> Thanks ! >>>> >>>> On Tue, Jul 31, 2012 at 12:54 AM, Olivier Lamy wrote: >>>>> Hi, >>>>> Not possible currently. >>>>> What is your use case ? those goals are for dev purpose. >>>>> >>>>> 2012/7/27 Albert Kam : >>>>>> I am currently using the snapshot version of tomcat maven plugin. >>>>>> And i am using tomcat7:run and tomcat7:run-war-only (for webapps with >>>>>> overlay) actively. >>>>>> >>>>>> And the time has come for me to try out virtual host .. and as i >>>>>> understand it, i have to configure the host, context, etc .. >>>>>> But i've been using the embedded tomcat 'supplied' by the tomcat maven >>>>>> plugin so far, >>>>>> >>>>>> so i wonder if there's a way to configure virtual host on the embedded >>>>>> tomcat ? >>>>>> >>>>>> Or should i just forget embedded tomcat and setup an independent >>>>>> tomcat i can configure freely ? >>>>>> >>>>>> Thank you, >>>>>> Albert >>>>>> >>>>>> -- >>>>>> Do not pursue the past. Do not lose yourself in the future. >>>>>> The past no longer is. The future has not yet come. >>>>>> Looking deeply at life as it is in the very here and now, >>>>>> the practitioner dwells in stability and freedom. >>>>>> (Thich Nhat Hanh) >>>>>> >>>>>> - >>>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>>>>> For additional commands, e-mail: users-h...@tomcat.apache.org >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Olivier Lamy >>>>> Talend: http://coders.talend.com >>>>> http://twitter.com/olamy | http://linkedin.com/in/ola
Re: tomcat maven plugin + configuring virtual host for the embedded tomcat ?
Try last SNAPSHOT (see how here: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html ) If any issue using this new feature, feel free to reopen: https://issues.apache.org/jira/browse/MTOMCAT-172 HTH, -- Olivier 2012/7/31 Albert Kam : > Hi, > > I have been developing with tomcat7:run happily for some months now. > > But then i am currently expanding the development where different > domains would provide different behaviour for the same webapp (imagine > multitenancy and ACLs based on the domain or the server name) > > To make this work in the development mode, > i would have to modify the hosts file, mapping several .com domains to > localhost + add some to the localhost's > > Currently i am using the standalone tomcat, doing : > - go to the parent module, install all modules, which results in the > newest WAR for the webapp > - go to the webapp project and tomcat7:deploy to it .. > > Not as fast-development-mode as tomcat7:run (which doesnt include > installing the modules + WAR building), but this will do :-) > > I may be too hopeful, but is this useful enough to be added as a new > feature of tomcat maven plugin ? > I imagine putting these aliases in the plugin's configuration in the pom.xml > .. > > Thanks ! > > On Tue, Jul 31, 2012 at 12:54 AM, Olivier Lamy wrote: >> Hi, >> Not possible currently. >> What is your use case ? those goals are for dev purpose. >> >> 2012/7/27 Albert Kam : >>> I am currently using the snapshot version of tomcat maven plugin. >>> And i am using tomcat7:run and tomcat7:run-war-only (for webapps with >>> overlay) actively. >>> >>> And the time has come for me to try out virtual host .. and as i >>> understand it, i have to configure the host, context, etc .. >>> But i've been using the embedded tomcat 'supplied' by the tomcat maven >>> plugin so far, >>> >>> so i wonder if there's a way to configure virtual host on the embedded >>> tomcat ? >>> >>> Or should i just forget embedded tomcat and setup an independent >>> tomcat i can configure freely ? >>> >>> Thank you, >>> Albert >>> >>> -- >>> Do not pursue the past. Do not lose yourself in the future. >>> The past no longer is. The future has not yet come. >>> Looking deeply at life as it is in the very here and now, >>> the practitioner dwells in stability and freedom. >>> (Thich Nhat Hanh) >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > > -- > Do not pursue the past. Do not lose yourself in the future. > The past no longer is. The future has not yet come. > Looking deeply at life as it is in the very here and now, > the practitioner dwells in stability and freedom. > (Thich Nhat Hanh) > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat maven plugin + [default] overlay
2012/7/26 Albert Kam :
> Hello,
>
> I am having a situation where i couldnt tomcat7:run with overlay in eclipse.
> In the eclipse indigo, i am using the maven plugin, and have imported
> two maven modules,
> the childwebapp which depends on the parentwebapp, which is just like
> a skeleton, with it's own classes, jsps, static resources, but also a
> runnable webapp of itself.
> Doing tomcat7:run on the parentwebapp works well as expected ..
>
> Here's the dependency in the childwebapp's pom, and i dont have any
> specific overlay configuration :
>
> group.id
> parentwebapp
> ${project.version}
> war
> runtime
>
This dependency is a reactor modules ? So in this case I presume
eclipse (m2e) see the build output directory rather than a war file.
The plugin doesn't have any idea how your war dependency is available
in an exploded mode (where are the webapp resources and/or classes
etc..)
try to install it first.
>
> When i try running tomcat7:run on the childwebapp, i get this error message,
> as if it tries to find the war of parentwebapp and try to extract it.
> But in my situation, i dont have the war in my development,
> since the eclipse maven plugin already resolves the workspace dependencies.
> I would imagine using the classes from the workspace instead of
> extracting the non-existent war file and load them into the
> childwebapp would solve the issue ..
>
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources)
> @ childwebapp ---
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> childwebapp ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] <<< tomcat7-maven-plugin:2.0-SNAPSHOT:run (default-cli) @ childwebapp
> <<<
> [INFO]
> [INFO] --- tomcat7-maven-plugin:2.0-SNAPSHOT:run (default-cli) @ childwebapp
> ---
> [INFO] Running war on http://localhost:8080/childwebapp
> [INFO] Creating Tomcat server configuration at
> C:\Users\albert\git\Startup\MavenParent\childwebapp\target\tomcat
> [INFO] create webapp with contextPath: /childwebapp
> [ERROR] fail to extract war file
> C:\Users\albert\git\Startup\MavenParent\parentwebapp\target\classes,
> reason:The source must not be a di
> rectory.
> org.codehaus.plexus.archiver.ArchiverException: The source must not be
> a directory.
> at
> org.codehaus.plexus.archiver.AbstractUnArchiver.validate(AbstractUnArchiver.java:185)
> at
> org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:118)
> at
> org.apache.tomcat.maven.common.run.DefaultClassLoaderEntriesCalculator.calculateClassPathEntries(DefaultClassLoaderEntriesCalc
> ulator.java:149)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.RunMojo.createWebappLoader(RunMojo.java:254)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.createContext(AbstractRunMojo.java:563)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:927)
> at
> org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:476)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> What can i do to resolve this situation ?
>
> Thank you,
> Albert
>
> --
> Do not pursue the past. Do not lose yourself in the future.
> The past no longer is. The future has not yet come.
> Looking deeply at life as it is in the very here and now,
> the practitioner dwells in stability and freedom.
> (Thich Nhat Hanh)
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat maven plugin + configuring virtual host for the embedded tomcat ?
Hi, Not possible currently. What is your use case ? those goals are for dev purpose. 2012/7/27 Albert Kam : > I am currently using the snapshot version of tomcat maven plugin. > And i am using tomcat7:run and tomcat7:run-war-only (for webapps with > overlay) actively. > > And the time has come for me to try out virtual host .. and as i > understand it, i have to configure the host, context, etc .. > But i've been using the embedded tomcat 'supplied' by the tomcat maven > plugin so far, > > so i wonder if there's a way to configure virtual host on the embedded tomcat > ? > > Or should i just forget embedded tomcat and setup an independent > tomcat i can configure freely ? > > Thank you, > Albert > > -- > Do not pursue the past. Do not lose yourself in the future. > The past no longer is. The future has not yet come. > Looking deeply at life as it is in the very here and now, > the practitioner dwells in stability and freedom. > (Thich Nhat Hanh) > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: confused by tomcat6/7 docs
Hi,
2012/7/8 Russ Tremain :
> ahh... thanks. bad assumption on my part that tomcat7-maven was a superset.
>
> what would really be cool is an "incremental" deploy, but not sure if the
> tomcat remote deploy api supports that or not.
with incremental you mean for classes too ? or for jsp,css, jss etc.. ?
>
> meantime I will see if we can revert to tomcat6-maven plugin to see if we can
> speed the build/deploy development cycle up.
>
> thx,
> /r
>
> At 10:16 PM +0200 7/7/12, Olivier Lamy wrote:
>>Yup because currently not all goals from tomcat6 have been implemented
>>in tomcat7.
>>
>>http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
>>whereas.
>>http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
>>
>>You can load an issue (if possible with a patch :-) ) for goals you'd like
>>see.
>>
>>2012/7/6 Russ Tremain :
>>> Hi Oliver,
>>>
>>> I must say I'm a bit confused by the examples & docs for
>>> tomcat7-maven-plugin.
>>>
>>> I see reference to a "war:explode" goal, which doesn't seem to exist. The
>>> reference is here:
>>>
>>> http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
>>>
>>> But when I dump the plugin documentation [1], I see no such goal.
>>>
>>> What I would like to find out about the possibility to deploy an exploded
>>> war image to a local tomcat instance.
>>>
>>> I've been successfully using the deploy (tomcat7:deploy) goal, but my
>>> developers are complaining that it is too slow. I need to work out a method
>>> to use an exploded war.
>>>
>>> Any help appreciated...
>>>
>>> thanks!
>>> -Russ
>>>
>>> [1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
>>> help:describe
>>> ...
>>> [INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
>>>
>>> Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
>>> Description: The Tomcat Maven Plugin provides goals to manipulate WAR
>>> projects within the Tomcat 7.x servlet container.
>>> Group Id: org.apache.tomcat.maven
>>> Artifact Id: tomcat7-maven-plugin
>>> Version: 2.0-beta-1
>>> Goal Prefix: tomcat7
>>>
>>> This plugin has 8 goals:
>>>
>>> tomcat7:deploy
>>> Description: Deploy a WAR to Tomcat.
>>> Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
>>> Language: java
>>> Before this mojo executes, it will call:
>>> Phase: 'package'
>>>
>>> Available parameters:
>>>
>>> charset (Default: ISO-8859-1)
>>> The URL encoding charset to use when communicating with Tomcat
>>> manager.
>>>
>>> contextFile
>>> The path of the Tomcat context XML file. This is not used for war
>>> deployment mode.
>>>
>>> ignorePackaging (Default: false)
>>> If set to true ignore if packaging of project is not 'war'.
>>>
>>> mode (Default: war)
>>> The deployment mode to use. This must be either war to deploy the war,
>>> context to deploy the context XML file, or both to deploy the war with
>>> the context XML file.
>>>
>>> password
>>> The password to use for deployment
>>>
>>> path (Default: /${project.artifactId})
>>> The webapp context path to use for the web application being run. This
>>> must always start with a forward-slash ('/').
>>>
>>> server
>>> The server id in settings.xml to use when authenticating with Tomcat
>>> manager, or null to use defaults of username admin and no password.
>>>
>>> tag
>>> The Tomcat webapp tag name to use.
>>>
>>> update (Default: false)
>>> Whether Tomcat should automatically undeploy webapps that already
>>> exist
>>> when deploying.
>>>
>>> url (Default: http://localhost:8080/manager/html)
>>> The full URL of the Tomcat manager instance to use.
>>>
>>> username
>>> The tomcat username to use for deployment
>>>
>>> warFile
>>> The path of the WAR file to deploy.
>>>
>>> tomcat7:deploy-only
>>> Description: Deploy a
Re: confused by tomcat6/7 docs
Language: java
>
> Available parameters:
>
> addContextWarDependencies (Default: false)
> Will create a tomcat context for each dependencies of war type with
> 'scope' set to 'tomcat'. In other words, dependencies with:
> war
> tomcat
> To preserve backward compatibility it's false by default.
>
> additionalConfigFilesDir (Default: ${basedir}/src/main/tomcatconf)
> The directory contains additional configuration Files that copied in
> the
> Tomcat conf Directory.
>
> ajpPort (Default: 0)
> The AJP port to run the Tomcat server on. By default it's 0 this means
> won't be started. The ajp connector will be started only for value >
> 0.
>
> ajpProtocol (Default: org.apache.coyote.ajp.AjpProtocol)
> The AJP protocol to run the Tomcat server on. By default it's ajp.
> NOTE
> The ajp connector will be started only if ajpPort > 0. possible values
> are:
> - org.apache.coyote.ajp.AjpProtocol - new blocking Java connector that
> supports an executor
> - org.apache.coyote.ajp.AjpAprProtocol - the APR/native connector.
>
> configurationDir
> The directory to create the Tomcat server configuration under.
>
> contextFile
> The path of the Tomcat context XML file.
>
> contextReloadable (Default: false)
> Force context scanning if you don't use a context file with reloadable
> =
> 'true'. The other way to use contextReloadable is to add attribute
> reloadable = 'true' in your context file.
>
> fork (Default: false)
> Set this to true to allow Maven to continue to execute after invoking
> the
> run goal.
>
> httpsPort (Default: 0)
> The https port to run the Tomcat server on. By default it's 0 this
> means
> won't be started. The https connector will be started only for value >
> 0.
>
> ignorePackaging (Default: false)
> If set to true ignore if packaging of project is not 'war'.
>
> keystoreFile
> Override the default keystoreFile for the HTTPS connector (if enabled)
>
> keystorePass
> Override the default keystorePass for the HTTPS connector (if enabled)
>
> path (Default: /${project.artifactId})
> The webapp context path to use for the web application being run. This
> must always start with a forward-slash ('/').
>
> pluginArtifacts
> (no description available)
>
> port (Default: 8080)
> The port to run the Tomcat server on.
>
> protocol (Default: HTTP/1.1)
> The protocol to run the Tomcat server on. By default it's HTTP/1.1.
>
> serverXml
> server.xml to use Note if you use this you must configure in this file
> your webapp paths.
>
> systemProperties
> List of System properties to pass to the Tomcat Server.
>
> tomcatLoggingFile
> The path of the Tomcat logging configuration.
>
> tomcatUsers
> The path of the Tomcat users XML file.
>
> tomcatWebXml
> overriding the providing web.xml to run tomcat
>
> uriEncoding (Default: ISO-8859-1)
> The character encoding to use for decoding URIs.
>
> useNaming (Default: true)
> Enables or disables naming support for the embedded Tomcat server.
>
> Note: This setting is ignored if you provide a server.xml for your
> Tomcat. Instead please configure naming in the server.xml.
>
> useSeparateTomcatClassLoader (Default: false)
> if true a new classLoader separated from maven core will be created to
> start tomcat.
>
> warDirectory
> The path of the exploded WAR directory to run.
>
> tomcat7:shutdown
> Description: Shuts down all possibly started embedded tomcat servers. This
> will be automatically down through a shutdown hook or you may call this
> Mojo to shut them down explictly.
>
> By default the shutdown goal is not bound to any phase. For integration
> tests you might want to bind it to post-integration-test.
> Implementation: org.apache.tomcat.maven.plugin.tomcat7.run.ShutdownMojo
> Language: java
>
> Available parameters:
>
> path (Default: /${project.artifactId})
> The webapp context path to use for the web application being run. This
> must always start with a forward-slash ('/').
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Starting up Tomcat in debug mode with tomcat6:run
The most simple is to use mvnDebug (no need to add vm options all is already set in mvnDebug script). 2012/5/11 Henrique Ordine : > Hi everybody, > > I understand that to start up tomcat in debug mode I need to add the > following JVM options : > > -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n > > I'm using the Maven tomcat6:run plugin though to start up my application on > Tomcat. Does anyone know how I can set those JVM options for this plugin? > > Thanks in advance. > > -- > Henrique Ordine > > http://hordine.wordpress.com/ -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7:run with multi maven modules changes
2012/5/9 Albert Kam : > After the advices, i took a peek on the the eclipse maven run > configuration that i use to launch tomcat7:run, and i notice the > checkbox : "Resolve Workspace Artifacts". > Ticking that checkbox, and re-run the tomcat7:run works great now, > which can see the other modules' changes without rebuilding ! > > Thanks a lot, i feel i can begin my fire dance now ! > > Anyway, i just want to report something that may not be related with > this topic in case that'd be useful. > I have these warnings when starting up tomcat7:run : > > [INFO] Scanning for projects... > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa > che.snapshots.xml is invalid: end tag name must be the same as > start tag from line 56 (position: TEXT seen ...arset > ="utf-8">\n Ext.onReady(Sonatype.init);\n \n... @65:8) > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat7-maven-plugin\2.0-SNAPSHOT\maven-metadata-apa > che.snapshots.xml is invalid: end tag name must be the same as > start tag from line 56 (position: TEXT seen ...arset > ="utf-8">\n Ext.onReady(Sonatype.init);\n \n... @65:8) > [WARNING] The metadata > C:\Users\albert\.m2\repository\org\apache\tomcat\maven\tomcat-maven-plugin\2.0-SNAPSHOT\maven-metadata-apac > he.snapshots.xml is invalid: end tag name must be the same as > start tag from line 56 (position: TEXT seen ...arset= > "utf-8">\n Ext.onReady(Sonatype.init);\n \n... @65:8) > It looks you have bad metadata locally. Maybe a misconfigured repo manager. Delete files from C:\Users\albert\.m2\repository\org\apache\tomcat\maven\ to download all again. > > > > On Wed, May 9, 2012 at 1:45 AM, Jeff MAURY wrote: >> You need to write a M2E connector for a Maven MOJO that processes your >> projects files. I don't think this is the case for the tomcat7:run goal and >> it should work out of of the box in Eclipse. Just need to add a Maven lunch >> configuration with the proper goal. >> >> Regards >> Jeff >> >> >> On Tue, May 8, 2012 at 5:34 PM, Olivier Lamy wrote: >> >>> I imagine you use tomcat7:run "inside" eclipse. >>> Do that work outside eclipse ? >>> >>> Perso I don't have any issues as I use only command line and >>> furthermore I don't use eclipse :-). >>> I imagine there is some m2e connector to write >>> >>> 2012/5/8 Albert Kam : >>> > I notice that i have to repeat these steps so that tomcat7:run will >>> > see the newest stuffs from other maven modules : >>> > - rebuild all of my mvn modules (including my webapp module on which >>> > my tomcat7:run-ed, and other dependencies module) >>> > - clean my eclipse java project, rebuilding everything >>> > - tomcat7:run will then see the newest stuffs >>> > >>> > Note that i dont need to rebuild maven and eclipse project if i dont >>> > modify the webapp maven module, tomcat7 can automatically see the >>> > newest changes >>> > >>> > Ideally i would like to skip rebuilding everything in maven and then >>> > eclipse to see the newest changes in the other modules outside webapp >>> > module. >>> > >>> > Are there any tips to achieve this ? >>> > >>> > Thanks ! >>> > >>> > -- >>> > Do not pursue the past. Do not lose yourself in the future. >>> > The past no longer is. The future has not yet come. >>> > Looking deeply at life as it is in the very here and now, >>> > the practitioner dwells in stability and freedom. >>> > (Thich Nhat Hanh) >>> > >>> > - >>> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> > For additional commands, e-mail: users-h...@tomcat.apache.org >>> > >>> >>> >>> >>> -- >>> Olivier Lamy >>> Talend: http://coders.talend.com >>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >> >> >> -- >> Jeff MAURY >> >> >> "Legacy code" often differs from its suggested alt
Re: tomcat7:run with multi maven modules changes
I imagine you use tomcat7:run "inside" eclipse. Do that work outside eclipse ? Perso I don't have any issues as I use only command line and furthermore I don't use eclipse :-). I imagine there is some m2e connector to write 2012/5/8 Albert Kam : > I notice that i have to repeat these steps so that tomcat7:run will > see the newest stuffs from other maven modules : > - rebuild all of my mvn modules (including my webapp module on which > my tomcat7:run-ed, and other dependencies module) > - clean my eclipse java project, rebuilding everything > - tomcat7:run will then see the newest stuffs > > Note that i dont need to rebuild maven and eclipse project if i dont > modify the webapp maven module, tomcat7 can automatically see the > newest changes > > Ideally i would like to skip rebuilding everything in maven and then > eclipse to see the newest changes in the other modules outside webapp > module. > > Are there any tips to achieve this ? > > Thanks ! > > -- > Do not pursue the past. Do not lose yourself in the future. > The past no longer is. The future has not yet come. > Looking deeply at life as it is in the very here and now, > the practitioner dwells in stability and freedom. > (Thich Nhat Hanh) > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [tomcat maven plugin] configure vm options on embedded tomcat ?
2012/5/1 Albert Kam : > I have successfully launched an embedded tomcat as detailed in here : > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/adjust-embedded-tomcat-version.html > > But i wonder whether it is possible to fork and set the extra vm > arguments for the embedded tomcat launch ? We do not fork a new vm. Extra vm arguments must be set via MAVEN_OPTS. > I need to do it to supply javaagent argument because i am currently > using spring and aop. > > Regards, > Albert Kam > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Does Tomcat Maven plugin support WAR overlays ?
2012/4/30 Jeff MAURY : > I don't link the idea of having Maven adding some stuff except under > target. This will cause many many problems with people and SCM. > I don't get your second solution: how do you merge you temporary stuff and > src/main/webapp with a symlink ? extract (except WEB-INF/lib and WEB-INF/classes) the overlay way in /tmp/foo/ src/main/webapp/foo (a kind of symlink to to /tmp/foo) But I have to investigate how to do that with the tomcat embed api ( :-) ) > > Jeff > > > On Mon, Apr 30, 2012 at 4:52 PM, Olivier Lamy wrote: > >> 2012/4/30 Jeff MAURY : >> > Salut Olivier, >> > >> > I wanted to make sure I understand the goal properly. >> > Is the rationale for using src/main/webapp as the default docbase for >> > Tomcat to propagate modifications of files on the fly (JSP,...) without >> the >> > need to restart Tomcat ? >> Yup that's the goal. Fast dev mode (i.e. no restart) when only >> modifying jsp or static resources (html, js, css etc...) >> > At least, I think we should make it clear in the documentation and issue >> a >> > warning at runtime when we detect an overlay. >> What I can do is to extract the war content (except WEB-INF/lib as >> it's already added) under the warSourceDirectory plugin parameter >> (default src/main/webapp) which is the docBase (but with a parameter >> called extractPath relative to the docBase). >> The plugin configuration part could be >> >> >> org.foo >> bar >> bar >> >> >> >> What I don't like is people will have to ignore this directory in their scm >> >> The best: extract somewhere (temporary directory) and add this as "a >> symlink" in the docBase. >> >> > I will open a JIRA >> > >> > Jeff >> > >> > On Sat, Apr 28, 2012 at 11:38 PM, Olivier Lamy wrote: >> > >> >> Salut Jeff, >> >> >> >> Current Overlay support with tomcat6/7:run is very limited (only use >> >> jars from WEB-INF/lib of the the war dependencies). >> >> Perso, I use maven-dependency-plugin to extract war content (see >> >> sample in this pom [1] ). >> >> I agree it's "hackhish" :-) and having a better support as in the war >> >> plugin could be better. >> >> But didn't yet have any time to work on that. (can you create an issue >> >> for that ?) >> >> As my goal was to cut a release soon (ideally starting release process >> >> next week, I'm not sure I will have time to work on that) >> >> >> >> -- >> >> Olivier Lamy >> >> Talend: http://coders.talend.com >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> [1] >> >> >> http://svn.apache.org/repos/asf/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/pom.xml >> >> >> >> 2012/4/28 Jeff MAURY : >> >> > Hello, >> >> > >> >> > I am facing the following problem with WAR overlays: >> >> > I have a first WAR, called skeleton, that contains all necessary >> stuff: >> >> > base web.xml, index.jsp and JAR dependencies. >> >> > I have another WAR whose first dependency is the skeleton which is >> (as of >> >> > yet) almost empty except for the slf4j_log4 dependency. >> >> > When i run tomcat7:run on the skeleton, everything is ok >> >> > When I run tomcat7:run on the second war, Tomcat start but I am not >> able >> >> to >> >> > use the application. >> >> > I have look at the mojo code and it seems it is using the web app >> source >> >> > directory (src/main/webapp) by default so as it is empty my case, it >> >> cannot >> >> > work. >> >> > AM I missing something ? >> >> > >> >> > Thanks >> >> > Jeff >> >> > >> >> > >> >> > -- >> >> > Jeff MAURY >> >> > >> >> > >> >> > "Legacy code" often differs from its suggested alternative by actually >> >> > working and scaling. >> >> > - Bjarne Stroustrup >> >> > >> >> > http://www.jeffmaury.com >> >> > http://riadiscuss.jeffmaury.com >> >> > http://www.twitter.com/jeffmaur
Re: Does Tomcat Maven plugin support WAR overlays ?
2012/4/30 Jeff MAURY : > Salut Olivier, > > I wanted to make sure I understand the goal properly. > Is the rationale for using src/main/webapp as the default docbase for > Tomcat to propagate modifications of files on the fly (JSP,...) without the > need to restart Tomcat ? Yup that's the goal. Fast dev mode (i.e. no restart) when only modifying jsp or static resources (html, js, css etc...) > At least, I think we should make it clear in the documentation and issue a > warning at runtime when we detect an overlay. What I can do is to extract the war content (except WEB-INF/lib as it's already added) under the warSourceDirectory plugin parameter (default src/main/webapp) which is the docBase (but with a parameter called extractPath relative to the docBase). The plugin configuration part could be org.foo bar bar What I don't like is people will have to ignore this directory in their scm The best: extract somewhere (temporary directory) and add this as "a symlink" in the docBase. > I will open a JIRA > > Jeff > > On Sat, Apr 28, 2012 at 11:38 PM, Olivier Lamy wrote: > >> Salut Jeff, >> >> Current Overlay support with tomcat6/7:run is very limited (only use >> jars from WEB-INF/lib of the the war dependencies). >> Perso, I use maven-dependency-plugin to extract war content (see >> sample in this pom [1] ). >> I agree it's "hackhish" :-) and having a better support as in the war >> plugin could be better. >> But didn't yet have any time to work on that. (can you create an issue >> for that ?) >> As my goal was to cut a release soon (ideally starting release process >> next week, I'm not sure I will have time to work on that) >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> [1] >> http://svn.apache.org/repos/asf/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/pom.xml >> >> 2012/4/28 Jeff MAURY : >> > Hello, >> > >> > I am facing the following problem with WAR overlays: >> > I have a first WAR, called skeleton, that contains all necessary stuff: >> > base web.xml, index.jsp and JAR dependencies. >> > I have another WAR whose first dependency is the skeleton which is (as of >> > yet) almost empty except for the slf4j_log4 dependency. >> > When i run tomcat7:run on the skeleton, everything is ok >> > When I run tomcat7:run on the second war, Tomcat start but I am not able >> to >> > use the application. >> > I have look at the mojo code and it seems it is using the web app source >> > directory (src/main/webapp) by default so as it is empty my case, it >> cannot >> > work. >> > AM I missing something ? >> > >> > Thanks >> > Jeff >> > >> > >> > -- >> > Jeff MAURY >> > >> > >> > "Legacy code" often differs from its suggested alternative by actually >> > working and scaling. >> > - Bjarne Stroustrup >> > >> > http://www.jeffmaury.com >> > http://riadiscuss.jeffmaury.com >> > http://www.twitter.com/jeffmaury >> > >> > >> > -- >> > Jeff MAURY >> > >> > >> > "Legacy code" often differs from its suggested alternative by actually >> > working and scaling. >> > - Bjarne Stroustrup >> > >> > http://www.jeffmaury.com >> > http://riadiscuss.jeffmaury.com >> > http://www.twitter.com/jeffmaury >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mvn tomcat:deploy fails with HTTP response 401
Hi, That's not an issue. See documentation here: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html 2012/4/30 Martin Gainty : > > > redirecting to maven users ..as this is a maven issue > > Thanks, > Martin > __ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger > sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung > oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich > dem Austausch von Informationen und entfaltet keine rechtliche > Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen > wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire informez > l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci > est interdite. Ce message sert à l'information seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > >> Date: Sat, 28 Apr 2012 23:24:36 +0200 >> Subject: Re: mvn tomcat:deploy fails with HTTP response 401 >> From: hord...@gmail.com >> To: users@tomcat.apache.org >> >> Awesome! I added the pluginGroup and it worked now. >> >> Thank you! >> >> 2012/4/28 Olivier Lamy >> >> > Have a look here >> > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html >> > >> > there is a section regarding content to add in ~/.m2/settings.xml >> > >> > or add the plugin declaration in the pom section build>plugins>plugin >> > (rather than pluginManagement) >> > >> > HTH >> > -- >> > Olivier Lamy >> > Talend: http://coders.talend.com >> > http://twitter.com/olamy | http://linkedin.com/in/olamy >> > >> > 2012/4/28 Henrique Ordine : >> > > Thanks again for your help. >> > > >> > > I added to my POM, but if I use tomcat6:deploy or >> > > tomcat6:run, Maven says: >> > > >> > > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist >> > > or no valid version could be found >> > > >> > > I'm using Maven, 2.2.0 by the way. >> > > >> > > 2012/4/27 Olivier Lamy >> > > >> > >> Add >> > >> >> > >> >> > >> apache.snapshots >> > >> Apache Snapshots >> > >> http://repository.apache.org/content/groups/snapshots-group/ >> > >> >> > >> >> > >> false >> > >> >> > >> >> > >> true >> > >> >> > >> >> > >> >> > >> >> > >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat >> > >> version you want to use). >> > >> >> > >> I'd like to know the command line you are using ? It must be >> > >> tomcat6:deploy or tomcat7:deploy >> > >> >> > >> 2012/4/27 Henrique Ordine : >> > >> > Thanks for your reply. >> > >> > >> > >> > I made the changes that you suggested but tomcat:deploy still fails >> > with >> > >> the >> > >> > same error. >> > >> > >> > >> > tomcat:run works, but it was already working before. >> > >> > >> > >> > My POM file is attached, if you could have a look at it, it would be >> > >> great. >> > >> > It's a small POM, I've only just started my App. >> > >> > >> > >> > Thanks in advance, >> > >> > >> > >> > Op 27 april 2012 12:14 schreef Olivier Lamy het >> > >> volgende: >> > >> >> >> > >> >> Hello, >> > >> >> >> > >> >> That's something which has been fixed in trunk (I will probably >> > >> >> rele
Re: Does Tomcat Maven plugin support WAR overlays ?
Salut Jeff, Current Overlay support with tomcat6/7:run is very limited (only use jars from WEB-INF/lib of the the war dependencies). Perso, I use maven-dependency-plugin to extract war content (see sample in this pom [1] ). I agree it's "hackhish" :-) and having a better support as in the war plugin could be better. But didn't yet have any time to work on that. (can you create an issue for that ?) As my goal was to cut a release soon (ideally starting release process next week, I'm not sure I will have time to work on that) -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy [1] http://svn.apache.org/repos/asf/archiva/trunk/archiva-modules/archiva-web/archiva-webapp/pom.xml 2012/4/28 Jeff MAURY : > Hello, > > I am facing the following problem with WAR overlays: > I have a first WAR, called skeleton, that contains all necessary stuff: > base web.xml, index.jsp and JAR dependencies. > I have another WAR whose first dependency is the skeleton which is (as of > yet) almost empty except for the slf4j_log4 dependency. > When i run tomcat7:run on the skeleton, everything is ok > When I run tomcat7:run on the second war, Tomcat start but I am not able to > use the application. > I have look at the mojo code and it seems it is using the web app source > directory (src/main/webapp) by default so as it is empty my case, it cannot > work. > AM I missing something ? > > Thanks > Jeff > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury > > > -- > Jeff MAURY > > > "Legacy code" often differs from its suggested alternative by actually > working and scaling. > - Bjarne Stroustrup > > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.twitter.com/jeffmaury - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: mvn tomcat:deploy fails with HTTP response 401
Have a look here http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html there is a section regarding content to add in ~/.m2/settings.xml or add the plugin declaration in the pom section build>plugins>plugin (rather than pluginManagement) HTH -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2012/4/28 Henrique Ordine : > Thanks again for your help. > > I added to my POM, but if I use tomcat6:deploy or > tomcat6:run, Maven says: > > The plugin 'org.apache.maven.plugins:maven-tomcat6-plugin' does not exist > or no valid version could be found > > I'm using Maven, 2.2.0 by the way. > > 2012/4/27 Olivier Lamy > >> Add >> >> >> apache.snapshots >> Apache Snapshots >> http://repository.apache.org/content/groups/snapshots-group/ >> >> >> false >> >> >> true >> >> >> >> >> Note now you must use tomcat6:run or tomcat7:run (depending tomcat >> version you want to use). >> >> I'd like to know the command line you are using ? It must be >> tomcat6:deploy or tomcat7:deploy >> >> 2012/4/27 Henrique Ordine : >> > Thanks for your reply. >> > >> > I made the changes that you suggested but tomcat:deploy still fails with >> the >> > same error. >> > >> > tomcat:run works, but it was already working before. >> > >> > My POM file is attached, if you could have a look at it, it would be >> great. >> > It's a small POM, I've only just started my App. >> > >> > Thanks in advance, >> > >> > Op 27 april 2012 12:14 schreef Olivier Lamy het >> volgende: >> >> >> >> Hello, >> >> >> >> That's something which has been fixed in trunk (I will probably >> >> release a 2.0 next week). >> >> >> >> >> >> 2012/4/27 Henrique Ordine : >> >> > Hi everybody, >> >> > >> >> > I'm trying to deploy my Maven Web App on my local Tomcat using the >> >> > tomcat:deploy maven plugin, but the Manager application fails with a >> >> > response code 401. >> >> > >> >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage >> to >> >> > access my Tomcat/manager app with the user "hordine", that I >> configured >> >> > and >> >> > deploy >> >> > >> >> > I've configured my tomcat-users.xml, settings.xml, and POM files, like >> >> > this: >> >> > >> >> > I've added this user to my tomcat-users.xml: >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > I've added this server to my settings.xml: >> >> > >> >> > >> >> > hordineLocalTomcat >> >> > hordine >> >> > hordine >> >> > >> >> > >> >> > >> >> > And I've configured my POM like this: >> >> > >> >> > >> >> > >> >> > hTask-web >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > org.apache.tomcat.maven >> >> > >> >> > tomcat-maven-plugin >> >> > >> >> > 1.1 >> >> >> >> Sure of that >> >> >> >> But to test if your issue is fixed in trunk try >> >> 2.0-SNAPSHOT >> >> >> >> see mojo declaration and repositories here: >> >> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html >> >> >> >> > >> >> > >> >> > >> >> > http://localhost:8080/manager >> >> > >> >> > hordineLocalTomcat >> >> > >> >> > /hTask-web >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >
Re: mvn tomcat:deploy fails with HTTP response 401
Add apache.snapshots Apache Snapshots http://repository.apache.org/content/groups/snapshots-group/ false true Note now you must use tomcat6:run or tomcat7:run (depending tomcat version you want to use). I'd like to know the command line you are using ? It must be tomcat6:deploy or tomcat7:deploy 2012/4/27 Henrique Ordine : > Thanks for your reply. > > I made the changes that you suggested but tomcat:deploy still fails with the > same error. > > tomcat:run works, but it was already working before. > > My POM file is attached, if you could have a look at it, it would be great. > It's a small POM, I've only just started my App. > > Thanks in advance, > > Op 27 april 2012 12:14 schreef Olivier Lamy het volgende: >> >> Hello, >> >> That's something which has been fixed in trunk (I will probably >> release a 2.0 next week). >> >> >> 2012/4/27 Henrique Ordine : >> > Hi everybody, >> > >> > I'm trying to deploy my Maven Web App on my local Tomcat using the >> > tomcat:deploy maven plugin, but the Manager application fails with a >> > response code 401. >> > >> > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage to >> > access my Tomcat/manager app with the user "hordine", that I configured >> > and >> > deploy >> > >> > I've configured my tomcat-users.xml, settings.xml, and POM files, like >> > this: >> > >> > I've added this user to my tomcat-users.xml: >> > >> > >> > >> > >> > >> > >> > >> > >> > I've added this server to my settings.xml: >> > >> > >> > hordineLocalTomcat >> > hordine >> > hordine >> > >> > >> > >> > And I've configured my POM like this: >> > >> > >> > >> > hTask-web >> > >> > >> > >> > >> > >> > >> > >> > org.apache.tomcat.maven >> > >> > tomcat-maven-plugin >> > >> > 1.1 >> >> Sure of that >> >> But to test if your issue is fixed in trunk try >> 2.0-SNAPSHOT >> >> see mojo declaration and repositories here: >> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html >> >> > >> > >> > >> > http://localhost:8080/manager >> > >> > hordineLocalTomcat >> > >> > /hTask-web >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > I'd appreciate any help. >> > >> > This is the entire error's stack trace: >> > >> > Embedded error: Server returned HTTP response code: 401 for URL: >> > http://localhost:8080/manager/deploy?path=%2FhTask-web&war= >> > [INFO] >> > >> > [INFO] Trace >> > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke >> > Tomcat manager >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) >> > at >> > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) >> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) >> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) >> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) >> > at >> > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> > at >> > >
Re: mvn tomcat:deploy fails with HTTP response 401
Hello, That's something which has been fixed in trunk (I will probably release a 2.0 next week). 2012/4/27 Henrique Ordine : > Hi everybody, > > I'm trying to deploy my Maven Web App on my local Tomcat using the > tomcat:deploy maven plugin, but the Manager application fails with a > response code 401. > > I have Tomcat 6 installed on Mac OS Leopard, with Java 1.5. I manage to > access my Tomcat/manager app with the user "hordine", that I configured and > deploy > > I've configured my tomcat-users.xml, settings.xml, and POM files, like this: > > I've added this user to my tomcat-users.xml: > > > > > > > > > I've added this server to my settings.xml: > > > hordineLocalTomcat > hordine > hordine > > > > And I've configured my POM like this: > > > > hTask-web > > > > > > > > org.apache.tomcat.maven > > tomcat-maven-plugin > > 1.1 Sure of that But to test if your issue is fixed in trunk try 2.0-SNAPSHOT see mojo declaration and repositories here: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html > > > > http://localhost:8080/manager > > hordineLocalTomcat > > /hTask-web > > > > > > > > > > > > > I'd appreciate any help. > > This is the entire error's stack trace: > > Embedded error: Server returned HTTP response code: 401 for URL: > http://localhost:8080/manager/deploy?path=%2FhTask-web&war= > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke > Tomcat manager > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:592) > at org.codehaus.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.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:149) > at > org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarCatalinaMojo.java:70) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > ... 17 more > Caused by: java.io.IOException: Server returned HTTP response code: 401 for > URL: http://localhost:8080/manager/deploy?path=%2FhTask-web&war= > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1196) > at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:604) > at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java:662) > at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:295) > at > org.codehaus.mojo.tomcat.AbstractDeployWarMojo.deployWar(AbstractDeployWarMojo.java:85) > at > org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDeployMojo.java:85) > at > org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalinaMojo.java:141) > ... 20 more > > > -- > Henrique Ordine > > http://hordine.wordpress.com/ -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat maven plugin deploy to multiple tomcat instances...
Do that work adding in the section: deploy ? 2012/4/19 Jeff : > (Didn't see a specific mailing list for the tomcat-maven-plugin...) > > I finally got the 2.0-SNAPSHOT version of the tomcat6-maven-plugin working > against a single server, but wondered how I could configure it to push to > multiple tomcat instances based on the environment. For example, our > staging environment for this application has 2 load balance servers. > > I tried using the structure like I do when running ws-import > but it doesn't seem to support that. > > Is there another way to easily handle deployments to multiple servers with > this plugin? If not, what would it take to support executions? Here is > what I tried. > > > > deploy-stage > > false > > > > > org.apache.tomcat.maven > tomcat6-maven-plugin > 2.0-SNAPSHOT > > > stage01 > > war > http://10.12.4.1/manager > true > UTF-8 > UTF-8 > HTTP/1.1 > true > stage01 > > > > stage06 > > war > http://10.12.4.6/manager > true > UTF-8 > UTF-8 > HTTP/1.1 > true > stage06 > > > > > -- > Jeff Vincent > predato...@gmail.com > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
Hi,
2012/4/13 Leigh Anderson :
> Hi Olivier,
>
> It's actually the act of declaring a context.xml with a Loader element
> that causes the application to fail. A new instance of WebAppLoader is
> created, overriding the one carefully created by the plugin, without the
> benefit of a properly configured class path. I've included a small patch
> below which demonstrates my intent.
Oh sure good catch.
>
> I'd added
> org.springframework.instrument.classloading.tomcat.Tomcat
> InstrumentableClassLoader to the plugin configuration,
> which was then picked up correctly and used by the WebAppLoader.
Could you attach the patch to an issue ?
>
> Thanks,
> Leigh
>
> Index:
> tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/r
> un/AbstractRunMojo.java
> ===
> ---
> tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/r
> un/AbstractRunMojo.java (revision 1)
> +++
> tomcat7-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat7/r
> un/AbstractRunMojo.java (revision )
> @@ -363,6 +357,15 @@
> */
> private ClassRealm tomcatRealm;
>
> + /**
> + * Class loader class to set.
> + *
> + * @parameter
> + */
> + protected String classLoaderClass;
> +
> //
> --
> // Mojo Implementation
> //
> --
> @@ -460,14 +462,19 @@
> {
> context.setParentClassLoader( getTomcatClassLoader() );
> }
> + final WebappLoader loader = createWebappLoader();
>
> - context.setLoader( createWebappLoader() );
> + context.setLoader( loader );
> File contextFile = getContextFile();
> if ( contextFile != null )
> {
> context.setConfigFile( getContextFile().toURI().toURL() );
> }
> + if (classLoaderClass != null) {
> + loader.setLoaderClass(classLoaderClass);
> + }
>
> +
> return context;
>
> }
>
>
>
> On 12/04/2012 13:14, "Olivier Lamy" wrote:
>
>>The plugin has an option to setup context.xml to use see [1].
>>You can try to write an other context.xml only for using with the plugin ?
>>
>>--
>>Olivier
>>
>>[1]
>>http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/ru
>>n-mojo.html#contextFile
>>
>>2012/4/12 Leigh Anderson :
>>> Hi Olivier,
>>>
>>> That's solved the problem, thanks. Unfortunately, declaring a custom
>>>class
>>> loader in a context.xml causes Tomcat to use that one, instead of the
>>>one
>>> set up with the correct class path by the plugin. I'll keep looking to
>>>see
>>> if I can find a way around this.
>>>
>>> Thanks for your prompt help with this.
>>> Leigh
>>>
>>> On 12/04/2012 11:35, "Olivier Lamy" wrote:
>>>
>>>>Hello,
>>>>Apologize for delay.
>>>>That should be fixed now (I have deployed 2.0-SNAPSHOT).
>>>>If you could try with your use case.
>>>>Thanks,
>>>>2012/4/8 Olivier Lamy :
>>>>> Hello Leigh,
>>>>> Thanks for creating issue.
>>>>> Until now I tried to reproduce the issue but I failed.
>>>>> I wonder if you could attach a build log using -e mvn flag.
>>>>>
>>>>> 2012/4/5 Leigh Anderson :
>>>>>> Hi Olivier,
>>>>>>
>>>>>> I'm not able to run this with tomcat6 as it's a Servlet 3.0 project.
>>>>>>I'll
>>>>>> get the issue created -- should have some time next week to put
>>>>>>together a
>>>>>> sample project.
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Leigh
>>>>>>
>>>>>> On 04/04/2012 11:36, "Olivier Lamy" wrote:
>>>>>>
>>>>>>>Hello,
>>>>>>>Looks to be an issue (does that work with tomcat6:run ?)
>>>>>>>Could you create an issue here:
>>>>>>>https://issues.apache.org/jira/browse/MTOMCAT (if possible with a
>>>>>>>small sample project to reproduce).
>>>>>>>
>>>>>>>Thanks
>>>>>>>--
>>>>>>>Olivier Lamy
>>>>>>>
Re: Tomcat 7 Maven plugin: deploy fails with tomcatManager status code:401, ReasonPhrase:Unauthorized
Hi, Can you try with: mvn tomcat7:deploy -Dtomcat.username=Administrator -Dtomcat.password=a See Mojo documentation: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/deploy-mojo.html 2012/4/13 Matt Munz : > Olivier, > > When I try to deploy from Maven, the following message appears in the access > log. [1] There are no other messages in any of the other logs for this event. > > [1] 127.0.0.1 - - [12/Apr/2012:21:15:59 -0700] "PUT > /manager/html/deploy?path=%2F HTTP/1.1" 401 2550 > > Matt > > On Apr 12, 2012, at 6:46 PM, Matt Munz wrote: > >> Olivier, >> >> Thanks for getting to this. >> >>> Do you have more logs/details from your tomcat instance ? >>> Especially: $CATALINA_HOME/logs/localhost_access_log.-MM-dd.txt >>> and entries corresponding to the deployment >> >> I will collect these and send them in a subsequent email. >> >>> Are you passing tru a http server which is proxying/redirecting to the >>> Tomcat instance ? >> >> Nope. This is on an OS X machine. All I did was install Tomcat 7 in a >> local directory, modify tomcat-users.xml as I described below, and start >> Tomcat. >> >>> What kind of deployment are you doing ? one with contextFile parameter ? >> >> No, I'm just using the parameters I mentioned previously. [1] >> >> [1] mvn tomcat7:deploy -Dusername=Administrator -Dpassword=a >> >> Matt >> >> On Apr 12, 2012, at 3:54 PM, Olivier Lamy wrote: >> >>> Hello, >>> Currently, I cannot reproduce. >>> Do you have more logs/details from your tomcat instance ? >>> Especially: $CATALINA_HOME/logs/localhost_access_log.-MM-dd.txt >>> and entries corresponding to the deployment >>> Are you passing tru a http server which is proxying/redirecting to the >>> Tomcat instance ? >>> What kind of deployment are you doing ? one with contextFile parameter ? >>> >>> >>> 2012/4/6 Matt Munz : >>>> Olivier, >>>> >>>> OK. Thanks. So with the 2.0-SNAPSHOT version I am getting the same >>>> error (HTTP 401). [1] Interestingly, the plugin output makes it look like >>>> the WAR file was uploaded but when I visit the Manager, I can see that it >>>> is not deployed. >>>> >>>> Do you have any thoughts about what I can do to debug this further? I'd >>>> really like to get this working. >>>> >>>> [1] >>>> [INFO] Deploying war to http://localhost:8080/ >>>> Uploading: http://localhost:8080/manager/html/deploy?path=%2F >>>> Uploaded: http://localhost:8080/manager/html/deploy?path=%2F (9555 KB at >>>> 33760.1 KB/sec) >>>> [INFO] tomcatManager status code:401, ReasonPhrase:Unauthorized >>>> >>>> Matt >>>> >>>> >>>> On Apr 4, 2012, at 12:23 AM, Olivier Lamy wrote: >>>> >>>>> Hello, >>>>> Have a look here: >>>>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html >>>>> >>>>> 2012/4/4 Matt Munz : >>>>>> Olivier, >>>>>> >>>>>> I made that change to settings.xml and now I'm getting a different >>>>>> error. [1] How can I find out where this plugin is stored? Perhaps >>>>>> there is a problem with the repository or my repository configuration. >>>>>> >>>>>> [1] >>>>>> [WARNING] The POM for >>>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is >>>>>> missing, no dependency information available >>>>>> [WARNING] Failed to retrieve plugin descriptor for >>>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT: Plugin >>>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT or one of its >>>>>> dependencies could not be resolved: Failed to read artifact descriptor >>>>>> for org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT >>>>>> ... >>>>>> [WARNING] The POM for >>>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is >>>>>> missing, no dependency information available >>>>>> ... >>>>>> [ERROR] Plugin org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT >>>>>> or one of its dependencies could not be resolved: Fai
Re: Tomcat 7 Maven plugin: deploy fails with tomcatManager status code:401, ReasonPhrase:Unauthorized
Hello, Currently, I cannot reproduce. Do you have more logs/details from your tomcat instance ? Especially: $CATALINA_HOME/logs/localhost_access_log.-MM-dd.txt and entries corresponding to the deployment Are you passing tru a http server which is proxying/redirecting to the Tomcat instance ? What kind of deployment are you doing ? one with contextFile parameter ? 2012/4/6 Matt Munz : > Olivier, > > OK. Thanks. So with the 2.0-SNAPSHOT version I am getting the same error > (HTTP 401). [1] Interestingly, the plugin output makes it look like the WAR > file was uploaded but when I visit the Manager, I can see that it is not > deployed. > > Do you have any thoughts about what I can do to debug this further? I'd > really like to get this working. > > [1] > [INFO] Deploying war to http://localhost:8080/ > Uploading: http://localhost:8080/manager/html/deploy?path=%2F > Uploaded: http://localhost:8080/manager/html/deploy?path=%2F (9555 KB at > 33760.1 KB/sec) > [INFO] tomcatManager status code:401, ReasonPhrase:Unauthorized > > Matt > > > On Apr 4, 2012, at 12:23 AM, Olivier Lamy wrote: > >> Hello, >> Have a look here: >> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html >> >> 2012/4/4 Matt Munz : >>> Olivier, >>> >>> I made that change to settings.xml and now I'm getting a different error. >>> [1] How can I find out where this plugin is stored? Perhaps there is a >>> problem with the repository or my repository configuration. >>> >>> [1] >>> [WARNING] The POM for >>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is missing, >>> no dependency information available >>> [WARNING] Failed to retrieve plugin descriptor for >>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT: Plugin >>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT or one of its >>> dependencies could not be resolved: Failed to read artifact descriptor for >>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT >>> ... >>> [WARNING] The POM for >>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is missing, >>> no dependency information available >>> ... >>> [ERROR] Plugin org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT or >>> one of its dependencies could not be resolved: Failed to read artifact >>> descriptor for >>> org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT: Could not >>> find artifact org.apache.tomcat.maven:tomcat7-maven-plugin:pom:2.0-SNAPSHOT >>> -> [Help 1] >>> >>> Matt Munz >>> >>> On Apr 2, 2012, at 11:48 PM, Olivier Lamy wrote: >>> >>>> Hello, >>>> With version from codehaus manager url for tomcat7 is not correct. >>>> (see >>>> http://mojo.codehaus.org/tomcat-maven-plugin/examples/deployment-tomcat7.html) >>>> >>>> Regarding the plugin prefix trouble, you have two solutions to use the >>>> correct version: >>>> >>>> * use the full cli: mvn >>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:deploy >>>> * configure your settings.xml with the entry >>>> >>>> >>>> org.apache.tomcat.maven >>>> >>>> >>>> >>>> HTH, >>>> -- >>>> Olivier Lamy >>>> Talend: http://coders.talend.com >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> 2012/4/3 Matt Munz : >>>>> Olivier, >>>>> >>>>> After switching to 2.0-SNAPSHOT, I am still getting errors :( First I >>>>> got an error saying that the tomcat7 prefix was not found. [1] Then I >>>>> tried "mvn tomcat:deploy -Dusername=Administrator -Dpassword=a" and I >>>>> got a 403 response from the manager. >>>>> >>>>> [1] >>>>> [ERROR] No plugin found for prefix 'tomcat7' in the current project and >>>>> in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] >>>>> available from the repositories [local (/Users/mattmunz/.m2/repository), >>>>> central (http://repo1.maven.org/maven2)] -> [Help 1] >>>>> [2] >>>>> [ERROR] Failed to execute goal >>>>> org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project >>>>> ...: Cannot invoke Tomcat manager: Server returned
Re: Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
The plugin has an option to setup context.xml to use see [1]. You can try to write an other context.xml only for using with the plugin ? -- Olivier [1] http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#contextFile 2012/4/12 Leigh Anderson : > Hi Olivier, > > That's solved the problem, thanks. Unfortunately, declaring a custom class > loader in a context.xml causes Tomcat to use that one, instead of the one > set up with the correct class path by the plugin. I'll keep looking to see > if I can find a way around this. > > Thanks for your prompt help with this. > Leigh > > On 12/04/2012 11:35, "Olivier Lamy" wrote: > >>Hello, >>Apologize for delay. >>That should be fixed now (I have deployed 2.0-SNAPSHOT). >>If you could try with your use case. >>Thanks, >>2012/4/8 Olivier Lamy : >>> Hello Leigh, >>> Thanks for creating issue. >>> Until now I tried to reproduce the issue but I failed. >>> I wonder if you could attach a build log using -e mvn flag. >>> >>> 2012/4/5 Leigh Anderson : >>>> Hi Olivier, >>>> >>>> I'm not able to run this with tomcat6 as it's a Servlet 3.0 project. >>>>I'll >>>> get the issue created -- should have some time next week to put >>>>together a >>>> sample project. >>>> >>>> >>>> Thanks, >>>> Leigh >>>> >>>> On 04/04/2012 11:36, "Olivier Lamy" wrote: >>>> >>>>>Hello, >>>>>Looks to be an issue (does that work with tomcat6:run ?) >>>>>Could you create an issue here: >>>>>https://issues.apache.org/jira/browse/MTOMCAT (if possible with a >>>>>small sample project to reproduce). >>>>> >>>>>Thanks >>>>>-- >>>>>Olivier Lamy >>>>>Talend: http://coders.talend.com >>>>>http://twitter.com/olamy | http://linkedin.com/in/olamy >>>>> >>>>>2012/4/3 Leigh Anderson : >>>>>> Hi All, >>>>>> >>>>>> I'm trying to start a web application with 'mvn tomcat7:run'. It >>>>>>seems >>>>>> that with the configuration below it fails with the following error: >>>>>> >>>>>> >>>>>> [INFO] >>>>>> >>>>>>-- >>>>>>-- >>>>>> [ERROR] Failed to execute goal >>>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run >>>>>>(default-cli) >>>>>> on project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1] >>>>>> [ERROR] >>>>>> [ERROR] To see the full stack trace of the errors, re-run >>>>>>Maven >>>>>>with the >>>>>> -e switch. >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug >>>>>>logging. >>>>>> >>>>>> I have also tried >>>>>> * 'mvn tomcat:run-war', which seems to get past this point, >>>>>>but >>>>>>then the >>>>>> application will not start because the 'additionalClasspathDir' >>>>>>property >>>>>> is not supported by the 'run-war' goal. >>>>>> * removing 'useSeparateTomcatClassLoader' which then doesn't >>>>>>load the >>>>>> Spring instrumenting class loader required to use AspectJ LTW, >>>>>>specified >>>>>> in >>>>>> context.xml. I have confirmed that I get the same 'no such archiver' >>>>>>error >>>>>> if I remove the >>>>>> context.xml, so I don't believe this to be the cause. >>>>>> >>>>>> Is there something I've missed in the configuration? >>>>>> >>>>>> Cheers, >>>>>> Leigh >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> org.apache.tomcat.maven >>>>>> tomcat7-maven-
Re: Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
Hello,
Apologize for delay.
That should be fixed now (I have deployed 2.0-SNAPSHOT).
If you could try with your use case.
Thanks,
2012/4/8 Olivier Lamy :
> Hello Leigh,
> Thanks for creating issue.
> Until now I tried to reproduce the issue but I failed.
> I wonder if you could attach a build log using -e mvn flag.
>
> 2012/4/5 Leigh Anderson :
>> Hi Olivier,
>>
>> I'm not able to run this with tomcat6 as it's a Servlet 3.0 project. I'll
>> get the issue created -- should have some time next week to put together a
>> sample project.
>>
>>
>> Thanks,
>> Leigh
>>
>> On 04/04/2012 11:36, "Olivier Lamy" wrote:
>>
>>>Hello,
>>>Looks to be an issue (does that work with tomcat6:run ?)
>>>Could you create an issue here:
>>>https://issues.apache.org/jira/browse/MTOMCAT (if possible with a
>>>small sample project to reproduce).
>>>
>>>Thanks
>>>--
>>>Olivier Lamy
>>>Talend: http://coders.talend.com
>>>http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>>2012/4/3 Leigh Anderson :
>>>> Hi All,
>>>>
>>>> I'm trying to start a web application with 'mvn tomcat7:run'. It seems
>>>> that with the configuration below it fails with the following error:
>>>>
>>>>
>>>> [INFO]
>>>>
>>>> [ERROR] Failed to execute goal
>>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run
>>>>(default-cli)
>>>> on project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>>with the
>>>> -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>>logging.
>>>>
>>>> I have also tried
>>>> * 'mvn tomcat:run-war', which seems to get past this point, but
>>>>then the
>>>> application will not start because the 'additionalClasspathDir' property
>>>> is not supported by the 'run-war' goal.
>>>> * removing 'useSeparateTomcatClassLoader' which then doesn't
>>>>load the
>>>> Spring instrumenting class loader required to use AspectJ LTW, specified
>>>> in
>>>> context.xml. I have confirmed that I get the same 'no such archiver'
>>>>error
>>>> if I remove the
>>>> context.xml, so I don't believe this to be the cause.
>>>>
>>>> Is there something I've missed in the configuration?
>>>>
>>>> Cheers,
>>>> Leigh
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> org.apache.tomcat.maven
>>>> tomcat7-maven-plugin
>>>> 2.0-beta-1
>>>>
>>>>
>>>>
>>>>true
>>>> localhost
>>>> 9090
>>>> 8443
>>>>
>>>> 9090
>>>> 8443
>>>> /
>>>> false
>>>>
>>>>
>>>>
>>>>${project.basedir}/config>>>>
>>>>
>>>>
>>>> true
>>>>
>>>>
>>>>
>>>> org.springframework
>>>>
>>>>
>>>>spring-instrument-tomcat
>>>> ${spring.version}
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> In order to protect our email recipients, Betfair Group use SkyScan from
>>>> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>>>>
>>>> ___
Re: Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
Hello Leigh,
Thanks for creating issue.
Until now I tried to reproduce the issue but I failed.
I wonder if you could attach a build log using -e mvn flag.
2012/4/5 Leigh Anderson :
> Hi Olivier,
>
> I'm not able to run this with tomcat6 as it's a Servlet 3.0 project. I'll
> get the issue created -- should have some time next week to put together a
> sample project.
>
>
> Thanks,
> Leigh
>
> On 04/04/2012 11:36, "Olivier Lamy" wrote:
>
>>Hello,
>>Looks to be an issue (does that work with tomcat6:run ?)
>>Could you create an issue here:
>>https://issues.apache.org/jira/browse/MTOMCAT (if possible with a
>>small sample project to reproduce).
>>
>>Thanks
>>--
>>Olivier Lamy
>>Talend: http://coders.talend.com
>>http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>2012/4/3 Leigh Anderson :
>>> Hi All,
>>>
>>> I'm trying to start a web application with 'mvn tomcat7:run'. It seems
>>> that with the configuration below it fails with the following error:
>>>
>>>
>>> [INFO]
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run
>>>(default-cli)
>>> on project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven
>>>with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>>>logging.
>>>
>>> I have also tried
>>> * 'mvn tomcat:run-war', which seems to get past this point, but
>>>then the
>>> application will not start because the 'additionalClasspathDir' property
>>> is not supported by the 'run-war' goal.
>>> * removing 'useSeparateTomcatClassLoader' which then doesn't
>>>load the
>>> Spring instrumenting class loader required to use AspectJ LTW, specified
>>> in
>>> context.xml. I have confirmed that I get the same 'no such archiver'
>>>error
>>> if I remove the
>>> context.xml, so I don't believe this to be the cause.
>>>
>>> Is there something I've missed in the configuration?
>>>
>>> Cheers,
>>> Leigh
>>>
>>>
>>>
>>>
>>>
>>> org.apache.tomcat.maven
>>> tomcat7-maven-plugin
>>> 2.0-beta-1
>>>
>>>
>>>
>>>true
>>> localhost
>>> 9090
>>> 8443
>>>
>>> 9090
>>> 8443
>>> /
>>> false
>>>
>>>
>>>
>>>${project.basedir}/config>>>
>>>
>>>
>>> true
>>>
>>>
>>>
>>> org.springframework
>>>
>>>
>>>spring-instrument-tomcat
>>> ${spring.version}
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> In order to protect our email recipients, Betfair Group use SkyScan from
>>> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>>>
>>> ________
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>
>>-
>>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>
>
>
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat7-maven-plugin 2.0-beta1 and useSeparateTomcatClassloader fails with run goal
Hello,
Looks to be an issue (does that work with tomcat6:run ?)
Could you create an issue here:
https://issues.apache.org/jira/browse/MTOMCAT (if possible with a
small sample project to reproduce).
Thanks
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
2012/4/3 Leigh Anderson :
> Hi All,
>
> I'm trying to start a web application with 'mvn tomcat7:run'. It seems
> that with the configuration below it fails with the following error:
>
>
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1:run (default-cli)
> on project mantis-test-web-app: No such archiver: 'jar'. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> I have also tried
> * 'mvn tomcat:run-war', which seems to get past this point, but then
> the
> application will not start because the 'additionalClasspathDir' property
> is not supported by the 'run-war' goal.
> * removing 'useSeparateTomcatClassLoader' which then doesn't load the
> Spring instrumenting class loader required to use AspectJ LTW, specified
> in
> context.xml. I have confirmed that I get the same 'no such archiver' error
> if I remove the
> context.xml, so I don't believe this to be the cause.
>
> Is there something I've missed in the configuration?
>
> Cheers,
> Leigh
>
>
>
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0-beta-1
>
>
>
> true
> localhost
> 9090
> 8443
>
> 9090
> 8443
> /
> false
>
>
> ${project.basedir}/config
>
>
> true
>
>
>
> org.springframework
>
>
> spring-instrument-tomcat
> ${spring.version}
>
>
>
>
>
>
>
> In order to protect our email recipients, Betfair Group use SkyScan from
> MessageLabs to scan all Incoming and Outgoing mail for viruses.
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 Maven plugin: deploy fails with tomcatManager status code:401, ReasonPhrase:Unauthorized
Hello, Have a look here: http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html 2012/4/4 Matt Munz : > Olivier, > > I made that change to settings.xml and now I'm getting a different error. > [1] How can I find out where this plugin is stored? Perhaps there is a > problem with the repository or my repository configuration. > > [1] > [WARNING] The POM for > org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT: Plugin > org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT or one of its > dependencies could not be resolved: Failed to read artifact descriptor for > org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT > ... > [WARNING] The POM for > org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT is missing, no > dependency information available > ... > [ERROR] Plugin org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT or > one of its dependencies could not be resolved: Failed to read artifact > descriptor for org.apache.tomcat.maven:tomcat7-maven-plugin:jar:2.0-SNAPSHOT: > Could not find artifact > org.apache.tomcat.maven:tomcat7-maven-plugin:pom:2.0-SNAPSHOT -> [Help 1] > > Matt Munz > > On Apr 2, 2012, at 11:48 PM, Olivier Lamy wrote: > >> Hello, >> With version from codehaus manager url for tomcat7 is not correct. >> (see >> http://mojo.codehaus.org/tomcat-maven-plugin/examples/deployment-tomcat7.html) >> >> Regarding the plugin prefix trouble, you have two solutions to use the >> correct version: >> >> * use the full cli: mvn >> org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:deploy >> * configure your settings.xml with the entry >> >> >> org.apache.tomcat.maven >> >> >> >> HTH, >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> 2012/4/3 Matt Munz : >>> Olivier, >>> >>> After switching to 2.0-SNAPSHOT, I am still getting errors :( First I got >>> an error saying that the tomcat7 prefix was not found. [1] Then I tried >>> "mvn tomcat:deploy -Dusername=Administrator -Dpassword=a" and I got a 403 >>> response from the manager. >>> >>> [1] >>> [ERROR] No plugin found for prefix 'tomcat7' in the current project and in >>> the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available >>> from the repositories [local (/Users/mattmunz/.m2/repository), central >>> (http://repo1.maven.org/maven2)] -> [Help 1] >>> [2] >>> [ERROR] Failed to execute goal >>> org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project >>> ...: Cannot invoke Tomcat manager: Server returned HTTP response code: 403 >>> for URL: http://localhost:8080/manager/deploy?path=%2F...&war= -> [Help 1] >>> >>> Matt >>> >>> On Apr 2, 2012, at 4:16 AM, Olivier Lamy wrote: >>> >>>> Hello, >>>> I have fixed few things related to deployment in trunk. >>>> Could you test with current 2.0-SNAPSHOT ? >>>> >>>> Thanks >>>> -- >>>> Olivier Lamy >>>> Talend: http://coders.talend.com >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> 2012/4/2 Matt Munz : >>>>> Hi all, >>>>> >>>>> I'm trying to get the Tomcat 7 Maven plugin to work and I'm getting an >>>>> authorization problem.[1] Here's the command that I'm running. [2] >>>>> Here's the relevant snippet from tomcat-users.xml. [3] From the browser >>>>> I am able to log on to the Manager with this account without problems. >>>>> >>>>> Any help you could provide would be greatly appreciated. >>>>> >>>>> [1] tomcatManager status code:401, ReasonPhrase:Unauthorized >>>>> [2] mvn tomcat7:deploy -Dusername=Administrator -Dpassword=a >>>>> [3] >>>>> >>>>> >>>>> >>>>> >>>> roles="manager-gui,manager-script,manager-jmx"/> >>>>> >>>>> Matt Munz >>>>> matt.m.m...@gmail.com >>>>> >>>>> >>>>> >>>>> >>>> >>>> ---
Re: Tomcat 7 Maven plugin: deploy fails with tomcatManager status code:401, ReasonPhrase:Unauthorized
Hello, With version from codehaus manager url for tomcat7 is not correct. (see http://mojo.codehaus.org/tomcat-maven-plugin/examples/deployment-tomcat7.html) Regarding the plugin prefix trouble, you have two solutions to use the correct version: * use the full cli: mvn org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-SNAPSHOT:deploy * configure your settings.xml with the entry org.apache.tomcat.maven HTH, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2012/4/3 Matt Munz : > Olivier, > > After switching to 2.0-SNAPSHOT, I am still getting errors :( First I got > an error saying that the tomcat7 prefix was not found. [1] Then I tried "mvn > tomcat:deploy -Dusername=Administrator -Dpassword=a" and I got a 403 > response from the manager. > > [1] > [ERROR] No plugin found for prefix 'tomcat7' in the current project and in > the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available > from the repositories [local (/Users/mattmunz/.m2/repository), central > (http://repo1.maven.org/maven2)] -> [Help 1] > [2] > [ERROR] Failed to execute goal > org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project > ...: Cannot invoke Tomcat manager: Server returned HTTP response code: 403 > for URL: http://localhost:8080/manager/deploy?path=%2F...&war= -> [Help 1] > > Matt > > On Apr 2, 2012, at 4:16 AM, Olivier Lamy wrote: > >> Hello, >> I have fixed few things related to deployment in trunk. >> Could you test with current 2.0-SNAPSHOT ? >> >> Thanks >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> 2012/4/2 Matt Munz : >>> Hi all, >>> >>> I'm trying to get the Tomcat 7 Maven plugin to work and I'm getting an >>> authorization problem.[1] Here's the command that I'm running. [2] Here's >>> the relevant snippet from tomcat-users.xml. [3] From the browser I am able >>> to log on to the Manager with this account without problems. >>> >>> Any help you could provide would be greatly appreciated. >>> >>> [1] tomcatManager status code:401, ReasonPhrase:Unauthorized >>> [2] mvn tomcat7:deploy -Dusername=Administrator -Dpassword=a >>> [3] >>> >>> >>> >>> >> roles="manager-gui,manager-script,manager-jmx"/> >>> >>> Matt Munz >>> matt.m.m...@gmail.com >>> >>> >>> >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 Maven plugin: deploy fails with tomcatManager status code:401, ReasonPhrase:Unauthorized
Hello, I have fixed few things related to deployment in trunk. Could you test with current 2.0-SNAPSHOT ? Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2012/4/2 Matt Munz : > Hi all, > > I'm trying to get the Tomcat 7 Maven plugin to work and I'm getting an > authorization problem.[1] Here's the command that I'm running. [2] Here's > the relevant snippet from tomcat-users.xml. [3] From the browser I am able > to log on to the Manager with this account without problems. > > Any help you could provide would be greatly appreciated. > > [1] tomcatManager status code:401, ReasonPhrase:Unauthorized > [2] mvn tomcat7:deploy -Dusername=Administrator -Dpassword=a > [3] > > > > roles="manager-gui,manager-script,manager-jmx"/> > > Matt Munz > matt.m.m...@gmail.com > > > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat Maven Plugin - Resource /WEB-INF/classes not found
atingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.catalina.LifecycleException: Failed to start > component [StandardEngine[Tomcat].StandardHost[localhost]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1568) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1558) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: org.apache.catalina.LifecycleException: A child container > failed during start > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1138) > at > org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:782) > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Using tomcat7-maven-plugin- 2.0-beta-1: java.lang.RuntimeException: Name jdbc is not bound in this Context
Hello
Sounds like an issue.
It will be really lovely if you could create a sample project to
reproduce that and attach it to a new issue here:
https://issues.apache.org/jira/browse/MTOMCAT
BTW does that work using a context file tru the configuration
${tomcatContextXml} (and not with a
server.xml file I mean nothing in src\main\tomcatconf ) ?
Thanks,
2012/3/7 Guofeng Zhang :
> Hi,
>
> I try tomcat7-maven-plugin/2.0-beta-1. When I use "mvn tomcat7:run" to launch
> my app, I got:
> javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
>
> I configured the datatsource as global naming datasource in server.xml,
>
> auth="Container"
> maxPoolSize="100" minPoolSize="10"
> name="jdbc/iviewDS"
> testQuery="select count(*) from T_ROLE"
> factory=".."
> type="javax.sql.DataSource"
> uniqueResourceName="jdbc/iviewDS"/>
>
> The server.xml is copied to src\main\tomcatconf, (this also copyied by the
> plugin to target\tomcat\conf, so it is used).
>
> then in webapp/META-INF/context.xml, I have:
> name="jdbc/iviewDS"
> global="jdbc/iviewDS"
> type="javax.sql.DataSource"
> />
>
> And in web.xml:
>
> datasoruce
> jdbc/iviewDS
> javax.sql.DataSource
> Container
>
> In my code, I lookup the datasource using 'java:/comp/env/jdbc/iviewDS'.
>
> This works well when I deploy the app into tomcat/app directory.
>
> How to solve the issue when use the plugin?
>
> Thanks
>
> Guofeng
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Maven and dependencies for $CATALINA/lib
2012/3/5 Olivier Lamy : > 2012/3/4 James Apfel : >> Hi, >> >> I'm working on a project that requires me to replace Tomcat's >> SessionManager. I've created a src/main/webapp/META-INF/context.xml >> (it defines the custom Manager) and I've edited my Maven pom file to >> include the requires JARs in the tomcat6-maven-plugin's dependencies >> section (see below) but I'm not sure if that actually refers to >> $CATALINA/lib or if these dependencies are for something else. It's >> failing with a ClassNotFoundException (it can't find the Manager class >> as defined in context.xml). > Arghh :-) > The dependencies for the tomcat start (the plugin create a class > loader with needed embeded tomcat jars) are limited to groupId > org.apache.tomcat > Can you load an issue ? https://issues.apache.org/jira/browse/MTOMCAT Thanks for the issue entry. That should be fixed now. Can you try with last 2.0-SNAPSHOT. > That's an easy fix. > >> >> Thanks, >> James >> >> >> >> >> org.apache.tomcat.maven >> tomcat6-maven-plugin >> 2.0-SNAPSHOT >> >> >> spy >> spymemcached >> 2.8.0 >> runtime >> >> >> de.javakaffee.msm >> memcached-session-manager-tc6 >> 1.6.1 >> runtime >> >> >> de.javakaffee.msm >> msm-kryo-serializer >> 1.6.0 >> runtime >> >> >> >> >> ----- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Tomcat Maven plugin] Not pulling in Test dependencies when useTestClasspath is true
2012/3/4 Nathan Schile :
> I have the plugin configured to pull in test classes and dependencies
> [1], however it doesn't seem to be pulling in my test dependencies. I
> am recieving a NoClassDefFoundError on the class from a test
> dependency, if I switch the dependency to a scope of compile, it works
> file. Any ideas?
Looks to be an issues with artifacts scoped "test".
Can you record an entry here: https://issues.apache.org/jira/browse/MTOMCAT
>
> [1]
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#useTestClasspath
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0-SNAPSHOT
>
> true
>
> ${basedir}/src/test/webapp
> true
>
>
>
> tomcat-run
>
> run
>
> pre-integration-test
>
> /
> true
> true
>
> ${basedir}/src/test/webapp
> true
> ${reserved.tomcat.port}
>
>
>
> tomcat-shutdown
>
> shutdown
>
> post-integration-test
>
>
>
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Maven and dependencies for $CATALINA/lib
2012/3/4 James Apfel : > Hi, > > I'm working on a project that requires me to replace Tomcat's > SessionManager. I've created a src/main/webapp/META-INF/context.xml > (it defines the custom Manager) and I've edited my Maven pom file to > include the requires JARs in the tomcat6-maven-plugin's dependencies > section (see below) but I'm not sure if that actually refers to > $CATALINA/lib or if these dependencies are for something else. It's > failing with a ClassNotFoundException (it can't find the Manager class > as defined in context.xml). Arghh :-) The dependencies for the tomcat start (the plugin create a class loader with needed embeded tomcat jars) are limited to groupId org.apache.tomcat Can you load an issue ? https://issues.apache.org/jira/browse/MTOMCAT That's an easy fix. > > Thanks, > James > > > > > org.apache.tomcat.maven > tomcat6-maven-plugin > 2.0-SNAPSHOT > > > spy > spymemcached > 2.8.0 > runtime > > > de.javakaffee.msm > memcached-session-manager-tc6 > 1.6.1 > runtime > > > de.javakaffee.msm > msm-kryo-serializer > 1.6.0 > runtime > > > > > --------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Apache Tomcat Maven plugin] Deploying a "jar" endstate
Hello,
Check this plugin parameter configuration:
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/run-mojo.html#ignorePackaging
HTH
2012/2/24 Nathan Schile :
> I currently have a project that has a package type of "jar" that I
> would like to run the embedded Tomcat instance on. Everything works
> fine if the package is "war", but does not work when it is "jar".
> My web.xml is located in src/test/webapp/WEB-INF/web.xml
>
> Anyone know if this is possible?
>
> Output:
> [INFO] --- tomcat7-maven-plugin:2.0-SNAPSHOT:run (default-cli) @ testJar ---
> [INFO] Skipping non-war project
>
> Plugin Configuration:
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0-SNAPSHOT
>
> true
> ${basedir}/src/test/webapp
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 Maven Plugin - embedded reload
2012/2/23 David Miller :
> I'm using the below Tomcat 7 Maven plugin and am not having any luck
> reloading changed classes. Changes made to a jsp are reflected right away
> but class file changes are not.
Frankly I have never tested that :-)
> I have my IDE (Netbeans 7) set to compile on save, I'm using Maven 2.2.1
> and I have reloadable='true' in my context.xml file.
First idea I have in mind, does your ide compile to the same
buildOutput directory as Maven ?
>
> I've not used Tomcat in years, and have never used it with Maven, so I'm
> not really sure if the problem is with the plugin or Tomcat.
>
> Can changed class files be reloaded without having to 'mvn tomcat7:run'
> each time?
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0-beta-1
>
> 5
>
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
>
>
>
> com.sybase
> jConnect
> 7.0.0
>
>
> commons-fileupload
> commons-fileupload
> 1.2.2
>
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
[ANN] Apache Tomcat Maven Plugin 2.0-beta-1 Released
Hello, The Apache Tomcat team is pleased to announce the release of Tomcat Maven Plugin 2.0-beta-1. The Apache Tomcat Maven Plugin provides goals to manipulate WAR projects within the Apache Tomcat servlet container. Documentation site: http://tomcat.apache.org/maven-plugin-2.0-beta-1/ You should specify the version in your project's plugin configuration: org.apache.tomcat.maven tomcat6-maven-plugin 2.0-beta-1 or org.apache.tomcat.maven tomcat7-maven-plugin 2.0-beta-1 Release Notes - Apache Tomcat Maven Plugin - Version 2.0-beta-1 ** New Feature * [MTOMCAT-70] - Make useNaming=false the default for the embedded Tomcat and make it configurable * [MTOMCAT-77] - Add support for using the test classpath instead of the compile classpath with tomcat:run * [MTOMCAT-87] - Make http protocol configurable for the embedded Tomcat * [MTOMCAT-102] - Add a mojo to build a standalone jar to run a web application * [MTOMCAT-110] - Support Slf4j bridge logger ** Bug * [MTOMCAT-85] - Perfoming tomcat:redeploy is not reflected in log messages * [MTOMCAT-103] - Executable War fails to run with a NullPointerException * [MTOMCAT-104] - Running java -jar from a parent directory causes a Zip file error * [MTOMCAT-106] - tomcat7-maven-plugin extraDependency not working with class not found * [MTOMCAT-108] - THe httpsPort flag starts another http thread not an https thread * [MTOMCAT-109] - org.apache.coyote.http11.Http11NioProtocol not honoured ** Improvement * [MTOMCAT-15] - Add dependency scanning support to tomcat:run * [MTOMCAT-43] - Allow configuration of URI encoding for tomcat run goals * [MTOMCAT-62] - Support Tomcat 7 * [MTOMCAT-78] - Upgrade to tomcat 6.0.32 * [MTOMCAT-95] - Add directories to the embedded tomcat classloader (equivalent to shared.loader property in regular tomcat instance). * [MTOMCAT-100] - support war overlay to add war external dependencies in tomcat run * [MTOMCAT-111] - Make extract directory configurable * [MTOMCAT-113] - Show progress on WAR uploads * [MTOMCAT-114] - Add an archetype project sample * [MTOMCAT-115] - Allow configuration of URI encoding for executable war Have Fun! -- The Apache Tomcat Team - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [Apache Tomcat Maven plugin] Howto specify the Document base ?
Hello,
See
http://tomcat.apache.org/maven-plugin-2.0-beta-1/tomcat7-maven-plugin/run-mojo.html#warSourceDirectory
So you must be able to configure the plugin :
target/${artifactId}-${version}
will be better with
${project.build.outputDirectory}/${artifactId}-${version}
2012/2/1 Blaise Gervais :
> Dear tomcat users,
>
> I try to use the Tomcat Maven
> plugin<http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/index.html>'s
> "run" goal on a webapp. The webapp is generated by
> Enunciate<http://enunciate.codehaus.org/> into
> the "*target\${artifactId}-${version}*" folder. So the tomcat plugin
> complains because it can't found the expected document base.
>
> How can I change the document base ?
>
> Thanks.
>
> GRAVE: Error starting static Resources
>> java.lang.IllegalArgumentException: Document base
>> C:\Dev\Sources\xyz\sample\src\main\webapp does not exist or is not a
>> readable directory
>> at
>> org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140)
>> at
>> org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4894)
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5074)
>> at
>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1568)
>> at
>> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1558)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>
>
> --
> Gervais Blaise
>
> Mail : gervai...@gmail.com
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7 maven plugin (frustration) - probably a simple question
Hello,
Does your current project have war packaging ? If yes, I think there
are some issues with that and btw use exec-war-only goal to prevent to
run an other full lifecycle in your war project.
What I recommend is to have an other project with packaging pom and
construct the exec war.
I have pushed samples here: https://github.com/olamy/translate-puzzle .
2011/12/27 PS M. :
> Hi there --
>
> I am frustrated with the tomcat7 maven plugin. I am trying to create an
> executable jar from my war project. The problem is that none of the war's
> dependencies are included in the executable jar even though the
> corresponding war created at the same time is complete.
>
> In the pom.xml file:
>
>
>
>
> org.apache.tomcat.maven
> tomcat7-maven-plugin
>
>
> tomcat-run
>
> exec-war
>
> package
>
> /
>
> exec-war
>
>
> jar
>
>
>
>
> com.my-company
> wireservice
>
> ${project.version}
> war
>
> /
>
>
>
> true
>
>
>
>
>
> The generated executable has a this structure:
> 820944 Mon Dec 26 18:28:42 PST 2011 .war
> 183 Mon Dec 26 18:28:42 PST 2011 tomcat.standalone.properties
> 0 Mon Dec 26 18:28:44 PST 2011 META-INF/
> 394 Mon Dec 26 18:28:44 PST 2011 META-INF/MANIFEST.MF
> 0 Mon Dec 26 18:28:44 PST 2011 javax/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/annotation/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/annotation/security/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/annotation/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/descriptor/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/http/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/jsp/
> 0 Mon Dec 26 18:28:44 PST 2011 javax/servlet/resources/
> 0 Mon Dec 26 18:28:44 PST 2011 org/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/authenticator/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/comet/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/connector/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/core/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/deploy/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/filters/
> 0 Mon Dec 26 18:28:44 PST 2011 org/apache/catalina/loader/
> ( tomcat 7 exploded into classes )
>
> The ".war" file has just the the classes in the current project included.
> No dependencies are included as jars or exploded in any other form.
>
> java -jar .jar starts tomcat but the war servlet is does not respond on
> http://localhost:8080/ and in any event it would not be able to run because
> of the missing dependencies.
>
> So 2 questions:
>
> 1. How to get the tomcat7-maven-plugin to include the war's
> dependencies. ( fyi the dependencies in question have the default scope )
> 2. How to get the path correctly so that http://localhost:8080/ is
> responded to?
>
> Thanks!
>
> Pat
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Maven Tomcat 7 plugin - changing war name
yep, not done yet :-)
It's a bit weird issue as the plugin use the project artifact (i.e.
${project.artifact} as mojo parameter expression which should point to
the war artifact of your project ).
Can you load an issue ? (I probably won't have time before end of the
week to have a look).
2011/11/22 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Will,
>
> On 11/22/11 2:02 PM, Will Glass-Husain wrote:
>> I'm struggling to get the tomcat7 plugin to work.
>
> I'm pretty sure that's still under development, so YMMV right now.
>
> Stick around and I'm sure you'll get a better answer from Olivier.
>
> I just didn't want you to beat your head against a wall for a while if
> the answer was going to be "yep, not done yet" or something like that.
>
> Can you limp-along with the XXX-YYY.war for now?
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk7ME8UACgkQ9CaO5/Lv0PC/tgCfWtubedIoK3BX8gQ8GwVqaa0H
> jQcAn2FM+DPHkTd+e8nq14/KgdlknrWB
> =lE2v
> -END PGP SIGNATURE-
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7-maven-plugin redeploy
Hello, Did you try update parameter to true [1] ? Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy [1] http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/deploy-mojo.html#update 2011/11/16 Hodchenkov, Paul : > Hi, > It's seems that new tomcat7 plugin does not have undeploy/redeploy goals. > > So deployment fails with: > -- > [ERROR] BUILD ERROR > [INFO] -- > -- > [INFO] Cannot invoke Tomcat manager: FAIL - Application already exists at > path / > > Is it possible to undeploy/redeploy app using apache tomcat7 plugin? Should I > revert back to codehaus plugin? > > -Original Message- > From: Jesse Farinacci [mailto:jie...@gmail.com] > Sent: Wednesday, November 16, 2011 4:21 AM > To: Tomcat Users List > Subject: Re: tomcat7-maven-plugin redeploy > > Greetings, > > On Tue, Nov 15, 2011 at 6:13 PM, David Yu wrote: >> Is there a redeploy goal for the tomcat7 plugin? I'm trying to re-deploy >> a war file that has already been deployed and built to my remote tomcat >> server. Thanks. > > New development is at: > > http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html > > Old deprecated plugin is at: > > http://mojo.codehaus.org/tomcat-maven-plugin/plugin-info.html > http://mojo.codehaus.org/tomcat-maven-plugin/redeploy-mojo.html > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Set docBase in pom.xml for maven tomcat plugin
2011/11/2 Bin Lan :
> Hi Olivier,
>
> I followed the instruction on
> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html, and
> use tomcat6:run instead of tomcat:run and now the plugin is using the path
> in warSourceDirectory.
>
> Quick question, is this gonna be part of the next release?
As it's in trunk sure will be in next release :-)
>
> Thank you very much.
>
> Regards
> Bin
>
>
>
> On Wed, Nov 2, 2011 at 7:32 AM, Olivier Lamy wrote:
>
>> Can you try with last changes I have pushed ?
>> You need to build locally from sources. (some network issues for
>> *.apache.org so I cannot deploy snapshots)
>>
>> 2011/11/2 Bin Lan :
>> > Forgot to mention that I am using 2.0-snapshot.
>> > On Nov 2, 2011 7:20 AM, "Bin Lan" wrote:
>> >
>> >> Hi Olivier,
>> >>
>> >> Thank you for you reply. I run maven in cli not in ecclipse. Since the
>> >> project is a eclipse native dynamc web project, so I gues eclipse has
>> its
>> >> own way to handle it. But regardless, the warSourceDirectory did not
>> change
>> >> the docBase for me.
>> >>
>> >> Regards
>> >> Bin
>> >> On Nov 2, 2011 5:08 AM, "Olivier Lamy" wrote:
>> >>
>> >>> Hello,
>> >>> Yup that's the correct ml.
>> >>> Did you try with last trunk version from ASF (tomcat6/7 mojos) ?
>> >>> For how to test that: see
>> >>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
>> >>>
>> >>> Yup normally warSourceDirectory should do the job.
>> >>> Honestly I test more with cli (and not an eclipse user :-) ).
>> >>> Do you have issues running that with cli ?
>> >>>
>> >>> 2011/11/2 Bin Lan :
>> >>> > Hi all,
>> >>> >
>> >>> > I hope this message reaches the right user group. My question is
>> pretty
>> >>> > simple. In maven-tomcat-plugin, how can I set the docBase path?
>> >>> Currently,
>> >>> > my project is a Eclipse dynamic web project and all the webapp files
>> are
>> >>> > being stored inside ${basedir}/WebContent folder. Whenever I tried
>> mvn
>> >>> > tomcat:run, I got an IllegalArgumentException saying that the
>> >>> > ${basedir}/src/main/webapp does not exists or is not readable. Is
>> there
>> >>> a
>> >>> > way that I can set it inside pom.xml? I tried
>> but
>> >>> it
>> >>> > is not doing what I want.
>> >>> >
>> >>> > Thanks in advance.
>> >>> >
>> >>> > Regards
>> >>> > Bin
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olivier Lamy
>> >>> Talend : http://talend.com
>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> >>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> >>>
>> >>>
>> >
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend : http://talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
--
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Set docBase in pom.xml for maven tomcat plugin
Can you try with last changes I have pushed ?
You need to build locally from sources. (some network issues for
*.apache.org so I cannot deploy snapshots)
2011/11/2 Bin Lan :
> Forgot to mention that I am using 2.0-snapshot.
> On Nov 2, 2011 7:20 AM, "Bin Lan" wrote:
>
>> Hi Olivier,
>>
>> Thank you for you reply. I run maven in cli not in ecclipse. Since the
>> project is a eclipse native dynamc web project, so I gues eclipse has its
>> own way to handle it. But regardless, the warSourceDirectory did not change
>> the docBase for me.
>>
>> Regards
>> Bin
>> On Nov 2, 2011 5:08 AM, "Olivier Lamy" wrote:
>>
>>> Hello,
>>> Yup that's the correct ml.
>>> Did you try with last trunk version from ASF (tomcat6/7 mojos) ?
>>> For how to test that: see
>>> http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
>>>
>>> Yup normally warSourceDirectory should do the job.
>>> Honestly I test more with cli (and not an eclipse user :-) ).
>>> Do you have issues running that with cli ?
>>>
>>> 2011/11/2 Bin Lan :
>>> > Hi all,
>>> >
>>> > I hope this message reaches the right user group. My question is pretty
>>> > simple. In maven-tomcat-plugin, how can I set the docBase path?
>>> Currently,
>>> > my project is a Eclipse dynamic web project and all the webapp files are
>>> > being stored inside ${basedir}/WebContent folder. Whenever I tried mvn
>>> > tomcat:run, I got an IllegalArgumentException saying that the
>>> > ${basedir}/src/main/webapp does not exists or is not readable. Is there
>>> a
>>> > way that I can set it inside pom.xml? I tried but
>>> it
>>> > is not doing what I want.
>>> >
>>> > Thanks in advance.
>>> >
>>> > Regards
>>> > Bin
>>> >
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend : http://talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>
>>>
>
--
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Set docBase in pom.xml for maven tomcat plugin
Hello,
Yup that's the correct ml.
Did you try with last trunk version from ASF (tomcat6/7 mojos) ?
For how to test that: see
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/snapshot-test.html
Yup normally warSourceDirectory should do the job.
Honestly I test more with cli (and not an eclipse user :-) ).
Do you have issues running that with cli ?
2011/11/2 Bin Lan :
> Hi all,
>
> I hope this message reaches the right user group. My question is pretty
> simple. In maven-tomcat-plugin, how can I set the docBase path? Currently,
> my project is a Eclipse dynamic web project and all the webapp files are
> being stored inside ${basedir}/WebContent folder. Whenever I tried mvn
> tomcat:run, I got an IllegalArgumentException saying that the
> ${basedir}/src/main/webapp does not exists or is not readable. Is there a
> way that I can set it inside pom.xml? I tried but it
> is not doing what I want.
>
> Thanks in advance.
>
> Regards
> Bin
>
--
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] Tomcat on its own SVN repository?
If you need a git clone use: https://github.com/apache/ and search clone started with tomcat 2011/9/29 Francis GALIEGUE : > Hello list, > > I was trying to get the source code in order to implement my own idea > of a remote address valve (as mentioned in a previous thread). > > But I use git-svn, and discovered that Tomcat is on a repository with > 1M+ changes on it! git svn clone is therefore woefully impractical. Is > there any plan to move each project at least to its own SVN repo, if > not git? > > -- > Francis Galiegue > ONE2TEAM > Ingénieur système > Mob : +33 (0) 683 877 875 > Tel : +33 (0) 178 945 552 > f...@one2team.com > 40 avenue Raymond Poincaré > 75116 Paris > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Weird stack trace when reloading a webapp
Ok I will search and try reordering filters.
Thanks for your time !
--
Olivier
2008/8/8 Johnny Kewl <[EMAIL PROTECTED]>:
>
> - Original Message - From: "Olivier Lamy" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Thursday, August 07, 2008 11:21 PM
> Subject: Re: Weird stack trace when reloading a webapp
>
>
>> Hi,
>> Thanks for your reponse but undeploy/redeploy don't save me same issue
>> :-(.
>
> Damn! I was hoping ;)
>
> Well... it looks like a struts framework so I think you need to ask some
> question in their mailing lists...
> All I can tell from this is that they seem to be hiding xerces in the
> META-INF folder...
> and they have a custom classloader trying to access it
> You seem to be making a filter... and the framework seems to want a web app
> for its classloader... but the webapp is down.
>
> So you calling Tiles or something... and that wants to live in a webapp, but
> you in a filter... maybe, but its the kind of thing that should be showing
> in your dev env?
> Is it your application? If not ask the supplier...
>
> Some guesses for you... the order of filters is important... maybe yours
> should be behind all the framework filters...
> Perhaps will get the webapp with all this framework stuff in
> it to start and make the cl happy.
>
> Thats the problem with frameworks... always have to ask more than one user
> group ;)
>
> Its a tricky problem I think and you'll have to talk to the guys that made
> your frameworks...
>
> Good luck... Sorry... outta idea's, maybe google will get you there
>
>> Olivier
>>
>> 2008/8/7 Johnny Kewl <[EMAIL PROTECTED]>:
>>>
>>> - Original Message - From: "Olivier Lamy" <[EMAIL PROTECTED]>
>>> To:
>>> Sent: Thursday, August 07, 2008 5:17 PM
>>> Subject: Weird stack trace when reloading a webapp
>>>
>>>
>>>> Hi,
>>>> I use the ant deploy target :
>>>> >>> password="${tomcat.password}"
>>>> path="/{webPath}" localWar="${warPath}" update="true"
>>>> config="${contextPath}" />
>>>>
>>>> But in catalina.out, I have the following stack trace :
>>>>
>>>> INFO: Deploying web application archive dotw-trans.war
>>>> 2008-08-07 15:04:38,942 INFO impl.BasicTilesContainer : Initializing
>>>> Tiles2 container. . .
>>>> 2008-08-07 15:04:39,177 INFO impl.BasicTilesContainer : Tiles2
>>>> container initialization complete.
>>>> 2008-08-07 15:04:39,185 INFO access.TilesAccess : Publishing
>>>> TilesContext for context: org.apache.catalina.core.Appli
>>>> cationContextFacade
>>>> 2008-08-07 15:04:39,247 INFO filter.DotwFilterDispatcher : init
>>>> DotwFilterDispatcher with encoding : UTF-8
>>>> Aug 7, 2008 3:04:40 PM org.apache.catalina.loader.WebappClassLoader
>>>> findResourceInternal
>>>> INFO: Illegal access: this web application instance has been stopped
>>>> already. Could not load META-INF/services/org.ap
>>>> ache.xerces.xni.parser.XMLParserConfiguration. The eventual following
>>>> stack trace is caused by an error thrown for de
>>>> bugging purposes as well as to attempt to terminate the thread which
>>>> caused the illegal access, and has no functional
>>>> impact.
>>>> Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start
>>>> SEVERE: Error filterStart
>>>> Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start
>>>> SEVERE: Context [/dotw-trans] startup failed due to previous errors
>>>>
>>>> Any idea on the Could not load
>>>> META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration.
>>>>
>>>> My en is :
>>>> - apache-tomcat-6.0.18
>>>> - jdk1.6.0_06
>>>> - solaris 10
>>>>
>>>> Any idea ?
>>>>
>>>> Thanks,
>>>> --
>>>> Olivier
>>>
>>> Oliver is that the whole error message or did you abreviate it?
>>> Does is say anything about a POST...
>>>
>>> I tell you why, on complex applications I've seen something similar...
>>>
>>> Anyway try this before you redeploy... open /manager/html and
>>> UNDEPLOY
>>> the old one... then run your script...
>>> If it is the same thing... you wont get the error because its actually
Re: Weird stack trace when reloading a webapp
Hi,
Thanks for your reponse but undeploy/redeploy don't save me same issue :-(.
--
Olivier
2008/8/7 Johnny Kewl <[EMAIL PROTECTED]>:
>
> - Original Message ----- From: "Olivier Lamy" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, August 07, 2008 5:17 PM
> Subject: Weird stack trace when reloading a webapp
>
>
>> Hi,
>> I use the ant deploy target :
>> > password="${tomcat.password}"
>> path="/{webPath}" localWar="${warPath}" update="true"
>> config="${contextPath}" />
>>
>> But in catalina.out, I have the following stack trace :
>>
>> INFO: Deploying web application archive dotw-trans.war
>> 2008-08-07 15:04:38,942 INFO impl.BasicTilesContainer : Initializing
>> Tiles2 container. . .
>> 2008-08-07 15:04:39,177 INFO impl.BasicTilesContainer : Tiles2
>> container initialization complete.
>> 2008-08-07 15:04:39,185 INFO access.TilesAccess : Publishing
>> TilesContext for context: org.apache.catalina.core.Appli
>> cationContextFacade
>> 2008-08-07 15:04:39,247 INFO filter.DotwFilterDispatcher : init
>> DotwFilterDispatcher with encoding : UTF-8
>> Aug 7, 2008 3:04:40 PM org.apache.catalina.loader.WebappClassLoader
>> findResourceInternal
>> INFO: Illegal access: this web application instance has been stopped
>> already. Could not load META-INF/services/org.ap
>> ache.xerces.xni.parser.XMLParserConfiguration. The eventual following
>> stack trace is caused by an error thrown for de
>> bugging purposes as well as to attempt to terminate the thread which
>> caused the illegal access, and has no functional
>> impact.
>> Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start
>> SEVERE: Error filterStart
>> Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start
>> SEVERE: Context [/dotw-trans] startup failed due to previous errors
>>
>> Any idea on the Could not load
>> META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration.
>>
>> My en is :
>> - apache-tomcat-6.0.18
>> - jdk1.6.0_06
>> - solaris 10
>>
>> Any idea ?
>>
>> Thanks,
>> --
>> Olivier
>
> Oliver is that the whole error message or did you abreviate it?
> Does is say anything about a POST...
>
> I tell you why, on complex applications I've seen something similar...
>
> Anyway try this before you redeploy... open /manager/html and UNDEPLOY
> the old one... then run your script...
> If it is the same thing... you wont get the error because its actually
> happening in the undeploy...
> If that works then add another section to your ant script... first
> undeploy... then redeploy...
>
> If it is the same thing... I've only noticed it on very complex apps
> Other thing I've noticed is that even when you get this weird message... the
> redeploy does work.
> And you cant debug it... because TC is killing the thing... ide wont trap
> it...
> And I think it only happens when there are classloaders in the webapp
> classloader... which would explain why the webapp class loader cant let
> go... the child still has references... anyway try the above, and I dont
> think its too serious... its a last complaint before it gets a bullet
> between the eyes ;)
>
> maybe its the same thing...
> ---
> HARBOR : http://www.kewlstuff.co.za/index.htm
> The most powerful application server on earth.
> The only real POJO Application Server.
> See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
> ---
>
>
>
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Weird stack trace when reloading a webapp
Hi, I use the ant deploy target : But in catalina.out, I have the following stack trace : INFO: Deploying web application archive dotw-trans.war 2008-08-07 15:04:38,942 INFO impl.BasicTilesContainer : Initializing Tiles2 container. . . 2008-08-07 15:04:39,177 INFO impl.BasicTilesContainer : Tiles2 container initialization complete. 2008-08-07 15:04:39,185 INFO access.TilesAccess : Publishing TilesContext for context: org.apache.catalina.core.Appli cationContextFacade 2008-08-07 15:04:39,247 INFO filter.DotwFilterDispatcher : init DotwFilterDispatcher with encoding : UTF-8 Aug 7, 2008 3:04:40 PM org.apache.catalina.loader.WebappClassLoader findResourceInternal INFO: Illegal access: this web application instance has been stopped already. Could not load META-INF/services/org.ap ache.xerces.xni.parser.XMLParserConfiguration. The eventual following stack trace is caused by an error thrown for de bugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start SEVERE: Error filterStart Aug 7, 2008 3:04:40 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/dotw-trans] startup failed due to previous errors Any idea on the Could not load META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration. My en is : - apache-tomcat-6.0.18 - jdk1.6.0_06 - solaris 10 Any idea ? Thanks, -- Olivier - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
