On Wed, Mar 01, 2006 at 10:53:29PM +, Pier Fumagalli wrote:
> On 1 Mar 2006, at 22:39, Jason Johnston wrote:
>
> > On Wed, 2006-03-01 at 11:59 -0600, Antonio Gallardo wrote:
> >>> Follow the "Edit" link of the issue you want to change. There is a
> >>> section "Other Info" containing a checkbo
Pier Fumagalli wrote:
>
> Yeah, it's not "fantastic" let's say... There should be really an
> option to search for issues with attachments, rather than relying on
> a "patched" flag in the issue itself...
I have a personal filter for Forrest that is
a workaround for that lack. It searches for
On Wed, Mar 01, 2006 at 10:52:07PM +, Pier Fumagalli wrote:
> On 1 Mar 2006, at 17:59, Antonio Gallardo wrote:
>
> >> Follow the "Edit" link of the issue you want to change. There is a
> >> section "Other Info" containing a checkbox field "Patch available".
> >
> > IIRC "edit" option is avai
Pier Fumagalli wrote:
> David Crossley wrote:
> >Pier Fumagalli wrote:
> >>David Crossley wrote:
> >>
> >>>That filter is COCOON-open-with-patch
> >>>http://issues.apache.org/jira/secure/IssueNavigator.jspa?
> >>>requestId=12310771
> >>>
> >>>How can we get Jira to send that to [EMAIL PROTECTED]
>
Hi team,
cocoon forms uses the common enumeration pattern for it's enum datatype
and selection list. The problem with the selection list is that the
order of the elements in it is not granted. Current implementation uses
the getDeclaredFields method, which states in its javadocs that " The
ele
[PATCH] Char datatype
-
Key: COCOON-1789
URL: http://issues.apache.org/jira/browse/COCOON-1789
Project: Cocoon
Type: New Feature
Components: Blocks: Forms
Versions: 2.1.9-dev (current SVN)
Reporter: Simone Gianni
Priority: Mino
On 1 Mar 2006, at 22:39, Jason Johnston wrote:
On Wed, 2006-03-01 at 11:59 -0600, Antonio Gallardo wrote:
Follow the "Edit" link of the issue you want to change. There is a
section "Other Info" containing a checkbox field "Patch available".
IIRC "edit" option is available to committers. Is th
On 1 Mar 2006, at 17:59, Antonio Gallardo wrote:
Follow the "Edit" link of the issue you want to change. There is a
section "Other Info" containing a checkbox field "Patch available".
IIRC "edit" option is available to committers. Is this correct, Pier?
Yep... Can't give it to *world* unfor
On 1 Mar 2006, at 22:34, David Crossley wrote:
Pier Fumagalli wrote:
David Crossley wrote:
That filter is COCOON-open-with-patch
http://issues.apache.org/jira/secure/IssueNavigator.jspa?
requestId=12310771
How can we get Jira to send that to [EMAIL PROTECTED]
once per week?
Is this all righ
On Wed, 2006-03-01 at 11:59 -0600, Antonio Gallardo wrote:
> > Follow the "Edit" link of the issue you want to change. There is a
> > section "Other Info" containing a checkbox field "Patch available".
>
> IIRC "edit" option is available to committers. Is this correct, Pier?
If that is the case
Pier Fumagalli wrote:
> David Crossley wrote:
>
> >That filter is COCOON-open-with-patch
> >http://issues.apache.org/jira/secure/IssueNavigator.jspa?
> >requestId=12310771
> >
> >How can we get Jira to send that to [EMAIL PROTECTED]
> >once per week?
>
> Is this all right? Every week starting no
[ http://issues.apache.org/jira/browse/COCOON-1786?page=all ]
Eric Meyer closed COCOON-1786:
--
Resolution: Fixed
> BrowserUpdateTransformer can get into invalid state - must override recycle()
> --
[
http://issues.apache.org/jira/browse/COCOON-1786?page=comments#action_12368338
]
Antonio Gallardo commented on COCOON-1786:
--
Improved Second patch applied. Would you cross check the patch and close the
issue?
> BrowserUpdateTransformer can get
[ http://issues.apache.org/jira/browse/COCOON-1785?page=all ]
Eric Meyer closed COCOON-1785:
--
Resolution: Fixed
Thanks, Antonio.
--Eric
> I18nMessage - null parameter values causes NPE
> --
>
> Key:
[ http://issues.apache.org/jira/browse/COCOON-1785?page=all ]
Antonio Gallardo updated COCOON-1785:
-
Would you cross check and close the bug?
> I18nMessage - null parameter values causes NPE
> --
>
>
[
http://issues.apache.org/jira/browse/COCOON-1785?page=comments#action_12368329
]
Antonio Gallardo commented on COCOON-1785:
--
Thanks Eric for your contribution!
The i18nMessage doesn't include a logger. Patch applied as is.
> I18nMessage - null
Reinhard Poetz wrote:
Jason Johnston wrote:
David Crossley wrote:
Recently we added a new Jira field "Patch available".
In the old Cocoon Bugzilla we used to ask people to
add PATCH to the Issue Summary name. We also used
to have a reminder email sent to the mailing list
every week to remin
[ http://issues.apache.org/jira/browse/COCOON-1726?page=all ]
Ugo Cei updated COCOON-1726:
Attachment: patch2.txt
Modified previous version following David's observations.
> Implementation of Source that supports conditional GETs
> -
Il giorno 03/feb/06, alle ore 00:32, David Crossley ha scritto:
I got it a few days ago. Perhaps you re-attached the
same patch.
Took a while for me to find the time to do something about this, but
I have a new version of the patch attached to the issue. You might
want to test it.
[ http://issues.apache.org/jira/browse/COCOON-1726?page=all ]
Ugo Cei updated COCOON-1726:
Attachment: (was: patch.txt)
> Implementation of Source that supports conditional GETs
> ---
>
> Key:
Ralph Goers wrote:
> Are you logged in?
Yes. :)
>
> Jason Johnston wrote:
>> Reinhard Poetz wrote:
>>
>>> Jason Johnston wrote:
>>>
David Crossley wrote:
> Recently we added a new Jira field "Patch available".
>
> In the old Cocoon Bugzilla we used to ask p
Are you logged in?
Jason Johnston wrote:
Reinhard Poetz wrote:
Jason Johnston wrote:
David Crossley wrote:
Recently we added a new Jira field "Patch available".
In the old Cocoon Bugzilla we used to ask people to
add PATCH to the Issue Summary name. We also used
to have a rem
Reinhard Poetz wrote:
> Jason Johnston wrote:
>> David Crossley wrote:
>>
>>> Recently we added a new Jira field "Patch available".
>>>
>>> In the old Cocoon Bugzilla we used to ask people to
>>> add PATCH to the Issue Summary name. We also used
>>> to have a reminder email sent to the mailing list
Jason Johnston wrote:
David Crossley wrote:
Recently we added a new Jira field "Patch available".
In the old Cocoon Bugzilla we used to ask people to
add PATCH to the Issue Summary name. We also used
to have a reminder email sent to the mailing list
every week to remind committers to attend to
Max Pfingsthorn schrieb:
> Hi!
>
> Okay, I traced this one to the o.a.c.environment.wrapper.EnvironmentWrapper
> thank god for debuggers). That one does not implement release(Source)
itself,
>so the superclass is used, but since it is a wrapper, it is not initialized to
>have a source resolver it
David Crossley wrote:
> Recently we added a new Jira field "Patch available".
>
> In the old Cocoon Bugzilla we used to ask people to
> add PATCH to the Issue Summary name. We also used
> to have a reminder email sent to the mailing list
> every week to remind committers to attend to patches.
>
>
Hi!
I want to refactor the repository block so that SourceProperty is an interface.
Or at least implement readObject() and writeObject(), so it can be serialized.
SourceProperty not being Serializable makes the WebDAVSource (and any other
which implements InspectableSource) not cacheable via th
A couple of weeks ago I promised to set up a FAQ system in Daisy. I've
now done this.
Creating a FAQ
==
There is a "FAQ" document Type. This is a simple document in which the
document title should be the question and the content should be the answer.
To illustrate things I have c
[
http://issues.apache.org/jira/browse/COCOON-1592?page=comments#action_12368279
]
Andrew Stevens commented on COCOON-1592:
For what it's worth, Vincent's patch passes the unit tests in COCOON-1779...
> Can't set cookie path etc. used by LocaleAct
[ http://issues.apache.org/jira/browse/COCOON-1786?page=all ]
Eric Meyer updated COCOON-1786:
---
Attachment: BrowserUpdateTransformer-setup-recycle-patch.txt
Upon reflection, this is more a task for the setup() method. Recycle should
deal with releasing ref
Hi!
Okay, I traced this one to the o.a.c.environment.wrapper.EnvironmentWrapper
(thank god for debuggers). That one does not implement release(Source) itself,
so the superclass is used, but since it is a wrapper, it is not initialized to
have a source resolver itself! I am not sure what this cl
Paul Browne has written up the state of Enterprise Java and Web 2.0 (or
rather Ajax) on his O'Reilly blog. Perhaps someone from the Cocoon
"Ajax-Team" feels like leaving a comment on Cocoon and Ajax support?
http://www.oreillynet.com/pub/wlg/9264
Matthew
Some thoughts (my opinion) about configuration.
1. Environment-related configuration should be banned inside the
webapp directory (or WAR file).
2. Business-related configuration should be inside it.
Developing it a little more you will see why I state that.
a. The developer of an application (
On 1 Mar 2006, at 08:12, David Crossley wrote:
That filter is COCOON-open-with-patch
http://issues.apache.org/jira/secure/IssueNavigator.jspa?
requestId=12310771
How can we get Jira to send that to [EMAIL PROTECTED]
once per week?
Is this all right? Every week starting now...
Issue Subscri
Issue Subscription
Filter: COCOON-open-with-patch (101 issues)
Subscriber: cocoon
Key Summary
COCOON-1785 I18nMessage - null parameter values causes NPE
http://issues.apache.org/jira/browse/COCOON-1785
COCOON-1782 [PATCH] Support for CSS classes in cocoon forms XSL
Recently we added a new Jira field "Patch available".
In the old Cocoon Bugzilla we used to ask people to
add PATCH to the Issue Summary name. We also used
to have a reminder email sent to the mailing list
every week to remind committers to attend to patches.
Today i visited every issue that alre
[ http://issues.apache.org/jira/browse/COCOON-1398?page=all ]
David Crossley updated COCOON-1398:
---
Bugzilla Id: (was: 32991)
Other Info: [Patch available]
> New CachingPortletAdapter
> -
>
> Key: COCOON-1398
>
37 matches
Mail list logo