You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Florian Maertl <Fl...@macquarie.com> on 2012/09/17 14:59:14 UTC
warDirectory property wrong evaluated in release version 2.0 ?
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" property in my pom, it
works:
<configuration>
<warDirectory>${project.build.directory}/${project.build.finalName}</war
Directory>
</configuration>
With version 2.0-beta-1 it worked without this configuration.
For me it looks like if the standard value is defined wrongly.
Does anybody else see this error?
Or is the cause something else?
Thanks
Florian
Re: warDirectory property wrong evaluated in release version 2.0 ?
Posted by Olivier Lamy <ol...@apache.org>.
Thanks it's now fixed.
2012/9/17 Florian Maertl <Fl...@macquarie.com>:
> Jira is raised:
>
> https://issues.apache.org/jira/browse/MTOMCAT-175
>
> Thanks
> Florian
>
> -----Original Message-----
> From: Olivier Lamy [mailto:olamy@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 <Fl...@macquarie.com>:
>> 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" property in my pom, it
>> works:
>>
>>
>>
>> <configuration>
>>
>>
>>
> <warDirectory>${project.build.directory}/${project.build.finalName}</war
>> Directory>
>>
>> </configuration>
>>
>>
>>
>> With version 2.0-beta-1 it worked without this configuration.
>>
>>
>>
>> For me it looks like if the standard value is defined wrongly.
>>
>>
>>
>> Does anybody else see this error?
>>
>> Or is the cause something else?
>>
>>
>>
>> Thanks
>>
>> Florian
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: warDirectory property wrong evaluated in release version 2.0 ?
Posted by Florian Maertl <Fl...@macquarie.com>.
Jira is raised:
https://issues.apache.org/jira/browse/MTOMCAT-175
Thanks
Florian
-----Original Message-----
From: Olivier Lamy [mailto:olamy@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 <Fl...@macquarie.com>:
> 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" property in my pom, it
> works:
>
>
>
> <configuration>
>
>
>
<warDirectory>${project.build.directory}/${project.build.finalName}</war
> Directory>
>
> </configuration>
>
>
>
> With version 2.0-beta-1 it worked without this configuration.
>
>
>
> For me it looks like if the standard value is defined wrongly.
>
>
>
> Does anybody else see this error?
>
> Or is the cause something else?
>
>
>
> Thanks
>
> Florian
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: warDirectory property wrong evaluated in release version 2.0 ?
Posted by Olivier Lamy <ol...@apache.org>.
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 <Fl...@macquarie.com>:
> 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" property in my pom, it
> works:
>
>
>
> <configuration>
>
>
> <warDirectory>${project.build.directory}/${project.build.finalName}</war
> Directory>
>
> </configuration>
>
>
>
> With version 2.0-beta-1 it worked without this configuration.
>
>
>
> For me it looks like if the standard value is defined wrongly.
>
>
>
> Does anybody else see this error?
>
> Or is the cause something else?
>
>
>
> Thanks
>
> Florian
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org