Berin Loritsch wrote:
>Leif Mortenson wrote:
>
>>I tried running build dist on jakarta-avalon and
>>jakarta-avalon-excalibur today and
>>am getting failures from cocoon like those that follows. Haven't run
>>this in a week
>>or so I think, but it was working correctly before.
>>
>>Is this a setup problem on my machine or are others seeing this as well?
>>
>
>Look in the build/work directory, you should see a cocoon.log file.
>That log file is your friend. What possible errors are you seeing
>there? It could be with the ExcaliburComponentSelector (i.e. you
>placed a change in the ECM, but forgot to apply it to ECS).
>
It does not exist. The build file is specifying it and it is getting
passed as an argument
when Java is launched. But cocoon seems to be ignoring it. This is
working on your machine?
The build.xml definition looks like this:
<java classname="org.apache.cocoon.Main" fork="true" maxmemory="128m">
<arg value="-c${build.context}/"/>
<arg value="-d${build.docs}"/>
<arg value="-w${build.dir}/work"/>
<arg value="-l${build.dir}/work/cocoon.log"/>
<arg value="-uINFO"/>
<arg value="index.html"/>
<classpath>
<path refid="tools.class.path"/>
<fileset dir="${tools.dir}/ext"/>
</classpath>
</java>
Looking at the cocoon source at:
http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/java/org/apache/cocoon/Main.java?rev=1.17&content-type=text/vnd.viewcvs-markup
it looks like the -l parameter is used to specify the name of a logkit
logger, not a file name.
And then it is only used if the -k parameter which specifies the logkit
config file to use is specified.
changing the -u argument to -uDEBUG gives me lots more information, but
I am afraid that I do
not speak cocoon well enough to see what the problem is :-/ It looks
like cocoon is generating
a class org.apache.cocoon.www.sitemap_xmap This class is then trying to
lookup components
which it is failing to find.
I don't have any ECM/ECS changes on my machine...
Leif
