On 10/12/06, David Crossley <[EMAIL PROTECTED]> wrote:
...Closing issues prematurely is disrespectful...
Agreed, with "prematurely" as the key aspect.
I must admit I haven't looked at the particular issue being discussed,
I was thinking in general terms: if an issue has been sitting here for
s
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441642
]
Cyriaque Dupoirieux commented on COCOON-1928:
-
David, I am going to try the solution of Jörg with entities. I think it can be
the solution and it's r
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441620
]
David Crossley commented on COCOON-1928:
Cyriaque, have you tried declaring the serializer in your project's
sitemap.xmap file? I am not sure which one t
Jean-Baptiste Quenot wrote:
> * Antonio Gallardo:
>
> > > Jean-Baptiste Quenot closed COCOON-1774.
> > >
> > >Resolution: Won't Fix
> > >
> > > Please reopen the issue if the problem persists with the new
> > > Dojo stuff. Thanks!
> >
> > I don't think it is the best way to close bugs. IMH
Jean-Baptiste Quenot wrote:
* Vadim Gritsenko:
Antonio Gallardo wrote:
I can confirm this error on the cocoon zones. It was
not before, I suspect some changes done in the hackathon
intriduced this bug, but I did not check this yet.
EnhancedRepeaterJXPathBinding
[ http://issues.apache.org/jira/browse/COCOON-907?page=all ]
Jörg Heinicke closed COCOON-907.
Resolution: Fixed
So trying to set it to fixed.
> Move Woody into CocoonForms block
> -
>
> Key: COCOON-907
>
[ http://issues.apache.org/jira/browse/COCOON-907?page=all ]
Jörg Heinicke reopened COCOON-907:
--
Reopening this issue as it is closed, but not resolved.
> Move Woody into CocoonForms block
> -
>
>
[ http://issues.apache.org/jira/browse/COCOON-267?page=all ]
Jörg Heinicke closed COCOON-267.
Resolution: Fixed
So trying to set it to fixed again.
> Lucene index/search broken, wrong contentType each doc so ignored
> ---
[ http://issues.apache.org/jira/browse/COCOON-267?page=all ]
Jörg Heinicke reopened COCOON-267:
--
Reopening this issue as it is closed, but not resolved.
> Lucene index/search broken, wrong contentType each doc so ignored
>
Joerg Heinicke wrote:
Yes, that should be the way to go. Furthermore (if it is possible) you
should add a dependency on the xmlutil issue to the Cocoon issue, so
that we get informed when xmlutil is fixed.
Yes that sounds about right to me. Create the ticket and I'll see to it
that it gets
[
http://issues.apache.org/jira/browse/COCOON-1931?page=comments#action_12441513
]
Jörg Heinicke commented on COCOON-1931:
---
flow => flaw
> Provide more information when compiling a Flowscript fails
> --
Issue Subscription
Filter: COCOON-open-with-patch (87 issues)
Subscriber: cocoon
Key Summary
COCOON-1931 Provide more information when compiling a Flowscript fails
http://issues.apache.org/jira/browse/COCOON-1931
COCOON-1929 [PATCH] Reloading classloader in Cocoon 2.2
[
http://issues.apache.org/jira/browse/COCOON-1931?page=comments#action_12441507
]
Jörg Heinicke commented on COCOON-1931:
---
IMO we should fix the flow, not the symptoms - if it is possible. Where is the
NPE thrown? Can you provide a stack
On 11.10.2006 11:41, Ard Schrijvers wrote:
There is a cocoon jira issue outstanding
(http://issues.apache.org/jira/browse/COCOON-1909) that is actually a
excalibur-xmlutil flaw. It is about check-includes for stylesheets only
working one level deep. I fixed this flaw in the XSLTProcessorImpl. I
On 10/11/06, Antonio Gallardo <[EMAIL PROTECTED]> wrote:
...IMHO, we should leave open this bug, because the fixi is not finished
yet until we update excalibur...
Same here. If "update excalibur" is a Jira or bugzilla issue
somewhere, I'd make a link or a dependency to it to indicate what's
ha
Hi Ard,
IMHO, we should leave open this bug, because the fixi is not finished
yet until we update excalibur.
Best Regards,
Antonio Gallardo.
Ard Schrijvers escribió:
A different question, but related to closing issues practices:
What is common practice for bugs that are reported in cocoon
[ http://issues.apache.org/jira/browse/COCOON-1928?page=all ]
Jörg Heinicke updated COCOON-1928:
--
> Add the ability to pass the doctype in parameter for Serializer
> ---
>
> Key: CO
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441464
]
Jörg Heinicke commented on COCOON-1928:
---
> Doctype is configurable right now, see Cocoon samples
Of course it is. But I wondered why he wants to make even
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441449
]
Vadim Gritsenko commented on COCOON-1928:
-
To Joerg:
Doctype is configurable right now, see Cocoon samples:
-//W3C//DTD HTML 4.01 Transitional/
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441446
]
Cyriaque Dupoirieux commented on COCOON-1928:
-
Because the core of forrest - an internal plugin exactly... - defines the
serializer with :
-//W3
Jean-Baptiste Quenot wrote:
* Vadim Gritsenko:
Antonio Gallardo wrote:
I can confirm this error on the cocoon zones. It was
not before, I suspect some changes done in the hackathon
intriduced this bug, but I did not check this yet.
EnhancedRepeaterJXPathBinding was the culpri
[ http://issues.apache.org/jira/browse/COCOON-1416?page=all ]
Jörg Heinicke closed COCOON-1416.
-
Resolution: Cannot Reproduce
> JXTemplate Bug List(For Refactoring info)
> -
>
> Key: COCOON-1416
>
[ http://issues.apache.org/jira/browse/COCOON-1416?page=all ]
Jörg Heinicke reopened COCOON-1416:
---
Just nitpicking and resetting to more appropriate WORKSFORME.
> JXTemplate Bug List(For Refactoring info)
> ---
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441410
]
Jörg Heinicke commented on COCOON-1928:
---
Sorry, but this really looks like FS (Flexibility Syndrome aka featuritis). Why
do you need this dynamic? Where do
[ http://issues.apache.org/jira/browse/COCOON-1931?page=all ]
Georg Hüttenegger updated COCOON-1931:
--
Attachment: FOM_JavaScriptInterpreter.java.MoreErrorInfoPatch
> Provide more information when compiling a Flowscript fails
> --
Provide more information when compiling a Flowscript fails
--
Key: COCOON-1931
URL: http://issues.apache.org/jira/browse/COCOON-1931
Project: Cocoon
Issue Type: Improvement
Co
A different question, but related to closing issues practices:
What is common practice for bugs that are reported in cocoon's jira, but are
actually for example an excalibur bug? For example, I just fixed the bug
regarding imported stylesheets not invalidating the parent-parent stylesheet
despi
Hello Jorg,
> Dear all,
>
> I have created a new test release of the avalon/excalibur components
> here [1]. The aim of this release was to convert a/e to
> maven2, so that
> people could include it in their m2 based projects using proper
> transitive dependency management based on clean poms
David Crossley wrote:
See the new section at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
to explain the quick way to update the Cocoon 2.1 docs.
Any committer can do it.
I followed this today (it has been 2 months since last update).
However i don't have time to find out what is going wro
[
http://issues.apache.org/jira/browse/COCOON-1732?page=comments#action_12441382
]
Franchet Nicolas commented on COCOON-1732:
--
The patch works fine for textareas, but the problem can occur with other html
element. IE seems to not under
On 10/11/06, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
...I think there is no good reason to keep the issue open forever if
no one intends to work on it, especially as the JIRA is full of
these...
Agreed - if an issue sits in the "feedback required" for a long time
and nothing happens, i
See the new section at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
to explain the quick way to update the Cocoon 2.1 docs.
Any committer can do it.
I followed this today (it has been 2 months since last update).
However i don't have time to find out what is going wrong.
Would someone else p
* Vadim Gritsenko:
> Antonio Gallardo wrote:
>
> > I can confirm this error on the cocoon zones. It was
> > not before, I suspect some changes done in the hackathon
> > intriduced this bug, but I did not check this yet.
>
> EnhancedRepeaterJXPathBinding was the culprit.
Hi Vadim,
[ http://issues.apache.org/jira/browse/COCOON-1416?page=all ]
Jean-Baptiste Quenot closed COCOON-1416.
Resolution: Won't Fix
Assignee: (was: Cocoon Developers Team)
Please reopen if this is still an issue, thanks.
> JXTemplate Bug List
* Antonio Gallardo:
> > Jean-Baptiste Quenot closed COCOON-1774.
> >
> >Resolution: Won't Fix
> >
> > Please reopen the issue if the problem persists with the new
> > Dojo stuff. Thanks!
>
> I don't think it is the best way to close bugs. IMHO, the first
> part of a problem resolution is
[
http://issues.apache.org/jira/browse/COCOON-1928?page=comments#action_12441369
]
Cyriaque Dupoirieux commented on COCOON-1928:
-
Here is my problem,
I want to use two variables to be able to define the doctype-public and the
doctyp
[ http://issues.apache.org/jira/browse/COCOON-1379?page=all ]
Jean-Baptiste Quenot closed COCOON-1379.
Fix Version/s: 2.2-dev (Current SVN)
Resolution: Fixed
Assignee: (was: Cocoon Developers Team)
I think we can close this on
37 matches
Mail list logo
