You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2005/07/08 13:13:40 UTC
cocoon-refdoc initial code is in the whiteboard
Hi everybody,
I've just committed some code for the cocoon-refdoc project at
http://svn.apache.org/repos/asf/cocoon/whiteboard/refdoc/ , see also
http://wiki.apache.org/cocoon/CocoonRefDocProject
This is meant mainly for Robert Graham who's working on the GSoC
cocoon-refdoc project, but of course everybody's welcome to have a
look.
See README.TXT there for how to test it. It's a rough prototype which
hopefully shows the main idea, it's more or less ready to start working
on the Lucene indexing (by feeding the XML snippets to Lucene and
having it index the snippet's elements), but I haven't had time to
really test this.
I'll be offline next week, it would be cool if people can help Robert
if he's stuck with this junk^H^H^H^Hrough initial code. Ross Gardler is
the official co-mentor on the cocoon-refdoc project, but the goal is to
immerse our GSoC students in our community, so everybody's welcome to
help and talk!
-Bertrand
Re: cocoon-refdoc initial code is in the whiteboard
Posted by Reinhard Poetz <re...@apache.org>.
Robert Graham wrote:
> I'm a little confused as to how the wildcard matchers work here:
>
> With a given URI snippets/samples/subdir/dummy-sitemap.xweb
>
> {global.codebase} = ../annotated-code
> That folder contains the files referenced by the pipeline.
>
> <map:match pattern="*/**.*">
> <map:generate type="slop" src="{global:codebase}/{2}.{3}">
>
> Here we have four asterisks. By my understanding {1}, {2}, {3}, and
> {4} respectively from left to right. Now {2}.{3} in this case is
> "dummy-sitemap.xweb" because {2} is the filename and {3} the
> extension, but from my understanding the last asterisk should match
> the extension. This isn't the case, but I was hoping someone could
> better elucidate the wildcard matching sequence there.
<map:match pattern="*/**.*">
1 2 3
a double asterisk is *one* match. The difference to a single asterisk is, that a
double asterisk also matches slashes.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: cocoon-refdoc initial code is in the whiteboard
Posted by Robert Graham <in...@gmail.com>.
I'm a little confused as to how the wildcard matchers work here:
With a given URI snippets/samples/subdir/dummy-sitemap.xweb
{global.codebase} = ../annotated-code
That folder contains the files referenced by the pipeline.
<map:match pattern="*/**.*">
<map:generate type="slop" src="{global:codebase}/{2}.{3}">
Here we have four asterisks. By my understanding {1}, {2}, {3}, and
{4} respectively from left to right. Now {2}.{3} in this case is
"dummy-sitemap.xweb" because {2} is the filename and {3} the
extension, but from my understanding the last asterisk should match
the extension. This isn't the case, but I was hoping someone could
better elucidate the wildcard matching sequence there.
Thanks,
Robert
Re: cocoon-refdoc initial code is in the whiteboard
Posted by Ben Pope <be...@gmail.com>.
Robert Graham wrote:
> I grabbed the trunk off of SVN and the whiteboard and tried to build
> this, but it failed trying to build the javadocs and I'm not sure why.
> I thought someone might be able to enlighten me.I've got 2.1 running
> on the same setup and have no trouble building it. I've edited it for
> simplicity as best I can:
>
> BUILD FAILED
> {COCOONDIR}\docs-build.xml:57: The following error occurred while
> executing this line:
> {COCOONDIR}\...\blocks-build.xml:641: Javadoc failed:
> java.io.IOException: CreateProcess: "{DIR}\...\javadoc.exe" -J-Xmx192m
> -stylesheetfile "{DIR}\...\trunk\src\resources\javadoc\javadoc.css"
> -windowtitle "Cocoon API 2.2.0-dev [July 9 2005]" -splitindex -use -d
> "{DIR}\...\trunk\build\cocoon\javadocs" -doctitle "Cocoon API
> 2.2.0-dev" -classpath "{DIR}\...\trunk\tools\lib\ant-contrib-0.6.jar;
> DIR\...\trunk\tools\lib\ant-junit.jar; ....etc.
Last I heard, you can't use the ant build to build the docs in trunk, that might have chnged by now. Just disable the docs to get the rest of cocoon built.
Ben
Re: cocoon-refdoc initial code is in the whiteboard
Posted by Robert Graham <in...@gmail.com>.
I grabbed the trunk off of SVN and the whiteboard and tried to build
this, but it failed trying to build the javadocs and I'm not sure why.
I thought someone might be able to enlighten me.I've got 2.1 running
on the same setup and have no trouble building it. I've edited it for
simplicity as best I can:
BUILD FAILED
{COCOONDIR}\docs-build.xml:57: The following error occurred while
executing this line:
{COCOONDIR}\...\blocks-build.xml:641: Javadoc failed:
java.io.IOException: CreateProcess: "{DIR}\...\javadoc.exe" -J-Xmx192m
-stylesheetfile "{DIR}\...\trunk\src\resources\javadoc\javadoc.css"
-windowtitle "Cocoon API 2.2.0-dev [July 9 2005]" -splitindex -use -d
"{DIR}\...\trunk\build\cocoon\javadocs" -doctitle "Cocoon API
2.2.0-dev" -classpath "{DIR}\...\trunk\tools\lib\ant-contrib-0.6.jar;
DIR\...\trunk\tools\lib\ant-junit.jar; ....etc.
Thanks,
Robert