Bertrand Delacretaz wrote:
Before digging too deep: are the ajax block samples supposed to work
as is in 2.1.8-rc1?
Nope. The problems with Scriptaculous led me to remove it, thus breaking
the samples. I therefore removed the samples so that we have a clean
state (empty, actually) for 2.1.8.
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween), I can do the release either tomorrow or we can use another
week to fix some possible issues and release next friday.
So please cast your votes for
[
Hi,
my vote does not count but:
So please cast your votes for
[x] Release tomorrow, 27th of October
[ ] Release next friday, 4th of November
:-)
kind regards,
Jens
Le 27 oct. 05, à 08:24, Sylvain Wallez a écrit :
Bertrand Delacretaz wrote:
Before digging too deep: are the ajax block samples supposed to work
as is in 2.1.8-rc1?
Nope. The problems with Scriptaculous led me to remove it, thus
breaking the samples. I therefore removed the samples so that
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is because the error page when a user is not logged in was quite unhelpful.
I've just had a reply on the Daisy list about how to change this, but I
Carsten Ziegeler wrote:
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween), I can do the release either tomorrow or we can use another
week to fix some possible issues and release next friday.
So
Le 27 oct. 05, à 09:14, Ralph Goers a écrit :
...it would be great if we had a testing matrix of JVMs, Servlet
Containers and operating systems that we could check off when doing a
release
If you want to setup a simple matrix as a wiki page (or jira issues,
one per set of tests where
Saving of JSR-168 preferences does not appear to be working.
Carsten Ziegeler wrote:
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween), I can do the release either tomorrow or we can use another
Carsten Ziegeler wrote:
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween)
You always have a unix system available: cocoon.zones.apache.org!
Sylvain
--
Sylvain Wallez
Bertrand Delacretaz wrote:
Le 27 oct. 05, à 09:14, Ralph Goers a écrit :
...it would be great if we had a testing matrix of JVMs, Servlet
Containers and operating systems that we could check off when doing a
release
If you want to setup a simple matrix as a wiki page (or jira issues,
Unless I have screwed something up, it appears the
ConvertableEventAspect is not doing its job. I can't test any more
tonight. It is very late.
Ralph
Ralph Goers wrote:
Saving of JSR-168 preferences does not appear to be working.
Carsten Ziegeler wrote:
We had some feedback in the last
Daisy isn't really appropriate for this. Users should be able to update
the matrix too.
Ralph
Ross Gardler wrote:
Bertrand Delacretaz wrote:
Le 27 oct. 05, à 09:14, Ralph Goers a écrit :
...it would be great if we had a testing matrix of JVMs, Servlet
Containers and operating systems
In both 2.1.8-rc1 and 2.2-dev hosted on cocoon.zones, the logo doesn't
appear.
Regards,
Luca Morandini
www.lucamorandini.it
Torsten Curdt wrote:
and find that the old doc (at new URL:
http://wiki.apache.org/cocoon/GeneralizedFlow, ever so unreadable as
back then) still holds some ideas worth considering, no?
...forgotten gems :) Definitely!
I have to read up on this.
just ask for clarification if the doc
Vadim Gritsenko wrote:
Torsten Curdt wrote:
IMHO having map:act *and* map:call is not really nice.
Why not? IMHO it is more readable to have
map:act function=foo/
map:call function=bar/
than:
map:call action=my-action function=function-name/
map:call flow=my-flow
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is because the error page when a user is not logged in was quite unhelpful.
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is because the error page when a user is not logged in was quite unhelpful.
On Thu, 2005-10-27 at 10:40 +0100, Ross Gardler wrote:
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is because the
Upayavira wrote:
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is because the error page when a user is not logged in
Bruno Dumon wrote:
On Thu, 2005-10-27 at 10:40 +0100, Ross Gardler wrote:
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
Ross Gardler wrote:
Upayavira wrote:
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page
for that document. It doesn't link straight back to the edit page
yet, this is because the error page when a
Bruno Dumon wrote:
On Thu, 2005-10-27 at 10:50 +0100, Upayavira wrote:
Bruno Dumon wrote:
On Thu, 2005-10-27 at 08:07 +0100, Ross Gardler wrote:
The Forrest generated docs are now linking back to the daisy page for
that document. It doesn't link straight back to the edit page yet, this
is
Le 27 oct. 05, à 12:57, Upayavira a écrit :
Bruno Dumon wrote:
...I thought we had a robot file in place which forbids that.
I don't know. Do we? If we have, then that goes part of the way for me.
We do: http://cocoon.zones.apache.org/robots.txt
Assuming this is correct, but I think it
Carsten Ziegeler wrote:
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween), I can do the release either tomorrow or we can use another
week to fix some possible issues and release next friday.
So
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
We had some feedback in the last days wrt to the 2.1.8 release.
As I'm having access to a unix system tomorrow and next friday (but not
inbetween), I can do the release either tomorrow or we can use another
week to fix some possible issues and
Hi,
On 27 Oct 2005, at 07:35, Carsten Ziegeler wrote:
So please cast your votes for
[ ] Release tomorrow, 27th of October
[ ] Release next friday, 4th of November
-1 for tomorrow: just got bitten again by this bug: http://
issues.apache.org/jira/browse/COCOON-1594
We need time to fix it.
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Project: Cocoon
Type: Task
Versions: 2.1.8-dev (Current SVN)
Reporter: Bertrand Delacretaz
Assigned to: Cocoon Developers Team
This issue depends on
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Bertrand Delacretaz updated COCOON-1663:
Comment: was deleted
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Andrew Savory wrote:
Hi,
On 27 Oct 2005, at 07:35, Carsten Ziegeler wrote:
So please cast your votes for
[ ] Release tomorrow, 27th of October
[ ] Release next friday, 4th of November
-1 for tomorrow: just got bitten again by this bug: http://
[
http://issues.apache.org/jira/browse/COCOON-1663?page=comments#action_12356092
]
Bertrand Delacretaz commented on COCOON-1663:
-
To mark an issue as blocking for the 2.1.8 release, use the links function of
the blocking issue.
Release 2.1.8
Bertrand Delacretaz (JIRA) wrote:
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Project: Cocoon
Type: Task
Versions: 2.1.8-dev (Current SVN)
Reporter: Bertrand Delacretaz
Assigned to: Cocoon
Le 27 oct. 05, à 16:42, Andrew Savory a écrit :
...-1 for tomorrow: just got bitten again by this bug:
http://issues.apache.org/jira/browse/COCOON-1594
I have created http://issues.apache.org/jira/browse/COCOON-1663 to list
issues which we consider blocking for the release, and added
Le 27 oct. 05, à 16:55, Vadim Gritsenko a écrit :
IIUC that's not the Jira way to do it... Am I right? Pier? :)
It would work, though ;-)
I'm open to other suggestions for sure, if people who know jira better
want to do it then go ahead, I won't mind!
The point is: managing these things in
Hi,
On 27 Oct 2005, at 15:53, Upayavira wrote:
Well, are you saying that this is a critical bug?
As far as I am concerned, you can vote -1 on a release because
something
is critical to the project, but not because it is inconvenient to
you :-)
Well, a component of Cocoon (SQL
Andrew Savory wrote:
Hi,
On 27 Oct 2005, at 15:53, Upayavira wrote:
Well, are you saying that this is a critical bug?
As far as I am concerned, you can vote -1 on a release because something
is critical to the project, but not because it is inconvenient to you
:-)
Well, a
Kris Schneider wrote:
We're using Java Flow and it looks like continuations are not
invalidated by calling sendPage. Is there a reason to keep a
continuation around after invoking sendPage?
Yes - it is called Back Button, usually located in the top left corner of your
browser window :-P
Bertrand Delacretaz wrote:
Le 27 oct. 05, à 16:55, Vadim Gritsenko a écrit :
IIUC that's not the Jira way to do it... Am I right? Pier? :)
I'm open to other suggestions for sure, if people who know jira better
want to do it then go ahead, I won't mind!
done: http://issues.apache.org/jira/browse/COCOON-1664
Let me know what ya think.
--Ryan
Ralph Goers wrote:
Ryan Slack wrote:
It was not particularly hard, but I wrote, and have somewhat tested,
a Jaas implmentation of Authenticator. Is this something
anyone/cocoon would be interested in?
Bertrand Delacretaz wrote:
Le 21 oct. 05, à 23:31, Sylvain Wallez a écrit :
...The live demo should be available soon at
http://cocoon.zones.apache.org/demos/trunk/samples/blocks/forms/sql/
The live demos have been updated but that page gives an error, as does
So please cast your votes for
[ ] Release tomorrow, 27th of October
-1: We can't: docs are not generated in 2.1 URI space yet
[ ] Release next friday, 4th of November
+0: Will see
+1 for delaying the release.
Jörg
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Pier Fumagalli updated COCOON-1663:
---
Fix Version: 2.1.8-dev (Current SVN)
Release 2.1.8
-
Key: COCOON-1663
URL:
[ http://issues.apache.org/jira/browse/COCOON-1594?page=all ]
Pier Fumagalli updated COCOON-1594:
---
Bugzilla Id: (was: 36573)
Fix Version: 2.1.8-dev (Current SVN)
SQLTransformer swallowing whitespace on substitute-value
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Pier Fumagalli deleted COCOON-1663:
---
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Project: Cocoon
On 27 Oct 2005, at 15:55, Vadim Gritsenko wrote:
Bertrand Delacretaz (JIRA) wrote:
Release 2.1.8
-
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Project: Cocoon
Type: Task
Versions: 2.1.8-dev (Current SVN)Reporter:
Saving of JSR-168 preferences does not appear to be working.
Key: COCOON-1666
URL: http://issues.apache.org/jira/browse/COCOON-1666
Project: Cocoon
Type: Bug
Components: Blocks: Portal
Versions:
Test release against JVM 1.3/5.0 and different Tomcat versions
--
Key: COCOON-1665
URL: http://issues.apache.org/jira/browse/COCOON-1665
Project: Cocoon
Type: Task
Versions: 2.1.8-dev (Current SVN)
Generation of documentation
---
Key: COCOON-1667
URL: http://issues.apache.org/jira/browse/COCOON-1667
Project: Cocoon
Type: Wish
Components: - Documentation
Versions: 2.1.8-dev (Current SVN)
Reporter: Vadim Gritsenko
Fix
As we're closing the 2.1.8 release, I'd like to get the bugs you wish
were fixed into Jira. Remember that you should set the Fix Version/
s field to 2.1.8-dev, which will become (officially) 2.1.8 when
we release.
I still have to think slightly about how to do release management...
Also,
Le 27 oct. 05, à 20:58, Pier Fumagalli a écrit :
...I still have to think slightly about how to do release management...
Yes, and thanks for setting this up in jira!
-Bertrand
On Oct 27, 2005, at 11:58 AM, Pier Fumagalli wrote:
If you can't find the field in the bug entry page, it's because you
don't have enough privileges, let me know and I'll make sure you're in
the cocoon-developers group.
If you would, please... for [EMAIL PROTECTED]
Thanks,
Mark
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 27 October 11:09 PM
Using Forrest 0.8-dev
Forrestbot administrator: Ross Gardler
--
[echo]
... Forrest render START 2005-10-27 11:02:06
... Rendering docs in
Automated build for cocoon-docs FAILED
Log attached.
--
Forrestbot run ended at 28 October 02:09 AM
Using Forrest 0.8-dev
Forrestbot administrator: Ross Gardler
--
[echo]
... Forrest render START 2005-10-28 02:02:06
... Rendering docs in
I'm not really sure why Jira didn't send an email. I added the following
comment to this issue.
I have created a table in the wiki for tracking testing. Feel free to
update it!
http://wiki.apache.org/cocoon/ReleaseTests218
Pier Fumagalli (JIRA) wrote:
Test release against JVM 1.3/5.0 and
Le 27 oct. 05, à 08:35, Carsten Ziegeler a écrit :
So please cast your votes for
[ ] Release tomorrow, 27th of October
[+1 ] Release next friday, 4th of November
Things are still happening re. testing and docs, so the release should
be a better one in a week.
-Bertrand
54 matches
Mail list logo
