Antonio Gallardo wrote:
I think I got the source of the problem: some transformers has bad
written javadocs that don't use the agreed format. Please do an SVN update
to see if it changes in your case too. Now I am getting a diferent one
after adding a new tag in the Includetranformer:
Antonio Gallardo wrote:
Hi David:
4:00 a.m. here! :-(
I guess I found and fixed the source error. (Am I telling the same again?
- lol.).
:-)
There you go, doing one of your super-human efforts again.
Thanks, that is an excellent step forward.
--David
Antonio Gallardo wrote:
Hi David:
4:00 a.m. here! :-(
I guess I found and fixed the source error. (Am I telling the same again?
- lol.).
I did some System.out of the process (included in the commit). Made a
workaround hack and I will commit. The hack works. :-D
No difference for me.
On Mie, 12 de Enero de 2005, 7:01, Geoff Howard dijo:
On Wed, 12 Jan 2005 16:57:31 +1100, David Crossley [EMAIL PROTECTED]
wrote:
Antonio Gallardo wrote:
Can you post where the problem is showed to you trying a full build? I
am
trying to get an idea if the problem is truly random or just
Geoff Howard wrote:
David Crossley wrote:
Antonio Gallardo wrote:
Can you post where the problem is showed to you trying a full build? I am
trying to get an idea if the problem is truly random or just because users
have diferent blocks configurations in local.blocks.properties. The
On Mie, 12 de Enero de 2005, 23:00, David Crossley dijo:
David Crossley wrote:
Antonio Gallardo wrote:
[snip]
I did some System.out of the process (included in the commit). Made a
workaround hack and I will commit. The hack works. :-D
No difference for me. Doing 'build clean, build' still
I am getting the same problem, but with :
BUILD FAILED
/Users/jerm/Development/Checkouts/Apache/Cocoon/trunk/tools/targets/
docs-build.xml:55: Sitemap component
org.apache.cocoon.generation.NekoHTMLGenerator does not implement a
sitemap component interface.
This was after a ./build.sh clean
Jeremy Quinn wrote:
I am getting the same problem, but with :
BUILD FAILED
/Users/jerm/Development/Checkouts/Apache/Cocoon/trunk/tools/targets/
docs-build.xml:55: Sitemap component
org.apache.cocoon.generation.NekoHTMLGenerator does not implement a
sitemap component interface.
I may be at
odd that this is breaking in different places for everyone. Do you
all have different sets of blocks enabled?
If not, I'm suspicious of out of memory error or something odd like
that. In that case, any chance that the docs build tasks could mask
some odd condition like that with such an error?
Geoff Howard wrote:
odd that this is breaking in different places for everyone. Do you
all have different sets of blocks enabled?
I have all blocks enabled.
If not, I'm suspicious of out of memory error or something odd like
that. In that case, any chance that the docs build tasks could
David Crossley wrote:
Geoff Howard wrote:
odd that this is breaking in different places for everyone. Do you
all have different sets of blocks enabled?
I have all blocks enabled.
Mine is an unmodified checkout of SVN head.
Ross
--
No virus found in this outgoing message.
Checked by AVG
On Mar, 11 de Enero de 2005, 10:55, Geoff Howard dijo:
odd that this is breaking in different places for everyone. Do you
all have different sets of blocks enabled?
Seems like have to do with diferent blocks enabled ;-)
In my case (a full build):
BUILD FAILED
Antonio Gallardo wrote:
The lastest changes of docs-build.xml (SVN 124702):
http://marc.theaimsgroup.com/?l=xml-cocoon-cvsm=110523951602586w=2
from:
sitemap-components docDir=${build.context}/xdocs/userdocs
source=${java}/
to:
sitemap-components
On Mar, 11 de Enero de 2005, 23:35, David Crossley dijo:
It is being done as part of the documentation effort.
http://cocoon.apache.org/2.1/plan/review-sitemap-docs.html
It is not the cause, it just enables to bug to manifest.
OK.
Can you post where the problem is showed to you trying a full
Antonio Gallardo wrote:
David Crossley dijo:
It is not the cause, it just enables to bug to manifest.
OK.
Can you post where the problem is showed to you trying a full build? I am
trying to get an idea if the problem is truly random or just because users
have diferent blocks
On Mar, 11 de Enero de 2005, 23:57, David Crossley dijo:
I showed that a few messages ago in this thread.
Both Ross and i are doing a full build, javadocs and all,
with no blocks disabled. It breaks in different places
for each of us.
Then the problem is somewhere in the Ant task:
Ralph Goers wrote:
David Crossley wrote:
I showed that a few messages ago in this thread.
Both Ross and i are doing a full build, javadocs and all,
with no blocks disabled. It breaks in different places
for each of us.
Does it fail for you in BRANCH_2_1_X (before you disabled it) in the
On Mie, 12 de Enero de 2005, 1:27, David Crossley dijo:
Ralph Goers wrote:
David Crossley wrote:
I showed that a few messages ago in this thread.
Both Ross and i are doing a full build, javadocs and all,
with no blocks disabled. It breaks in different places
for each of us.
Does it fail
The Cocoon SitemapTask in trunk is suddenly throwing a wobbly.
-
...
Building component docs from blocks.
Collecting sitemap components info
BUILD FAILED
/opt/cocoon-trunk/tools/targets/docs-build.xml:55:
Sitemap component org.apache.cocoon.generation.HTMLGenerator
does not
Carsten Ziegeler wrote:
David Crossley wrote:
That is the trouble - i don't know what is correct.
:)
The file called components-javadoc-sitemaptask-diff.txt
is the difference between the list produced by scanning
javadocs (finding extra clutter, maybe missing some) and the
list
David Crossley wrote:
So if I read the diff correctly, these classes are not found by the
sitemap
task:
65a64,71
org/apache/cocoon/components/pipeline/impl/AbstractCachingProcessingPi
peline
org/apache/cocoon/components/pipeline/impl/BaseCachingProcessingPipe
line
Carsten Ziegeler wrote:
David Crossley wrote:
Okay, i uploaded them to my ASF committer space
www.apache.org ~crossley/review-sitemap-docs/ See the notes
in SVN cocoon-2_1_X/tools/review-sitemap-docs/README.txt
and cocoon-2_1_X/tools/review-sitemap-docs/TODO.txt
Thanks!!
So if
David Crossley wrote:
I am working on this in cocoon-2_1_X branch.
In tools/targets/docs-build.xml uncomment the
sitemap-components task at line 56 to also scan the blocks.
Then run 'build javadocs'.
Then run 'build docs'. This will also produce lists of all
possible sitemap components
Carsten Ziegeler wrote:
David Crossley wrote:
I am working on this in cocoon-2_1_X branch.
In tools/targets/docs-build.xml uncomment the
sitemap-components task at line 56 to also scan the blocks.
Then run 'build javadocs'.
Then run 'build docs'. This will also produce lists of
David Crossley wrote:
Okay, i uploaded them to my ASF committer space
www.apache.org ~crossley/review-sitemap-docs/ See the notes
in SVN cocoon-2_1_X/tools/review-sitemap-docs/README.txt
and cocoon-2_1_X/tools/review-sitemap-docs/TODO.txt
Thanks!!
So if I read the diff correctly, these
Carsten Ziegeler wrote:
David Crossley wrote:
...
which misses src/java/o/a/c/serialization/XMLSerializer.java
perhaps because that extends AbstractTextSerializer.
Ah, ok, that's strange. My understanding was that this should work
and if I'm not mistaken it works for other classes.
David Crossley wrote:
Bertrand Delacretaz wrote:
Upayavira a écrit :
...cd build/cocoon-2.1.7-dev/javadocs/
grep -rl SitemapModelComponent *
Good one! Here's the pretty listing then:
for i in $(grep -rl SitemapModelComponent * | grep org/apache)
do
echo $i | sed 's/\//\./g' | sed 's/\.html$//'
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...Using the grep javadocs method does not find any
serializers, actions, matchers, selectors.
Why, can't you grep their base interfaces like:
for i in $(egrep -rl 'SitemapModelComponent|OtherBaseInterface|Other)
?
Oh, i haven't tried
David Crossley wrote:
Thanks, that will be suitable. Fiddling with the SitemapTask.java i
can also getting a listing.
So i will be able to work out a solution. Thanks.
Hmmm, no joy so far.
Using the grep javadocs method does not find any serializers,
actions, matchers, selectors.
Carsten Ziegeler wrote:
David Crossley wrote:
...Fiddling with the SitemapTask.java i can also
getting a listing.
So i will be able to work out a solution. Thanks.
Hmmm, no joy so far.
Using the grep javadocs method does not find any serializers,
actions, matchers, selectors.
David Crossley wrote:
Welcome back Carsten. You probably have stacks of email to
catch up with.
Yes I had, now I'm done to 50 (I just deleted all the stuff dealing
with jxtg, tags, templates blabla :) )
Here is the reason for my questions.
Re: review of sitemap component documentation
Le 13 déc. 04, à 09:20, David Crossley a écrit :
...Using the grep javadocs method does not find any
serializers, actions, matchers, selectors.
Why, can't you grep their base interfaces like:
for i in $(egrep -rl 'SitemapModelComponent|OtherBaseInterface|Other)
?
Also, how about defining a
Upayavira wrote:
David Crossley wrote:
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...Using the grep javadocs method does not find any
serializers, actions, matchers, selectors.
Why, can't you grep their base interfaces like:
for i in $(egrep -rl
David Crossley wrote:
Geoff Howard wrote:
I'd just use eclipse to find every class that implements the right
interface(s). Would that work?
Thanks Geoff. However, command-line tools only
because i need to script it. Sorry, i forgot
to specify that.
A bit of BCEL should do the trick.
I'd just use eclipse to find every class that implements the right
interface(s). Would that work?
Geoff
On Thu, 09 Dec 2004 10:46:36 +1100, David Crossley [EMAIL PROTECTED] wrote:
I am trying to create a list of all sitemap
components in the Cocoon core and blocks.
So far i have tried to
Geoff Howard wrote:
I'd just use eclipse to find every class that implements the right
interface(s). Would that work?
Or, what we need is a tool that lists all the interfaces that a class
implements. Hmm. Javadoc. For the CastorTransformer, you get a line saying:
*All Implemented
Le 9 déc. 04, à 00:46, David Crossley a écrit :
I am trying to create a list of all sitemap
components in the Cocoon core and blocks...
Doesn't qdox list the interfaces that a class implements?
If it's the case, it should be possible to create a pipeline (using the
qdox block) or use the qdox ant
Bertrand Delacretaz wrote:
Le 9 déc. 04, à 00:46, David Crossley a écrit :
I am trying to create a list of all sitemap
components in the Cocoon core and blocks...
Doesn't qdox list the interfaces that a class implements?
If it's the case, it should be possible to create a pipeline (using
the
Le 9 déc. 04, à 16:56, Upayavira a écrit :
...cd build/cocoon-2.1.7-dev/javadocs/
grep -rl SitemapModelComponent *
Good one! Here's the pretty listing then:
for i in $(grep -rl SitemapModelComponent * | grep org/apache)
do
echo $i | sed 's/\//\./g' | sed 's/\.html$//'
done
There's still a bit of
Geoff Howard wrote:
I'd just use eclipse to find every class that implements the right
interface(s). Would that work?
Thanks Geoff. However, command-line tools only
because i need to script it. Sorry, i forgot
to specify that.
--David
Bertrand Delacretaz wrote:
Upayavira a écrit :
...cd build/cocoon-2.1.7-dev/javadocs/
grep -rl SitemapModelComponent *
Good one! Here's the pretty listing then:
for i in $(grep -rl SitemapModelComponent * | grep org/apache)
do
echo $i | sed 's/\//\./g' | sed 's/\.html$//'
done
There's still a
I am trying to create a list of all sitemap
components in the Cocoon core and blocks.
So far i have tried to use 'find and grep'
by looking for well-known filenames,
e.g. *Transformer.java and also searching in
well-known directories, e.g. /transformation/
However, that misses some components and
42 matches
Mail list logo
