Jorg Heymans wrote:
Hi,
How do people feel about moving sample content and source from a block
out of the block directory into its own location ?
Carsten already did that for the portal, although not with either of the
directory structures you list below. Ultimately this needs to be
Stefano Mazzocchi wrote:
Upayavira wrote:
Stefano Mazzocchi wrote:
Ross Gardler wrote:
I've just added the Forrest configuration to the whiteboard as
daisy-to-docs. I'll now update our forestbot to retrieve it from the
Cocoon repo instead of the Forrest one. This way if any changes are
Jorg Heymans wrote:
Hi,
How do people feel about moving sample content and source from a block
out of the block directory into its own location ?
eg something like
/src
/blocks
/cforms
pom.xml
/blocks-samples
/cforms
pom.xml
Upayavira wrote:
Stefano Mazzocchi wrote:
Upayavira wrote:
...
An edit this page link would make is *sooo* much better to tie the
whole system together and shouldn't be that hard.
With one of those 'don't crawl me' request parameters, I assume? And a
robots.txt on Daisy. We don't want
Ross Gardler wrote:
Upayavira wrote:
Stefano Mazzocchi wrote:
Upayavira wrote:
...
An edit this page link would make is *sooo* much better to tie the
whole system together and shouldn't be that hard.
With one of those 'don't crawl me' request parameters, I assume? And a
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
Vadim Gritsenko wrote:
[EMAIL PROTECTED] wrote:
Author: sylvain
Date: Thu Oct 20 09:03:19 2005
New Revision: 326930
URL: http://svn.apache.org/viewcvs?rev=326930view=rev
Log:
Fields with value-changed listeners are triggering form submit
automatically. fi:styling submit-on-change=true is no
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Why such a complicated exception handling?
Same as before.
I see several problems here:
- SourceNotFoundException is a nominal case (BTW why not using
Source.exists()?) and should not log an exception
* Source.exists() will not work here:
Can you please add the license for jdbi to the legal directories (2.1.x
and trunk)?
Thanks
Carsten
Sylvain Wallez wrote:
Hi all,
Just in time before the code freeze deadline, I committed an additional
sample for CForms [1], which shows how, using JDBI [2] and the
Collection wrappers for
Ralph Goers wrote:
I don't like this structure much. I prefer
/src
/blocks
/cforms
/api
pom.xml
/impl
pom/xml
/samples
pom.xml
Upayavira wrote:
Please do it. A sample is a separate block with a dependency. A sample
may contain Java code, just as a block itself. The only difference
really is that the block.xml or pom.xml or something needs to have the
designation sample so we can say install Cocoon with all samples.
David Crossley wrote:
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/
On 23.10.2005 13:10, Jorg Heymans wrote:
So the layout is:
/src/blocks/cforms/pom.xml
/src/blocks/cforms-samples/pom.xml
note that the blocks directory will have about 120 subdirs in total
then, easy to get lost in. That's why i thought a blocks-samples
directory would make sense, doesn't
Joerg Heinicke wrote:
On 23.10.2005 13:10, Jorg Heymans wrote:
So the layout is:
/src/blocks/cforms/pom.xml
/src/blocks/cforms-samples/pom.xml
note that the blocks directory will have about 120 subdirs in total
then, easy to get lost in. That's why i thought a blocks-samples
On 23.10.2005 13:40, Upayavira wrote:
So the layout is:
/src/blocks/cforms/pom.xml
/src/blocks/cforms-samples/pom.xml
note that the blocks directory will have about 120 subdirs in total
then, easy to get lost in. That's why i thought a blocks-samples
directory would make sense, doesn't have
Upayavira wrote:
Thing is, we've been through that discussion before. Do we separate out
samples from main blocks, stable from unstable, supported from
deprecated? What separations do we do?
ok let's not get into this argument again then. Separating the code that
demonstrates a blocks'
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-template has an issue affecting its community integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-midi has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jcr has an issue affecting its community integration.
This issue
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-jcr has an issue affecting its community integration.
This issue
Carsten Ziegeler wrote:
Can you please add the license for jdbi to the legal directories (2.1.x
and trunk)?
Oh yes, sure, forgot that! It's the well-known ASL 2.0 :-)
I also solved the ant build problem I had in trunk as I finally found
that gump.xml has moved to src/gump/module.xml :-/
Jorg Heymans wrote:
Upayavira wrote:
Thing is, we've been through that discussion before. Do we separate out
samples from main blocks, stable from unstable, supported from
deprecated? What separations do we do?
ok let's not get into this argument again then. Separating the code that
was: [M10N] separating samples from blocks
Jorg Heymans wrote:
Another thing i didn't think of last night is that this will impact the
current ant build of 2.2 as well. How easy is it to change this, just a
matter of adjusting paths ?
More importantly : how long should we still care about the
Joerg Heinicke wrote:
...
Ralph made a proposal [1] where exactly one block (= directory) per
block (= block in the narrower sense) exists, but with many modules
(in the maven sense) in them:
/src
/blocks
/cforms
/api
pom.xml
Sylvain,
It seem to be great stuff, and something that we really need. But being
somewhat formalistic I'm a bit doubtfull about the timing. Ok, you
committed it before the freeze, but not in good enough time to make much
community involvment possible before the release.
/Daniel
Sylvain
On 23.10.2005 10:52, Sylvain Wallez wrote:
The only case where form behaviour will be different will be for fields
that have change listeners but no submit-on-change=true in the
template. These forms will not be broken, but will roundtrip too much to
the server.
It depends on how you define
Hi,
you might have seen the notification mails on the docs list for updates
to the forms documentation, but is probably easier if I explain what
I've done:
* the introductionary sample has been updated to reflect the current
state of affairs (jx instead of forms transformer, no use of
Peter,
thanks so much for this, great plug for me to start.
Peter Hunsberger wrote:
On 9/30/05, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
There was a moment where I could have been one of the first people to
respond to this thread, you just happened to ask this question when I
was watching
Jorg Heymans wrote:
Ralph Goers wrote:
I don't like this structure much. I prefer
/src
/blocks
/cforms
/api
pom.xml
/impl
pom/xml
/samples
pom.xml
Joerg Heinicke wrote:
On 23.10.2005 13:40, Upayavira wrote:
Sorry, I'm afraid I don't understand what you are saying!
No problem, let me try a second time:
Ralph made a proposal [1] where exactly one block (= directory) per
block (= block in the narrower sense) exists, but with many
Ok, progress on Jira.
As requested, I added the workflow statuses that marks an issue as
on hold (when waiting for feedback) and continued meaning that
feedback was received and work should continue.
I'm waiting for the changes to propagate through the system now...
Pier
smime.p7s
Daniel Fagerstrom wrote:
* M2 stable enough (2.0 is out so this should be fullfilled)
* Reasonably fast (don't need to be as fast as Ant, but not several
times slower)
For me, this isn't an issue.
* Easy configuration of what blocks to compile (like blocks.properties
and maybe even
was: Super-easy SQL/Form integration for simple CRUD applications
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
Sylvain,
It seem to be great stuff, and something that we really need. But
being somewhat formalistic I'm a bit doubtfull about the timing. Ok,
you committed it before the
Ralph Goers wrote:
/src
/blocks
/cforms
/api
pom.xml
/impl
pom/xml
/samples
pom.xml
/test
pom.xml
Why would
On 23 Oct 2005, at 18:56, Pier Fumagalli wrote:
Ok, progress on Jira.
As requested, I added the workflow statuses that marks an issue as
on hold (when waiting for feedback) and continued meaning that
feedback was received and work should continue.
I'm waiting for the changes to propagate
Daniel Fagerstrom wrote:
* M2 stable enough (2.0 is out so this should be fullfilled)
* Reasonably fast (don't need to be as fast as Ant, but not several
times slower)
* Easy configuration of what blocks to compile (like blocks.properties
and maybe even dependency aware)
* M2 bundled
This is a test issue
Key: COCOON-1
URL: http://issues.apache.org/jira/browse/COCOON-1
Project: Cocoon
Type: Bug
Reporter: Pier Fumagalli
Assigned to: Cocoon Developers Team
This is a test issue to verify that Jira is correctly
[ http://issues.apache.org/jira/browse/COCOON-1?page=all ]
Pier Fumagalli reopened COCOON-1:
-
The issue is being reopened.
This is a test issue
Key: COCOON-1
URL:
[ http://issues.apache.org/jira/browse/COCOON-1?page=all ]
Pier Fumagalli deleted COCOON-1:
This is a test issue
Key: COCOON-1
URL: http://issues.apache.org/jira/browse/COCOON-1
Project: Cocoon
On 23 Oct 2005, at 19:36, Pier Fumagalli wrote:
On 23 Oct 2005, at 18:56, Pier Fumagalli wrote:
Ok, progress on Jira.
As requested, I added the workflow statuses that marks an issue as
on hold (when waiting for feedback) and continued meaning that
feedback was received and work should
Test issue
--
Key: COCOON-2
URL: http://issues.apache.org/jira/browse/COCOON-2
Project: Cocoon
Type: Bug
Reporter: Pier Fumagalli
Assigned to: Cocoon Developers Team
This is a test issue.
--
This message is automatically generated by JIRA.
-
If you
[
http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332916 ]
Pier Fumagalli commented on COCOON-2:
-
This is a comment without status workflow change.
Test issue
--
Key: COCOON-2
URL:
[ http://issues.apache.org/jira/browse/COCOON-2?page=all ]
Pier Fumagalli updated COCOON-2:
We're now requiring feedback, and the issue should be placed on hold.
Test issue
--
Key: COCOON-2
URL:
[
http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332918 ]
Pier Fumagalli commented on COCOON-2:
-
This is the feedback...
Test issue
--
Key: COCOON-2
URL: http://issues.apache.org/jira/browse/COCOON-2
[ http://issues.apache.org/jira/browse/COCOON-2?page=all ]
Pier Fumagalli updated COCOON-2:
Making a workflow change indicating that feedback was received.
Test issue
--
Key: COCOON-2
URL:
[
http://issues.apache.org/jira/browse/COCOON-2?page=comments#action_12332920 ]
Pier Fumagalli commented on COCOON-2:
-
Work is progressiong.
Test issue
--
Key: COCOON-2
URL: http://issues.apache.org/jira/browse/COCOON-2
[ http://issues.apache.org/jira/browse/COCOON-2?page=all ]
Pier Fumagalli closed COCOON-2:
---
Resolution: Fixed
I'm closing this issue for good...
Test issue
--
Key: COCOON-2
URL:
Hi,
On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote:
Just because of its importance, you agree that it is important
don't you ;) we should follow our usual and well proven development
patterns which involves community involvement.
FWIW, Sylvain showed quite a few people an example of
Daniel Fagerstrom wrote:
Joerg Heinicke wrote:
...
Ralph made a proposal [1] where exactly one block (= directory) per
block (= block in the narrower sense) exists, but with many modules
(in the maven sense) in them:
/src
/blocks
/cforms
/api
[ http://issues.apache.org/jira/browse/COCOON-2?page=all ]
Pier Fumagalli deleted COCOON-2:
Test issue
--
Key: COCOON-2
URL: http://issues.apache.org/jira/browse/COCOON-2
Project: Cocoon
Type: Bug
Everyone,
as of right now, BugZilla is closed for entries while I'm
migrating the content to Jira.
Please refrain for using BugZilla and/or Jira for bugs until the
import is finished.
Thank you for understanding.
Pier
smime.p7s
Description: S/MIME cryptographic signature
Jorg Heymans wrote:
Ralph Goers wrote:
/src
/blocks
/cforms
/api
pom.xml
/impl
pom/xml
/samples
pom.xml
/test
pom.xml
Andrew Savory wrote:
* We really need to get rid of obsolete stuff. Must really every
single block go to 2.2? Are there some oneman shows that better
could be returned to their creator and driven on source forge or
Cocoon-dev?
Hmm. I'm not convinced of this. The problem is that we
Ralph Goers wrote:
Andrew Savory wrote:
* We really need to get rid of obsolete stuff. Must really every
single block go to 2.2? Are there some oneman shows that better
could be returned to their creator and driven on source forge or
Cocoon-dev?
Hmm. I'm not convinced of this.
Upayavira wrote:
Basically, we relegate blocks not by removing or reducing them, but my
lifting others. We will have a background of many blocks, many one man
shows, half maintained ones, etc. However, we will also have lists
saying these are the cool ones, the ones that really work and are
Sylvain Wallez wrote:
I would also appreciate a crash course on how to add new dependencies in
trunk.
For the maven part, refer to
http://cocoon.zones.apache.org/daisy/documentation/756.html
Would you like to try it out with the new jdbi ? :-P
Regards
Jorg
Hi all,
I've started a daisy page on the current status and a bit more
background info
http://cocoon.zones.apache.org/daisy/documentation/756.html
We should probably find a proper location for this, so feel free to move
it around.
Jorg
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
Ralph Goers wrote:
There are easy ways to deal with that. Again, I am speaking from a
Maven 1 perspective since that is what I am very familiar with. My
understanding is that Maven 2 can do what Maven 1 can and more.
One way is to have each block have a pom which just does a multiproject
Bruno Dumon wrote:
Hi,
you might have seen the notification mails on the docs list for updates
to the forms documentation, but is probably easier if I explain what
I've done:
snip/
Great job Bruno!
I started filling some blanks, starting with Ajax and will continue next
week also!
Andrew Savory wrote:
On 23 Oct 2005, at 19:20, Daniel Fagerstrom wrote:
...
* We really need to get rid of obsolete stuff. Must really every
single block go to 2.2? Are there some oneman shows that better
could be returned to their creator and driven on source forge or
Cocoon-dev?
Daniel Fagerstrom wrote:
was: Super-easy SQL/Form integration for simple CRUD applications
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
Sylvain,
It seem to be great stuff, and something that we really need. But
being somewhat formalistic I'm a bit doubtfull about the timing. Ok,
you
Sylvain Wallez wrote:
Let me just explain how this works:
- I added two classes to CForms (about 3 weeks ago), namely
ContainerAsMap and RepeaterAsList. These classes are a Map and a List
implementations (live wrappers) on top of a container widget and a
repeater respectively.
- I added
Still mangling with a few unexpected things: it seems that the status
migration was wrong for the following issues:
Unable to determine the current status for issue 'COCOON-1571'.
Unable to determine the current status for issue 'COCOON-1564'.
Unable to determine the current status for issue
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=21177.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=23615.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29401.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29547.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30824.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33662.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33762.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35144.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35673.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35811.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35986.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
[ http://issues.apache.org/jira/browse/COCOON-1571?page=all ]
Pier Fumagalli deleted COCOON-1571:
---
[PATCH] NullPointerException in MultiValueField
---
Key: COCOON-1571
URL:
[ http://issues.apache.org/jira/browse/COCOON-1564?page=all ]
Pier Fumagalli deleted COCOON-1564:
---
[html block] HTMLGenerator doesn't copy POST parameters
---
Key: COCOON-1564
[ http://issues.apache.org/jira/browse/COCOON-1558?page=all ]
Pier Fumagalli deleted COCOON-1558:
---
[PATCH] Fix for validation-error tag in FormsTemplateTransformer
Key:
[ http://issues.apache.org/jira/browse/COCOON-1520?page=all ]
Pier Fumagalli deleted COCOON-1520:
---
Database / avalon problems
--
Key: COCOON-1520
URL: http://issues.apache.org/jira/browse/COCOON-1520
[ http://issues.apache.org/jira/browse/COCOON-1242?page=all ]
Pier Fumagalli deleted COCOON-1242:
---
XML serializer puts DOCTYPE after initial XML comments
--
Key: COCOON-1242
[ http://issues.apache.org/jira/browse/COCOON-1194?page=all ]
Pier Fumagalli deleted COCOON-1194:
---
FormsTransformer causes NPE
---
Key: COCOON-1194
URL: http://issues.apache.org/jira/browse/COCOON-1194
[ http://issues.apache.org/jira/browse/COCOON-1175?page=all ]
Pier Fumagalli deleted COCOON-1175:
---
xslt extension functions with bsf broken due to xalan-2.6 / bsf-2.3 conflict
[ http://issues.apache.org/jira/browse/COCOON-831?page=all ]
Pier Fumagalli deleted COCOON-831:
--
XSLTC doesn't work with nodeset functions
-
Key: COCOON-831
URL:
[ http://issues.apache.org/jira/browse/COCOON-740?page=all ]
Pier Fumagalli deleted COCOON-740:
--
a crash in the name() function of the xslt, when using SQL transformer
--
[ http://issues.apache.org/jira/browse/COCOON-1183?page=all ]
Pier Fumagalli deleted COCOON-1183:
---
can't use singleton classes in Continuable
--
Key: COCOON-1183
URL:
[ http://issues.apache.org/jira/browse/COCOON-1457?page=all ]
Pier Fumagalli deleted COCOON-1457:
---
jsp functionality broken in cocoon 2.1.7-dev, Tomcat 5.5.7, jdk1.5.0_01
---
[ http://issues.apache.org/jira/browse/COCOON-1451?page=all ]
Pier Fumagalli deleted COCOON-1451:
---
o.a.c.transformation.EncodeURLTransformer doesn't work
--
Key: COCOON-1451
On 23.10.2005 23:45, Ralph Goers wrote:
We are chosen as committers as induviduals and not as representants
for our companies. From a community stand point I would say that it is
time to deprecate the SQLTransformer. As a representative for my
company I would rather say: no way, we have tons
On Sun, Oct 23, 2005 at 11:19:06PM +0100, Pier Fumagalli wrote:
Still mangling with a few unexpected things: it seems that the status
migration was wrong for the following issues:
Unable to determine the current status for issue 'COCOON-1571'.
Unable to determine the current status for
On 24 Oct 2005, at 00:07, Jeff Turner wrote:
On Sun, Oct 23, 2005 at 11:19:06PM +0100, Pier Fumagalli wrote:
Still mangling with a few unexpected things: it seems that the status
migration was wrong for the following issues:
Unable to determine the current status for issue 'COCOON-1571'.
[ http://issues.apache.org/jira/browse/COCOON-1657?page=all ]
Pier Fumagalli moved CTEMP-740 to COCOON-1657:
--
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1657 (was: CTEMP-740)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1658?page=all ]
Pier Fumagalli moved CTEMP-831 to COCOON-1658:
--
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1658 (was: CTEMP-831)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1659?page=all ]
Pier Fumagalli moved CTEMP-1175 to COCOON-1659:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1659 (was: CTEMP-1175)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1661?page=all ]
Pier Fumagalli moved CTEMP-1194 to COCOON-1661:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1661 (was: CTEMP-1194)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1660?page=all ]
Pier Fumagalli moved CTEMP-1183 to COCOON-1660:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1660 (was: CTEMP-1183)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1662?page=all ]
Pier Fumagalli moved CTEMP-1242 to COCOON-1662:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1662 (was: CTEMP-1242)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Pier Fumagalli moved CTEMP-1451 to COCOON-1663:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1663 (was: CTEMP-1451)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Pier Fumagalli updated COCOON-1663:
---
Bugzilla Id: (was: 33662)
Description:
Not sure that EncodeURLTransformer is for xml/xslt with no xsp's in the mix,
but it certainly doesn't
[ http://issues.apache.org/jira/browse/COCOON-1664?page=all ]
Pier Fumagalli moved CTEMP-1457 to COCOON-1664:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1664 (was: CTEMP-1457)
Workflow: Cocoon Workflow (was: jira)
[ http://issues.apache.org/jira/browse/COCOON-1665?page=all ]
Pier Fumagalli moved CTEMP-1520 to COCOON-1665:
---
Project: Cocoon (was: Cocoon 2)
Key: COCOON-1665 (was: CTEMP-1520)
Workflow: Cocoon Workflow (was: jira)
1 - 100 of 116 matches
Mail list logo
