Vadim Gritsenko wrote:
Ross Gardler wrote:
Vadim Gritsenko wrote:
Forgot to add... Can we loose page toc which now appears within left
navigation bar? I'm not sure we should have it there, it certainly
looks strange...
It was moved there as a test, come people like it in the body, come
Vadim Gritsenko wrote:
Hm, why some files are there twice? Example:
/developing/concepts/avalon.html
/documentation/developing/concepts/avalon.html
I know why. It is because the forrestbot didn't clean
out its workspace on the server. So the old generated
documents are still included.
David Crossley wrote:
Double Uh'oh ... the docs target was also removed,
so that means that for someone to build the Changes
they will need to go back to an old version of cocoon-2_1_X
and use todays status.xml file. Need to do 'build docs'
and then do 'forrest' as described at:
http
Ross Gardler wrote:
[EMAIL PROTECTED] wrote:
Automated build for cocoon-docs FAILED
Log attached.
...
[copy] Copying 1 file to /var/apache2/htdocs/ft/build/cocoon-docs
[echo] Oops, something broke
Interesting...
Every build overnight (for me) worked, but this one failed.
Vadim Gritsenko wrote:
hepabolu wrote:
-/changes.html
This is so outdated (see http://cocoon.apache.org/changes.html) that I
would be ashamed to put it up again. So it's missing from Daisy (also
because it's toplevel) and therefore from forrest.zones.
Not correct, please read the
Hmm, looking further at the messages, there are just
a few broken links ...
http://forrest.zones.apache.org/ft/build/cocoon-docs/broken-links.xml
-David
David Crossley wrote:
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...As i warned a long time ago, the re-arrangement of
documentation should not have been done until the
2.2 release...
Fully agreed, staying with the old docs for 2.1.8 seems much easier,
and 2.2 is a good
Automated build for cocoon-site succeeded
Woops, forgot to set notify.on.success value=false
Fixed now.
-David
Bertrand Delacretaz wrote:
With svn log you can see when it was deleted:
Thanks, that is what i was looking for.
I haven't commited the recovered file, in case you just need it it
temporarily you can get it with the above command.
Please do. I want to encourage other people to
deal with
Carsten Ziegeler wrote:
Ross Gardler wrote:
Sorry, I'm a little slow responding right now. I'm travelling at present
and only have intermittent access and time. However, the URL space
issues are not issues, just get David or myself to zip up te built docs
and there you go, you have
David Crossley wrote:
David Crossley wrote:
Another issue is that normally i run a program to
scan for license issues, but have not found time.
I will try to make some time to do that tonight.
That is done now.
There are SUN licenses throughout the
src/blocks/faces/java/org/apache
, Jorg Heymans wrote:
I know for a fact that the xml formatter from eclipse+wtp does exactly
this :
- * http://www.apache.org/licenses/LICENSE-2.0
+ * http://www.apache.org/licenses/LICENSE-2.0
Oh no! Damn Eclipse!
Why is the reformatting a problem ?
The issue below is that it
Ross Gardler wrote:
I just built a tar file of the cocoon docs from the last automated
build. You can download it from:
http://forrest.zones.apache.org/ft/build/cocoon-docs.tar.gz
You should find that the URLspace is suitable for inclusion within the
cocoon.a.o urlspace and for
Vadim Gritsenko wrote:
David Crossley wrote:
Vadim Gritsenko wrote:
David Crossley wrote:
there is currently a changed URL-space which will bust links,
David,
What changed URLs have you noticed, so far? If there is a list, it will
help fixing problems. Myself, I noticed that
http
Ross Gardler wrote:
hepabolu wrote:
I now also realise what happened and what the rationale was behind the
way it is currently set up in Daisy:
the main menu bar suggests that there are sub sections: About,
Documentation, Community etc. I wanted to keep that division so I
created the
Torsten Curdt wrote:
It is a shame, but these samples never got over the loss on the xml
docs that used to be distributed with Cocoon.
These were what were indexed for those samples AFAIR.
Remove them?
Erk, that is bad. How about just leaving them there,
knowing that they are broken,
Carsten Ziegeler wrote:
This is another try to get 2.1.8 finally out:
Please cast your votes for releasing 2.1.8 tomorrow, 8th of November.
-1 ... People have not addressed the documentation
side of things. See other recent email on this topic
to which nobody replied. We will not be able to
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...As i warned a long time ago, the re-arrangement of
documentation should not have been done until the
2.2 release...
Fully agreed, staying with the old docs for 2.1.8 seems much easier,
and 2.2 is a good time to make a transition
Vadim Gritsenko wrote:
David Crossley wrote:
there is currently a changed URL-space which will bust links,
David,
What changed URLs have you noticed, so far? If there is a list, it will
help fixing problems. Myself, I noticed that
http://cocoon.apache.org/2.1/introduction.html
David Crossley wrote:
Another issue is that normally i run a program to
scan for license issues, but have not found time.
I will try to make some time to do that tonight.
-David
David Crossley wrote:
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...As i warned a long time ago, the re-arrangement of
documentation should not have been done until the
2.2 release...
Fully agreed, staying with the old docs for 2.1.8 seems much easier,
and 2.2 is a good
Torsten Curdt wrote:
Jeremy Quinn wrote:
Torsten Curdt wrote:
5) In the Lucene examples I've created an index
but got a ResourceNotFound for
http://localhost:/samples/blocks/lucene/statistic
And also an IOException when accessing index2 (how
can I create index2??)
Torsten Curdt wrote:
...don't kill the messenger but unless I am mistaken
we still have some issues with 2.1.8rc1
The new documentation is not yet ready, so we will
not be able to update the website following the release
as we normally do.
See the many issues over the last few days.
Here is
Ross Gardler wrote:
Joerg Heinicke wrote:
Ross Gardler wrote:
Of course, someone could fix the broken link, then the nags would go
away ;-)
To do this myself I have to get more to know about the current docs
infrastructure.
Of course I wasn't suggesting you personally do it, but if
. During the release process
either David Crossley or myself will have to zip the build in the
Forrest zone for the release.
For the release, someone needs to decide how we are
going to package the docs with the release.
For the website, the generated content needs svn checkin.
For future
Reinhard Poetz wrote:
Ralph Goers wrote:
On second thought, why are these not sent to the doc list?
Yes please!
Because the docs list is out-of-sight. It is just for
the diff notifications from the Wiki and from Daisy.
I guess that not many people look at the messages there.
The forrestbot
David Crossley wrote:
Ross Gardler wrote:
hepabolu wrote:
just to get the confusion level down I'd like to verify that my ideas
about the current docs are complete and correct.
Good idea, I've been a little confused by the need for continuing the
cocoon-site build. Here's what I
Bertrand Delacretaz wrote:
Torsten Curdt a ?crit :
Carsten Ziegeler wrote:
Our web site does currently provide no sign of the upcoming ApacheCon
in
December. Can someone please add the logo there?
Hmm... I did add it directly to the site and Bertrand
committed the change - where is it
Upayavira wrote:
hepabolu wrote:
Stefano Mazzocchi wrote:
+1 to new skin but only with new content.
I'd like a more lighter (i.e. in color) skin, much along the lines of
the current Maven site.
If you want to make new content a prerequisite for a new skin, it won't
happen for
Youch, i presumed that when we moved to Jira that
the old Bugzilla would be closed and people would
need to look for our issues.apache.org/jira
This old issue was able to be re-opened and commented.
-David
On Mon, Oct 31, 2005 at 08:41:43AM +0100, [EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS
Pier Fumagalli wrote:
hepabolu wrote:
On my brand new Powerbook, the background color of the Apache
Cocoon logo (left with feather) has a different shade of blue as
background, while I can't remember having seen that on my Windows
machine.
AFAICT colors are identical. Anyone else
[
http://issues.apache.org/jira/browse/COCOON-1616?page=comments#action_12356308
]
David Crossley commented on COCOON-1616:
samples/blocks/linkrewriter/welcome ... sitedemo-ns works now. You are a
champ Antonio. We will do a test at Forrest
Antonio Gallardo wrote:
Antonio Gallardo (JIRA) wrote:
[ http://issues.apache.org/jira/browse/COCOON-1616?page=all ]
BTW, is this bug needed to be fixed also in 2.1.8-dev?
Yes. One way to test it would be to copy the extra linkrewriter
sample from trunk.
-David
Bertrand Delacretaz wrote:
Sylvain Wallez a ?crit :
...I think that, along with pinging the Ajaxian guys (which I will
do), we should rewrite our home page to make more apparent Cocoon's
unique abilities in the changing world of webapp development
+1, and it would be good to make it
Bertrand Delacretaz wrote:
Ross Gardler a ?crit :
We've pretty much cleared out all the broken links in the docs in
Daisy. There's just one page left causing a problem:
http://cocoon.zones.apache.org/daisy/legacydocs/status/plan/
documentation/review-sitemap-docs.html
This page has
(there are links to these on http://cocoon.zones.apache.org/)
The two new demos are down ...
502 Bad Gateway
The proxy server received an invalid response from an upstream server.
-David
Sorry, we had a cronjob failing overnight.
All back now
http://forrest.zones.apache.org/
http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1/653.daisy.html
http://forrest.zones.apache.org/ft/build/cocoon-docs/broken-links.xml
-David
Bertrand Delacretaz wrote:
To find out how this works, zone admins should start by studying the
/home/config/cocoon.zone/cdemos/cocoondemo.sh script, it's fairly
self-explanatory. Any changes to stuff under /home/config should be
done with the config user ID (su - config).
Good on you
I have created a Daisy account (crossley). Would someone
please add me to the doc-editors group.
-David
Ross Gardler wrote:
http://forrest.zones.apache.org/ft/build/cocoon-docs/broken-links.xml
This not only lists the target of the link, but also the source of the
link too. So make fixing these things much easier :-)
Had my first Diasy editing today, nice. I fixed a few
of the broken links.
Ross Gardler wrote:
Stefano Mazzocchi wrote:
Is there a way to have non-numerical URL in daisy?
Yes, and no.
Daisy completely separates the front-end application (the daisy-wiki)
from the back-end repository.
In the repository it is only possible to have numerical document IDs.
Vadim Gritsenko wrote:
Ross Gardler wrote:
I'll commit the new configuration to SVN then. Question is where?
Are we ready to delete everything from the site repo?
No! Site repository is contains Cocoon Project docs, 1.x docs, 2.0, and 2.1
docs.
By the way, the forrestbot is also
Carsten Ziegeler wrote:
Ok, I think it's safer to just vote on this as well - again the majority
wins. We already agreed on using just HTML for the docs.
Please cast your votes for:
a) Include the docs in the distribution
b) Provide a separate docs package to download
The docs will
Steven Noels wrote:
Carsten Ziegeler wrote:
As our documentation is now managed by Daisy, we don't have the docs in
the source repository anymore. For the release we should include docs
in
the distributions.
It seems to me that we have three choices (please correct me if I'm
wrong):
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
Now that I am a Cocoon committer, can someone with the necessary karma
please create an account for me on the Cocoon Zone. I would like to set
up the ForrestBot to publish a staged site from Daisy every X hours.
I know
Vadim Gritsenko wrote:
Ugo Cei wrote:
Would you be so nice as to share with us the contents of your [auto-
props] section? I assume you have added all filename patterns that are
relevant for Cocoon sources.
Done. Feel free to update.
http://wiki.apache.org/cocoon/SVNConfig
Surely
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
If the Cocoon project wants us to regularly generate
the newest doc effort (remembering that docs are not
actually published to cocoon.apache.org yet) then lets
build on Forrest's existing resources.
+1 - At present
Ralph Goers wrote:
Stefano Mazzocchi wrote:
Ralph Goers wrote:
Vadim Gritsenko wrote:
Torsten Curdt wrote:
We only need a few more people using it to find the corner cases.
Stable API != Stable Implementation. If API is stable, you should
start vote on marking javaflow stable.
I
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code and on the
lists.
-0 ... nothing against Max, it is just that i
Bertrand Delacretaz wrote:
David Crossley a ?crit :
Bertrand Delacretaz wrote:
Several of us share the thought that Max is the perfect example of a
GSoC success: apart from great technical work, he's quickly found his
place in our community, with regular contributions in code
Ross Gardler wrote:
Now that I am a Cocoon committer, can someone with the necessary karma
please create an account for me on the Cocoon Zone. I would like to set
up the ForrestBot to publish a staged site from Daisy every X hours.
I know that enthousiasm is bubbling Ross, but
please lets
hepabolu wrote:
Vadim Gritsenko wrote:
hepabolu wrote:
Grr. I checked this and thought it was properly set up. What should I
have done?
Check your ~/.subversion/config, it should have [auto-props] section set
up.
See the ready-made config file linked at:
Pier Fumagalli wrote:
Ok, there we go, here's the vote...
0 ... i don't care which issue tracking system we use.
-David
Ross Gardler wrote:
hepabolu wrote:
After talks to several people I feel we need a semi-automatic update
process of the Cocoon documentation to cocoon.apache.org.
We have always needed this, but not possible with the
current setup of the project publishing mechanism at apache.org
If
Daniel Fagerstrom wrote:
Please cast you votes.
+1
-David
Joerg Heinicke wrote:
I have another issue: We don't get commit mails for the gump descriptor.
Is this solvable? Does anybody know the archive for commits to gump
repository?
commits@gump.apache.org
-David
Jean-Baptiste Quenot wrote:
Sorry for the subject of my message, you're right we can't
work together properly with such an aggressive tone. However
just to be clear, I reread the two messages I sent to you
privately with subject ??Error on LoginAction?? and ??Error
Bertrand Delacretaz wrote:
Arje Cahn a ?crit :
...How can I get Bugzilla to tell me what issues are scheduled to be
fixed for the next release?..
Very easy: define an issue which represents the next release, and make
it dependent on all issues that must be fixed. I use it all the time,
Pier Fumagalli wrote:
David Crossley wrote:
Ah i see now where my extra comments in msg18202 came from:
I refererred to an additional file called copyright.txt
which must have had extra restrictions. Don't know if
that is still the same today.
The copyright.txt just states that it's (C
Pier Fumagalli wrote:
David Crossley wrote:
http://www.mail-archive.com/dev@cocoon.apache.org/msg18202.html
Darn... I wish you found that when I posted the license before
committing...
http://www.mail-archive.com/dev@cocoon.apache.org/msg34406.html
The License that Pier shows
Jorg Heymans wrote:
David Crossley wrote:
Erk, something went wrong. This generated file has Windows
end-of-line markers, so that makes it look like the whole
file was changed. It is not your fault Jorg. The svn:eol-style
property is not set, so this is the effect. Each time someone
Pier Fumagalli wrote:
Antonio Gallardo wrote:
Ralph Goers wrote:
Ralph Goers wrote:
I seem to remember reading on legal-discuss that the nuclear
clause is incompatible with the ASL. If true, any components
with such a license can not be disctributed with our code or
reside in SVN.
Erk, something went wrong. This generated file has Windows
end-of-line markers, so that makes it look like the whole
file was changed. It is not your fault Jorg. The svn:eol-style
property is not set, so this is the effect. Each time someone
generates it on different platforms, then line endings
Sylvain Wallez wrote:
Please cast your votes!
+1
-David
Hi Jorg, just in case you don't know this already,
all the information that you should need is at
http://www.apache.org/dev/
Any questions, just ask here on the cocoon-dev list.
-David
Pier Fumagalli wrote:
David Crossley wrote:
Pier Fumagalli wrote:
Nah, I'm pretty confident that on this little nag, I'm right...
Does anyone have a pier2doc transformer?
I need to get into a meeting right now, but the first part of the
pier2doc translation of this thread is here
Pier Fumagalli wrote:
Stefano Mazzocchi wrote:
David Crossley wrote:
Pier Fumagalli wrote:
Nah, I'm pretty confident that on this little nag, I'm right...
Does anyone have a pier2doc transformer?
Why do you think this projet was started? :-)
;-)
Darn, I can see in that 9 years my
Pier Fumagalli wrote:
Nah, I'm pretty confident that on this little nag, I'm right...
Does anyone have a pier2doc transformer?
-David
Sylvain Wallez wrote:
Pier Fumagalli wrote:
I'm working on a JING Transformer (using JING in the pipeline to
validate a document using RNG).
It's cacheable and all that lot... I need to use it with very
slightly XML skilled ASP developers moving to Cocoon (and willing to
break my
Vadim Gritsenko wrote:
Pier Fumagalli wrote:
Vadim Gritsenko wrote:
Pier Fumagalli wrote:
I'm working on a JING Transformer (using JING in the pipeline to
validate a document using RNG).
http://wiki.apache.org/cocoon/ValidationTransformer
It supports JING.
My 0.02 ?
- It's
Carsten Ziegeler wrote:
So please cast your votes for switching to Maven2 NOW as
outlined/discussed in the proposal thread.
+1
Bertrand Delacretaz wrote:
David Crossley a ?crit :
...This is always the case with every new committer,
whether they are subscribed or not. The first commits
need to be moderated. As moderator, you need to add them
to the allow list by using reply-to-all...
Thanks for the info - I've
Antonio Gallardo wrote:
So, I'm pleased to propose Jorg Heymans, as a committer.
+1 from me. He is way past due.
David
Max Pfingsthorn wrote:
Hi!
Sorry about that... I wasn't quite sure what this cvs list was for until
now.. I subscribed now as well.
I was just trying out my svn access, so things were bound to go wrong
somewhere ;)
bye!
max
-Original Message-
From: Bertrand Delacretaz
+1
David
+1 from me
-David
Jorg Heymans wrote:
Torsten Curdt wrote:
On the other hand providing svn commit access
also means handing out an @apache.org address
(required for technical reasons) and (to some extend)
access to the apache infrastructure. Not everyone is
really excited about that. Less for security
Upayavira wrote:
So, we got 23 positive votes (if we include the +1 I forgot to make
myself!) and zero negatives.
Therefore, congratulations Helma, and welcome!
As soon as necessary paperwork is dealt with, I will send the necessary
requests for account creation.
The receipt of
Stefano Mazzocchi wrote:
Stefan Bodewig wrote:
On Thu, 16 Jun 2005, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
it's not a matter of being annoyed enough (we are already!), it's
the fact that cocoon needs that file at build time.
Hmm, so why don't you realize that you have a typo
Upayavira wrote:
As granting committership requires a vote, please cast your votes now:
[ ] Helma Van Der Linden as a Cocoon committer
+1
--David
Sylvain Wallez wrote:
Hi all,
We discussed more that one year ago the removal of @author tags in our
source files (see [1] and [2]) but although the consensus was to remove
them, we never actually did it. Now most if not all new classes added
since then have no @author tag, leading to a
How do artifacts get into the remote Maven respository
and how are they guaranteed to be the legitimate file?
Surely this concern has been discussed before,
but i cannot find the answer.
The Maven web pages just say something like:
create a Jira issue and tell us what you want to add.
That
Bertrand Delacretaz wrote:
Please cast your votes:
+1
--David
Vadim Gritsenko wrote:
AFAIU, samples refactoring is done. Should we remove the page?
Actually it is a shame, but the real job never got finished.
The main reason that i started the effort was the disruption
that occurred in Feb 2003 when we re-structured the CVS and
build system while in the
David Crossley wrote:
Linden H van der (MI) wrote:
I found out Eclipse can do one big patch file by recursing
subdirectories. This is what I've done by starting off from
src/blocks/forms/samples. The result is in bug 34077.
Thanks.
So does the commandline tool ... svn diff patch.txt
Linden H van der (MI) wrote:
Guys,
I found out Eclipse can do one big patch file by recursing
subdirectories. This is what I've done by starting off from
src/blocks/forms/samples. The result is in bug 34077.
Thanks.
So does the commandline tool ... svn diff patch.txt
I do hope you can
Reinhard Poetz wrote:
It has become more and more a PITA that the Forrest extensions (flat
structure, Cocoon style, comments, metadata, ...) had to be copied into all
Forrest repositories. Whenever I had to change something, I had to
synchronize my change with all other already set up
Linden H van der (MI) wrote:
I fixed several of the problems below, but it results in 1 to 3 line
patches of about 40 files. What's the most efficient way of handling this?
That you do ...
cd cocoon-2_1_X
svn diff patch.txt
... and add it to bugzilla
Then follow up to this email with the
Antonio Gallardo wrote:
Linden H van der (MI) dijo:
I fixed several of the problems below, but it results in 1 to 3 line
patches of about 40 files. What's the most efficient way of handling this?
Bye, Helma
Perhaps using jEdit and searching for a regexp and using BeanShell for
Reinhard Poetz wrote:
Upayavira wrote:
David Crossley wrote:
Upayavira wrote:
Bertrand Delacretaz wrote:
Jeremy Quinn a ?crit :
Do you know if there will continue to be xml docs in the build?
AFAIK it's still being discussed, see the recent automatically
generating docs thread.
I
Jeremy Quinn wrote:
Don't get me wrong, I am happy you are being pro-active about this.
However, I see several items on the unsupported list which are IMHO
important components of Cocoon, or are blocks that I use regularly in
my work. eg. chaperon, jms, naming, repository, webdav, xmldb
Reinhard Poetz wrote:
Whenever I work as trainer or consultant and Cocoon is the subject, people
always ask me the same questions about maturity and community of Cocoon and
its blocks. We should tell our users clearly what *we* consider as
supported, deprecated and committed and then
Mark Leicester wrote:
Hi Jeremy (et al),
Ahem... If someone is prepared to nominate me as a committer I'll
gladly support the midi block. :)
Hah, you and others like you have been on my radar for a long time
to invite as committers. Later.
However, your comment reinforces one of my points.
Bertrand Delacretaz wrote:
How about adding another condition: a block can only have supported
status if we have automated tests for all its critical functions?
This might make a big difference in the accountability of supported
stuff in our releases.
That is a great idea. Then rather
Upayavira wrote:
Bertrand Delacretaz wrote:
Jeremy Quinn a ?crit :
Do you know if there will continue to be xml docs in the build?
AFAIK it's still being discussed, see the recent automatically
generating docs thread.
I would be reluctant to see the online docs go. It would be a
Upayavira wrote:
Reinhard Poetz wrote:
David Crossley wrote:
snip/
The other thing to bear in mind, and this was one of the big hold-ups
in the past with improving the docs, is that all of the docs are also
generated via the Cocoon webapp ... 'cocoon.sh servlet'. They use old
stylesheets
Reinhard Poetz wrote:
David Crossley wrote:
[snip]
Perhaps we should step back a bit and assess the situation. It seems
a cumbersome process to double-handle all of the source docs, just to
add some specially-generated docs. Would it help to put these special
docs into a completely separate
Reinhard Poetz wrote:
David Crossley wrote:
I will not have much time to help with the docs re-organisation,
but i will do what i can.
If you can help me to understand what the docs target does I'm more than
happy :-)
I will try. Please ask specific questions on that. I have provided
] (Sorry
guys,
it started with a slightly off-topic question and it has grown bigger, and
bigger )
David Crossley wrote:
Reinhard Poetz wrote:
After looking at cocoon/trunk/tools/targets/docs-build.xml I have to
admit that I don't understand the purpose of this, except that it builds
It seems that not many of us bother with running 'build test'.
That is a shame.
I found that it was broken (for many months) in 2.2 and made some
fixes today. The properties build.test.report and junit.test.loglevel
were missing in the build.properties file. I hope that is all that
is missing,
401 - 500 of 892 matches
Mail list logo
