Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[David Crossley]

Our KEYS file is at https://dist.apache.org/repos/dist/release/cocoon/KEYS

Chris, please add yours to that one, rather than "replacing" it
as is indicated in your temporary KEYS file.

And extensive gratitude to you for taking on this task.

-David

On Sun, Oct 29, 2023 at 09:01:12PM +, Christofer Dutz wrote:
> Here’s the KEYS file … there wasn’t any, so I initialized it with my key.
> 
> https://dist.apache.org/repos/dist/dev/cocoon/KEYS
> 
> Chris
> 
> Von: Christofer Dutz 
> Datum: Sonntag, 29. Oktober 2023 um 21:09
> An: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> I added my key to the KEYS file in the svn repo one level up..
> 
> Gesendet von Outlook für Android
> 
> From: Peter Hunsberger 
> Sent: Sunday, October 29, 2023 6:16:02 PM
> To: dev@cocoon.apache.org 
> Cc: Cocoon PMC List 
> Subject: Re: [VOTE] Apache Cocoon 2.3.0 RC2 
> https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> 
> Everything looks good except I can't check the signature, I get "No public 
> key" from gpg.  I believe I need a copy of your public key to import?
> 
> Peter Hunsberger
> 
> 
> On Sun, Oct 29, 2023 at 6:55 AM Christofer Dutz 
> mailto:christofer.d...@c-ware.de>> wrote:
> 
> Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote
> 
> on accepting it for release. All Maven artifacts are available under [1].
> 
> Voting will be open for 72hr.
> 
> 
> 
> A minimum of 3 binding +1 votes and more binding +1 than binding -1
> 
> are required to pass.
> 
> 
> 
> Release tag: 
> https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/
> 
> Director revision of the tag: 1913422
> 
> 
> 
> Per [3] "Before voting +1 PMC members are required to download
> 
> the signed source code package, compile it as provided, and test
> 
> the resulting executable on their own platform, along with also
> 
> verifying that the package meets the requirements of the ASF policy
> 
> on releases."
> 
> 
> 
> You can achieve the above by following the guide of a fellow Apache project 
> [4].
> 
> 
> 
> [ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
> in [4])
> 
> [ ]  -1 reject (explanation required)
> 
> 
> 
> 
> 
> [1] https://repository.apache.org/content/repositories/orgapachecocoon-1007
> 
> [2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/
> 
> [3] https://www.apache.org/dev/release.html#approving-a-release
> 
> [4] 
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
> 
> 

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

[David Crossley]

Here is my +1

Checked on macOS, JDK 17.

-David
> 

Re: [DISCUSS] Set minimum JDK version to 1.5 for Cocoon 2.1

[David Crossley]

I agree. It should also enable better participation at both Cocoon
and at Apache Forrest. There were also many supporting products
that could then be updated. Lets go to 8.

-David

Insight 49 wrote:
> +1, and I strongly agree with Alfred.
> 
> Cocoon 2.1 is a good stable platform, but doesn't encourage new
> participation, partly I suspect, because many people and businesses
> run Java 8 or 7 (as you know, you get all kinds of build errors when
> trying to build cocoon using those Java versions).
> 
> If we can upgrade the code, classes and supporting jars, I'd recommend
> Java version 7 or 8.
> 
> As an example, the very successful Apache Solr search uses Java 8!
> 
> "You will need the Java Runtime Environment (JRE) version 1.8 or higher."
> https://cwiki.apache.org/confluence/display/solr/Installing+Solr
> 
> Dan
> 
> 
> On 10/7/16, Nathaniel, Alfred  wrote:
> > +1 but I would go straight to 6, 7, or even 8.
> > Past experience is that it is a real nuisance trying to support an ancient
> > JDK no developer is actually using anymore.
> >
> > Cheers, Alfred.
> >
> > -Original Message-
> > From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> > Sent: Freitag, 7. Oktober 2016 11:46
> > To: dev@cocoon.apache.org
> > Subject: [DISCUSS] Set minimum JDK version to 1.5 for Cocoon 2.1
> >
> > Hi all,
> > as recently noticed during the (unfortunately rejected) patch for
> > COCOON-2354 [1], it might make sense to upgrade the current minimum JDK
> > requirement for Cocoon 2.1 from 1.4 to 1.5, mainly to ease some upgrades
> > and help Cocoon 2.1 living in the modern world.
> >
> > Besides 3rd part library updates, some work could be needed to upgrade
> > our Java code, so help would be appreciated.
> 

Re: Upcoming releases

[David Crossley]

On Mon, Jun 06, 2016 at 03:16:58PM +0300, Johan Sjöberg wrote:
> Greetings.
> 
> Those filters seems to include 11 issues where 3 are reported as Bug. Of
> these two should IMO be checked, COCOON-2253 and COCOON-2246.

Thanks for the review. Hopefully a committer can do those.

I have not looked at other filters to see any suggested enhancements.

> So, the important thing would perhaps be to find consensus about what's
> gonna be in 2.1.13, is it branded as a library upgrade and Java 8 support
> release or that plus some new features?

There are some new features already. If others would like
to add or enhance anything then please provide patches.

Upgrading some supporting products would be good. We did do some
last time. For some (IIRC e.g. FOP) we would need to raise our
minimum Java version. Upgrading Ant would be good.

Also need to review the recent commits and patch $COCOON_HOME/status.xml
to notify any worthy changes.

> Are most who would like to see a
> 2.1.13 release waiting for official Java 8 support?

Deciding the minimum Java version is one of the early release
process steps. It would be better to have a separate mail thread.
Also we should review such discussion from last time.

I am not sure what you mean by "Java 8 support".

The main demos on our vm are okay:
http://cocoon.zones.apache.org

The HEAD of the current 2.1 branch does work for me,
but i did need to add this recently:
  http://svn.apache.org/r1623915
  Enable 'java' to be found on a modern Mac OS X.

> All in all, it doesn't
> look too bad. IOW, not too much stuff todo.
>
> Additionally I think it would be nice to have a configurable
> SaxParserFactory and a configurable DocumentBuilderFactory, to prevent some
> XEE attacks. I didn't find any in the code, but I might have missed it of
> course. That's low prio though, as it can be achieved with external
> implementations of the Factories registered in cocoon.xconf.

If someone can provide such an enhancement then that would be useful.

We should also provide some documentation to warn about such problems,
As alluded to earlier, our documentation system is busted.
So perhaps a Wiki page (could be moved to docs later).

e.g. remind to not process source xml docs that you do not control;
e.g. remind that Catalog Entity Resolver can assist; etc.
and link to articles like these:

Managing XML data: XML catalogs
http://www.ibm.com/developerworks/library/x-mxd3/

and 

Tip: Configure SAX parsers for secure processing
Prevent entity resolution vulnerabilities and overflow attacks
http://www.ibm.com/developerworks/xml/library/x-tipcfsx
... Oh crikey, it is 404. So need rescue of wayback machine
or find something similar.

-David

> Thoughts?
> 
> Cheers,
> 
> Johan
> 
> On Wed, Jun 1, 2016 at 6:40 AM, David Crossley <cross...@apache.org> wrote:
> 
> > On Tue, May 31, 2016 at 11:01:51PM +0300, Johan Sjöberg wrote:
> > >
> > > Referring to David’s message on the "user" list, there seems to be plans
> > > for Cocoon-2.1 and Cocoon-2.2 releases. That’s great!
> >
> > Thanks for your interest.
> >
> > It is a loose use of the term "plans", but yeah, these are the first steps.
> >
> > > What would be needed
> > > from "outsiders" to help with these, patches and testing, more?
> >
> > Reviewing these lists of issues:
> >
> > https://issues.apache.org/jira/issues/?filter=12310771
> > COCOON-open-with-patch
> > ... twiddle that filter to restrict to "Affects Version".
> >
> > https://issues.apache.org/jira/issues/?filter=12335814
> > COCOON-affects-2_1_12-and-2_1_13
> > ... general issues affecting recent 2.1
> >
> > Also, there would be some documentation tweaks needed.
> > However i am not clear about the state of our system.
> >
> > > Personally
> > > I would be interested in an official release of the 2.1 branch and will
> > > check what possible local changes I might have.
> >
> > I too am mainly interested in Cocoon-2.1
> >
> > Yes please do add to our JIRA issue tracker any changes that you
> > reckon are useful.
> >
> > You might need to be added to JIRA permissions. If so then please
> > contact the "private" mail list and tell us your JIRA username.
> >
> > Thanks again. Hopefully your efforts will encourage others.
> >
> > -David
> >

Re: Upcoming releases

[David Crossley]

On Tue, May 31, 2016 at 11:01:51PM +0300, Johan Sjöberg wrote:
> 
> Referring to David’s message on the "user" list, there seems to be plans
> for Cocoon-2.1 and Cocoon-2.2 releases. That’s great!

Thanks for your interest.

It is a loose use of the term "plans", but yeah, these are the first steps.

> What would be needed
> from "outsiders" to help with these, patches and testing, more?

Reviewing these lists of issues:

https://issues.apache.org/jira/issues/?filter=12310771
COCOON-open-with-patch
... twiddle that filter to restrict to "Affects Version".

https://issues.apache.org/jira/issues/?filter=12335814
COCOON-affects-2_1_12-and-2_1_13
... general issues affecting recent 2.1

Also, there would be some documentation tweaks needed.
However i am not clear about the state of our system.

> Personally
> I would be interested in an official release of the 2.1 branch and will
> check what possible local changes I might have.

I too am mainly interested in Cocoon-2.1

Yes please do add to our JIRA issue tracker any changes that you
reckon are useful.

You might need to be added to JIRA permissions. If so then please
contact the "private" mail list and tell us your JIRA username.

Thanks again. Hopefully your efforts will encourage others.

-David

new mail archives interface

[David Crossley]

At the recent ApacheCon conference, the new mail archives interface was 
unveiled.

See https://lists.apache.org/

See the mention at the weekly article "The Apache News Round-up"
https://blogs.apache.org/foundation/entry/the_apache_news_round_up85

-David

[REMINDER] ApacheCon NA 2016 Travel Assistance Applications now open!

[David Crossley]

The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon North America 2016 are now open! This
announcement serves as a purpose for you (pmcs@) to let members of your
community know about both ApacheConNA 2016 and about the TAC assistance to
attend. Could you please forward this announcement to your community,
along  with (if possible) information on how your project is involved in
ApacheCon this year?

We will be supporting ApacheCon NA, Vancouver BC, May 9th - 13th 2016.

TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons. For more info on this years
applications and qualifying criteria please visit the TAC website at <
http://www.apache.org/travel/ >.   Applications are already open, so don't
delay!

*Important dates*...

   - CFP Close: February 12, 2016
   - CFP Notifications: February 29, 2016
   - TAC Applications close:  March 2, 2016
   - Schedule Announced: March 3, 2016

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as required
to efficiently and accurately process your request), this will enable TAC
to announce successful awards shortly afterwards.

As usual TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.

We look forward to greeting many of you in Vancouver, BC in May 2016!

Kind Regards

Lewis

(On behalf of the Travel Assistance Committee)

early registration for ApacheCon in Austin Texas

[David Crossley]

Dear Apache Cocoon enthusiast,

In just a few weeks, we'll be holding ApacheCon in Austin, Texas, and
we'd love to have you in attendance. You can save $300 on admission by
registering NOW, since the early bird price ends on the 21st.

Register at http://s.apache.org/acna2015-reg

ApacheCon this year celebrates the 20th birthday of the Apache HTTP
Server, and we'll have Brian Behlendorf, who started this whole thing,
keynoting for us, and you'll have a chance to meet some of the original
Apache Group, who will be there to celebrate with us.

We've got 7 tracks of great talks, as well as BOFs, the Apache BarCamp,
project-specific hack events, and evening events where you can deepen
your connection with the larger Apache community. See the full schedule
at http://apacheconna2015.sched.org/

And if you have any questions, comments, or just want to hang out with
us before and during the event, follow us on Twitter - @apachecon - or
drop by #apachecon on the Freenode IRC network.

Hope to see you in Austin!

sitemap trouble when deploy cocoon-2.1 war in tomcat

[David Crossley]

I am having difficulty deploying a cocoon.war to a local Tomcat (using recent 
v7.0.55).

To start with, see the Cocoon jail demo:

http://cocoon.zones.apache.org/cocoon21/samples/
and notice how the trailing slash just works okay
as it should according to the sitemap.xmap

Now when i build Cocoon 2.1.13-dev (head of svn branch) locally,
and then do:
]$ ./cocoon.sh
http://localhost:/samples/
all is okay using the built-in Jetty.

Now do:
]$ ./build.sh war
then copy to the Tomcat webapps directory.
http://localhost:8080/cocoon/samples/
and get error:
org.apache.cocoon.ResourceNotFoundException: No pipeline matched request: 
samples/index.html

Looking at the docs for the cocoon.zones.apache.org at
http://wiki.apache.org/cocoon/JailManagement
https://svn.apache.org/repos/private/pmc/cocoon/cocoon.zones.apache.org/
i do not see any special configuration for Tomcat.

So can anyone explain the difference.

Also does anyone know how that redirect to index.html is happening.

I do vaguely recall these problems in the past.

-David

Re: sitemap trouble when deploy cocoon-2.1 war in tomcat

[David Crossley]

On Tue, Sep 02, 2014 at 09:56:07AM +0200, Francesco Chicchiriccò wrote:
 On 02/09/2014 09:53, David Crossley wrote:
 I am having difficulty deploying a cocoon.war to a local Tomcat (using 
 recent v7.0.55).
 
 To start with, see the Cocoon jail demo:
 
 http://cocoon.zones.apache.org/cocoon21/samples/
 and notice how the trailing slash just works okay
 as it should according to the sitemap.xmap
 
 Now when i build Cocoon 2.1.13-dev (head of svn branch) locally,
 and then do:
 ]$ ./cocoon.sh
 http://localhost:/samples/
 all is okay using the built-in Jetty.
 
 Now do:
 ]$ ./build.sh war
 then copy to the Tomcat webapps directory.
 http://localhost:8080/cocoon/samples/
 and get error:
 org.apache.cocoon.ResourceNotFoundException: No pipeline matched request: 
 samples/index.html
 
 Looking at the docs for the cocoon.zones.apache.org at
 http://wiki.apache.org/cocoon/JailManagement
 https://svn.apache.org/repos/private/pmc/cocoon/cocoon.zones.apache.org/
 i do not see any special configuration for Tomcat.
 
 So can anyone explain the difference.
 
 Also does anyone know how that redirect to index.html is happening.
 
 I do vaguely recall these problems in the past.
 
 Hi David,
 can [1] be of any help?
 
 [1] http://blog.tirasa.net/apache-fun-cocoon-2-1.html

You are a champ. Yes it does.

Remove the welcome-file-list from $CATALINA_HOME/conf/web.xml

What a team. I have been struggling all afternoon,
then an answer in minutes. Thanks.

-David

 -- 
 Francesco Chicchiriccò
 
 Tirasa - Open Source Excellence
 http://www.tirasa.net/
 
 Involved at The Apache Software Foundation:
 member, Syncope PMC chair, Cocoon PMC, Olingo PMC
 http://people.apache.org/~ilgrosso/
 

Re: Update Cocoon 2.1.13-dev dojo up to 1.9.3

[David Crossley]

Francesco Chicchiriccò wrote:
 Reynaldo Porras García wrote:
 Dear cocooners,
 
 I am working on upgrading a app for a client. We have found issues with
 recent browsers and dojo 0.4.3 which comes in cocoon. I am working on
 updating dojo to it latest version 1.9.3 which the latest available.
 
 I know there was some work going to update cocoon 2.1 to use dojo 1.1.1
 [1] long time ago. I am looking at the branch [2] and the work looks
 promising. I am planning to use that branch to move dojo up to 1.9.3.
 But I see the branch is behind current development branch[3]. Is it
 possible to add merge changes from current development branch to the
 dojo branch?
 
 Last change in branch [2] is dated 2008-11-05 16:06:50 +0100, e.g. 5 
 years and a half ago: I have just merged without particular problems [4] 
 - everything seems to be working, but I am sure it worths more 
 investigation that I assume you are going to perform, right? ;-)
 
 Regards.
 
 Any suggestions or ideas?

Perhaps contact the people who were involved in that branch.
Maybe they have some unfinished work or dump of ideas.

Thanks to Reynaldo for attending to Cocoon-2.1 ... it has life yet.

Thanks too to Francesco.

-David

 [1] - 
 http://markmail.org/message/iatwhjzsa53skbdz?q=apache+cocoon+%2B+dojo+1.1+%2B+jeremy
 [2] - http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X-dojo1_1/
 [3] - http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
 [4] http://svn.apache.org/r1573205

Re: Your Gump Build(s)

[David Crossley]

Reminder to the Cocoon project:

We have a number of Gump builds:
See http://svn.apache.org/repos/asf/gump/metadata/project/
for the cocoon entries.

For example, the output from the vmgump machine is here:
http://vmgump.apache.org/gump/public/cocoon3/
and
http://vmgump.apache.org/gump/public/cocoon/ for c2.2
(IIRC then cocoon-2.1 is packaged rather than built.)

The metadata for each Cocoon project probably
needs some care and attention from us.

-David

Stefan Bodewig wrote:
 Dear Community
 
 Apache Gump builds some of your projects and it is quite possible you
 don't know or have by now forgotten about it.
 
 More than half a year ago a technical problem has forced us to turn off
 emails on build failures as we would have been sending out lots of false
 alarms.
 
 Before we re-enable emails we'd like to know whether you are still
 interested in the service Gump provides, so please tell us. :-)
 
 Metadata for many projects have been neglected for a long time and it is
 quite possible they'd need some love for results to be meaningful.  All
 Apache committers have write access to Gump's metadata.
 
 In case you don't know what this Gump stuff is about:
 
 Apache Gump builds the full stack of the latest commits of software in
 order to ensure integrity over releases.  Build failures surface API
 discontinuities between projects before they impact releases, and Gump's
 e-mail notifications hope to promote the conversations between teams to
 resolve those discontinuities.
 
 When responding to this mail please shorten the CC list as appropriate.
 
 Cheers
 
 Stefan
 
  on behalf of the Gump PMC
 

Re: Your Gump Build(s)

[David Crossley]

David Crossley wrote:

 Reminder to the Cocoon project:
 
 We have a number of Gump builds:
 See http://svn.apache.org/repos/asf/gump/metadata/project/
 for the cocoon entries.
 
 For example, the output from the vmgump machine is here:
 http://vmgump.apache.org/gump/public/cocoon3/

At the moment Cocoon3 is failing with a complaint
that seems to be related to FOP.
See http://vmgump.apache.org/gump/public/cocoon3/
and follow the link to cocoon-optional (which the other
cocoon parts depend upon). Then follow the link to
the build_cocoon3_cocoon-optional output which has the detail.

-David

 and
 http://vmgump.apache.org/gump/public/cocoon/ for c2.2
 (IIRC then cocoon-2.1 is packaged rather than built.)
 
 The metadata for each Cocoon project probably
 needs some care and attention from us.
 
 -David
 
 Stefan Bodewig wrote:
  Dear Community
  
  Apache Gump builds some of your projects and it is quite possible you
  don't know or have by now forgotten about it.
  
  More than half a year ago a technical problem has forced us to turn off
  emails on build failures as we would have been sending out lots of false
  alarms.
  
  Before we re-enable emails we'd like to know whether you are still
  interested in the service Gump provides, so please tell us. :-)
  
  Metadata for many projects have been neglected for a long time and it is
  quite possible they'd need some love for results to be meaningful.  All
  Apache committers have write access to Gump's metadata.
  
  In case you don't know what this Gump stuff is about:
  
  Apache Gump builds the full stack of the latest commits of software in
  order to ensure integrity over releases.  Build failures surface API
  discontinuities between projects before they impact releases, and Gump's
  e-mail notifications hope to promote the conversations between teams to
  resolve those discontinuities.
  
  When responding to this mail please shorten the CC list as appropriate.
  
  Cheers
  
  Stefan
  
   on behalf of the Gump PMC
  

Re: Your Gump Build(s)

[David Crossley]

Francesco Chicchiriccò wrote:
 David Crossley wrote:
 
 Reminder to the Cocoon project:
 
 We have a number of Gump builds:
 See http://svn.apache.org/repos/asf/gump/metadata/project/
 for the cocoon entries.
 
 For example, the output from the vmgump machine is here:
 http://vmgump.apache.org/gump/public/cocoon3/
 and
 http://vmgump.apache.org/gump/public/cocoon/ for c2.2
 (IIRC then cocoon-2.1 is packaged rather than built.)
 
 The metadata for each Cocoon project probably
 needs some care and attention from us.
 
 Hi David,
 I am not familiar with Gump at all, but at least for Cocoon 3 [1] and 
 Cocoon 2.1 [2] we have Jenkins jobs defined.

Gump is very different. See Stefan's message below.

I reckon that both are useful in different ways.

-David

 I don't think we still need Gump, at least for C3 and C2.1 (and we might 
 define a job on Jenkins for C2.2 as well), right?
 
 WDYT? Should we safely remove cocoon entries from Gump? How could this 
 be done?
 
 Regards.
 
 [1] https://builds.apache.org/job/Cocoon%203.0/
 [2] https://builds.apache.org/job/Cocoon%202.1.X/
 
 Stefan Bodewig wrote:
 Dear Community
 
 Apache Gump builds some of your projects and it is quite possible you
 don't know or have by now forgotten about it.
 
 More than half a year ago a technical problem has forced us to turn off
 emails on build failures as we would have been sending out lots of false
 alarms.
 
 Before we re-enable emails we'd like to know whether you are still
 interested in the service Gump provides, so please tell us. :-)
 
 Metadata for many projects have been neglected for a long time and it is
 quite possible they'd need some love for results to be meaningful.  All
 Apache committers have write access to Gump's metadata.
 
 In case you don't know what this Gump stuff is about:
 
 Apache Gump builds the full stack of the latest commits of software in
 order to ensure integrity over releases.  Build failures surface API
 discontinuities between projects before they impact releases, and Gump's
 e-mail notifications hope to promote the conversations between teams to
 resolve those discontinuities.
 
 When responding to this mail please shorten the CC list as appropriate.
 
 Cheers
 
  Stefan
 
   on behalf of the Gump PMC
 
 -- 
 Francesco Chicchiriccò
 
 ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
 http://people.apache.org/~ilgrosso/
 

Re: Your Gump Build(s)

[David Crossley]

David Crossley wrote:
 Francesco Chicchiriccò wrote:
  David Crossley wrote:
  
  Reminder to the Cocoon project:
  
  We have a number of Gump builds:
  See http://svn.apache.org/repos/asf/gump/metadata/project/
  for the cocoon entries.
  
  For example, the output from the vmgump machine is here:
  http://vmgump.apache.org/gump/public/cocoon3/
  and
  http://vmgump.apache.org/gump/public/cocoon/ for c2.2
  (IIRC then cocoon-2.1 is packaged rather than built.)
  
  The metadata for each Cocoon project probably
  needs some care and attention from us.
  
  Hi David,
  I am not familiar with Gump at all, but at least for Cocoon 3 [1] and 
  Cocoon 2.1 [2] we have Jenkins jobs defined.
 
 Gump is very different. See Stefan's message below.
 
 I reckon that both are useful in different ways.

This is the description from their home page:
Gump is unique in that it builds and compiles software against the latest 
development versions of those projects. This allows gump to detect potentially 
incompatible changes to that software just a few hours after those changes are 
checked into the version control system.

and from their Board reports:
Apache Gump is a cross-project continuous integration server. Gump's intention 
isn't so much to be a CI server but rather a vehicle that makes people look 
beyond their project's boundaries and helps the projects to collaborate.

-David

  I don't think we still need Gump, at least for C3 and C2.1 (and we might 
  define a job on Jenkins for C2.2 as well), right?
  
  WDYT? Should we safely remove cocoon entries from Gump? How could this 
  be done?
  
  Regards.
  
  [1] https://builds.apache.org/job/Cocoon%203.0/
  [2] https://builds.apache.org/job/Cocoon%202.1.X/
  
  Stefan Bodewig wrote:
  Dear Community
  
  Apache Gump builds some of your projects and it is quite possible you
  don't know or have by now forgotten about it.
  
  More than half a year ago a technical problem has forced us to turn off
  emails on build failures as we would have been sending out lots of false
  alarms.
  
  Before we re-enable emails we'd like to know whether you are still
  interested in the service Gump provides, so please tell us. :-)
  
  Metadata for many projects have been neglected for a long time and it is
  quite possible they'd need some love for results to be meaningful.  All
  Apache committers have write access to Gump's metadata.
  
  In case you don't know what this Gump stuff is about:
  
  Apache Gump builds the full stack of the latest commits of software in
  order to ensure integrity over releases.  Build failures surface API
  discontinuities between projects before they impact releases, and Gump's
  e-mail notifications hope to promote the conversations between teams to
  resolve those discontinuities.
  
  When responding to this mail please shorten the CC list as appropriate.
  
  Cheers
  
   Stefan
  
on behalf of the Gump PMC
  
  -- 
  Francesco Chicchiriccò
  
  ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
  http://people.apache.org/~ilgrosso/
  

[jira] [Commented] (COCOON3-125) Missing support for Catalog Resolver

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON3-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673762#comment-13673762
 ] 

David Crossley commented on COCOON3-125:


I cannot help much at this time, other than to ensure awareness of previous 
efforts. I was involved with getting the original Catalog Entity Resolver into 
Cocoon-2.1 and you will find good docs and cocoon samples. Pretty sure that the 
Samples with Cocoon-2.2 also work.

IIRC then there was some discussion in the early days of Cocoon3/Corona. All 
that i have time for is to give some pointers to search, e.g. the following 
with Google:
site:gmane.org/gmane.text.xml.cocoon entity resolver carsten
site:gmane.org/gmane.text.xml.cocoon entity resolver crossley



 Missing support for Catalog Resolver
 

 Key: COCOON3-125
 URL: https://issues.apache.org/jira/browse/COCOON3-125
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Mansour Al Akeel
Priority: Minor
 Fix For: 3.0.0-beta-1

 Attachments: CatalogResolver-support.diff


 When we load xml document using org.apache.cocoon.sax.util.XMLUtils.toSax, 
 and the XML document has a link to a DTD, the parser fails if the DTD is not 
 in the specified location. To solve this issue, a CatalogManager.properties 
 can be used. The same thing if we are using document() function from an xslt 
 and loaded document has a DTD. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON3-125) Missing support for Catalog Resolver

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON3-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673892#comment-13673892
 ] 

David Crossley commented on COCOON3-125:


For example:

http://s.apache.org/9bz
From: Carsten Ziegeler
Subject: Core XML Module
Date: 2008-04-08

Not sure what happened after that regarding actual code.

 Missing support for Catalog Resolver
 

 Key: COCOON3-125
 URL: https://issues.apache.org/jira/browse/COCOON3-125
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Mansour Al Akeel
Priority: Minor
 Fix For: 3.0.0-beta-1

 Attachments: CatalogResolver-support.diff


 When we load xml document using org.apache.cocoon.sax.util.XMLUtils.toSax, 
 and the XML document has a link to a DTD, the parser fails if the DTD is not 
 in the specified location. To solve this issue, a CatalogManager.properties 
 can be used. The same thing if we are using document() function from an xslt 
 and loaded document has a DTD. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release Cocoon 2.1.12

[David Crossley]

Cédric Damioli wrote:
 
 I've put the files at http://people.apache.org/~cdamioli/cocoon-2.1.12/
 
 Please check the files, build and run samples, and cast your votes.

+1 from me for cocoon-2.1.12-src.tar.gz MD5 8f86915b851df0405fa52dbe249bd3da

Thanks.

There are some small things that can be fixed after this release.
e.g. Apache Software License in deps/LICENSE.txt should be Apache License.

Your key should get signed by someone else.

We could follow what Subversion does. The multiple signatures
would assist with that issue.
http://subversion.apache.org/docs/community-guide/releasing.html#tarball-signing

Also i see that rather than using a static KEYS file,
they link directly from their download page to the set of current keys.

Anyway, stuff for next time.

Thanks again.

-David

Re: please add me to the wiki ContributorsGroup

[David Crossley]

Francesco Chicchiriccò wrote:
 David Crossley wrote:
 
 Would someone please add me to the ContributorsGroup of the Cocoon wiki
 http://wiki.apache.org/cocoon/ContributorsGroup
 as DavidCrossley
 
 Done.
 Please let me know if it has worked.

Yes the Edit link is now shown.

Thanks.

-David

please add me to the wiki ContributorsGroup

[David Crossley]

Would someone please add me to the ContributorsGroup of the Cocoon wiki
http://wiki.apache.org/cocoon/ContributorsGroup
as DavidCrossley

-David

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

Cédric Damioli wrote:
 Francesco Chicchiriccò a écrit :
  David Crossley wrote:
 
 I am busy for the next two weeks, being away for the second.
 Now half-way through testing Forrest using the recently updated
 Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.
 
 ...guess it's wise to wait for you to finish such tests before 
 starting the actual release process ;-)
 
 Indeed :)

;-)
I only have time for some quick look and testing.
Done that now, and my local Forrest seems happy.

There are some svg-to-png errors from Batik, but other
svg-to-png is okay, so assuming that that is a Forrest issue.

-David

 I see that final touches were recently added to
 http://www.apache.org/dev/licensing-howto.html
 https://issues.apache.org/jira/browse/INCUBATOR-125
 
 I think our recent work is still compliant with that. WDYT ?
 
 Regards,
 Cédric

[jira] [Created] (COCOON-2335) samples in asciiart block are missing the text in the generated images

[David Crossley (JIRA)]

David Crossley created COCOON-2335:
--

 Summary: samples in asciiart block are missing the text in the 
generated images
 Key: COCOON-2335
 URL: https://issues.apache.org/jira/browse/COCOON-2335
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: ASCII Art
Affects Versions: 2.1.12
Reporter: David Crossley


The generated PNG and JPEG images do show each box outline, but the text within 
those boxes is not generated.

We also see this issue at Apache Forrest where we use the Cocoon Asciiart Block.

This is not a new issue. We noticed it at least three months ago.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (COCOON-2335) samples in asciiart block are missing the text in the generated images

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley closed COCOON-2335.
--

   Resolution: Invalid
Fix Version/s: 2.1.12

Ah, that was using Java 5. If i go back to Java 1.4.2 (which is the version for 
Cocoon-2.1.12+) then all is well.

 samples in asciiart block are missing the text in the generated images
 --

 Key: COCOON-2335
 URL: https://issues.apache.org/jira/browse/COCOON-2335
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: ASCII Art
Affects Versions: 2.1.12
Reporter: David Crossley
 Fix For: 2.1.12


 The generated PNG and JPEG images do show each box outline, but the text 
 within those boxes is not generated.
 We also see this issue at Apache Forrest where we use the Cocoon Asciiart 
 Block.
 This is not a new issue. We noticed it at least three months ago.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (COCOON-2295) Integrate FOP 1.0

[David Crossley]

Francesco Chicchiriccò (JIRA) wrote:
 
 [ 
 https://issues.apache.org/jira/browse/COCOON-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578204#comment-13578204
  ] 
 
 Francesco Chicchiriccò commented on COCOON-2295:
 
 
 According to [1] FOP 1.1 still requires JDK 1.4.
 
 If the patch looks fine, I'd commit and close this issue.
 
 [1] http://xmlgraphics.apache.org/fop/1.1/running.html

I just tried building Cocoon-2.1 using Java 1.4.2
and get complaints from the Cocoon FOP Block:
--
/cocoon_2_1/src/blocks/fop/java/org/apache/cocoon/serialization/FOPSerializer.java:34:
 cannot access org.apache.fop.apps.FOPException
bad class file: 
/cocoon_2_1/lib/optional/fop-1.1.jar(org/apache/fop/apps/FOPException.class)
class file has wrong version 49.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the 
classpath.
import org.apache.fop.apps.FOPException;
--

However the block is okay when using Java 5.

-David

  Integrate FOP 1.0
  -
 
  Key: COCOON-2295
  URL: https://issues.apache.org/jira/browse/COCOON-2295
  Project: Cocoon
   Issue Type: Improvement
   Components: Blocks: Batik, Blocks: FOP
 Affects Versions: 2.1.12
 Reporter: ron van den branden
 Assignee: Francesco Chicchiriccò
  Fix For: 2.1.12
 
  Attachments: COCOON-2295-FOP_1_1.patch, COCOON-2295.patch, 
  jars.patch, jars.xml
 
 
  Here are instructions for updating the current FOP-0.95 serializer in 
  Cocoon-2.1.12-dev (see https://issues.apache.org/jira/browse/COCOON-2289):
  1. checkout http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
  2. download (and build) FOP-1.0 from 
  http://xmlgraphics.apache.org/fop/download.html
  3. update jars in %COCOON_HOME%\lib\*:
  -replace %COCOON_HOME%\lib\optional\batik-all-1.6.jar with 
  %FOP_HOME%\lib\batik-all-1.7.jar
  -replace %COCOON_HOME%\lib\optional\fop-0.95.jar with 
  %FOP_HOME%\build\fop.jar
  -replace %COCOON_HOME%\lib\optional\xmlgraphics-commons-1.3.1.jar with 
  %FOP_HOME%\lib\xmlgraphics-commons-1.4.jar
  -copy %FOP_HOME%\lib\xml-apis-ext-1.3.04.jar to 
  %COCOON_HOME%\lib\endorsed
  -copy %FOP_HOME%\lib\serializer-2.7.0.jar to %COCOON_HOME%\lib\optional
  4. update references to these jars in %COCOON_HOME%\lib\jars.xml (see 
  attached file)
  5. build Cocoon
 
 --
 This message is automatically generated by JIRA.
 If you think it was sent incorrectly, please contact your JIRA administrators
 For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.

I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125

-David

[jira] [Comment Edited] (COCOON-2295) Integrate FOP 1.0

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578164#comment-13578164
 ] 

David Crossley edited comment on COCOON-2295 at 2/14/13 5:20 AM:
-

According to the notes related to COCOON-2333, then FOP 1.0 is the last release 
for Java 1.4 (our required version). I hope that is wrong and we can move to 
FOP 1.1

  was (Author: crossley):
According to the notes related to COCOON-2333, then FOP-1.0 is the last 
release for Java 1.4 (our required version). I hope that is wrong and we can 
move to FOP-1.1
  
 Integrate FOP 1.0
 -

 Key: COCOON-2295
 URL: https://issues.apache.org/jira/browse/COCOON-2295
 Project: Cocoon
  Issue Type: Improvement
  Components: Blocks: Batik, Blocks: FOP
Affects Versions: 2.1.12
Reporter: ron van den branden
Assignee: Francesco Chicchiriccò
 Fix For: 2.1.12

 Attachments: COCOON-2295-FOP_1_1.patch, COCOON-2295.patch, 
 jars.patch, jars.xml


 Here are instructions for updating the current FOP-0.95 serializer in 
 Cocoon-2.1.12-dev (see https://issues.apache.org/jira/browse/COCOON-2289):
 1. checkout http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
 2. download (and build) FOP-1.0 from 
 http://xmlgraphics.apache.org/fop/download.html
 3. update jars in %COCOON_HOME%\lib\*:
 -replace %COCOON_HOME%\lib\optional\batik-all-1.6.jar with 
 %FOP_HOME%\lib\batik-all-1.7.jar
 -replace %COCOON_HOME%\lib\optional\fop-0.95.jar with 
 %FOP_HOME%\build\fop.jar
 -replace %COCOON_HOME%\lib\optional\xmlgraphics-commons-1.3.1.jar with 
 %FOP_HOME%\lib\xmlgraphics-commons-1.4.jar
 -copy %FOP_HOME%\lib\xml-apis-ext-1.3.04.jar to %COCOON_HOME%\lib\endorsed
 -copy %FOP_HOME%\lib\serializer-2.7.0.jar to %COCOON_HOME%\lib\optional
 4. update references to these jars in %COCOON_HOME%\lib\jars.xml (see 
 attached file)
 5. build Cocoon

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2295) Integrate FOP 1.0

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578164#comment-13578164
 ] 

David Crossley commented on COCOON-2295:


According to the notes related to COCOON-2333, then FOP-1.0 is the last release 
for Java 1.4 (our required version). I hope that is wrong and we can move to 
FOP-1.1

 Integrate FOP 1.0
 -

 Key: COCOON-2295
 URL: https://issues.apache.org/jira/browse/COCOON-2295
 Project: Cocoon
  Issue Type: Improvement
  Components: Blocks: Batik, Blocks: FOP
Affects Versions: 2.1.12
Reporter: ron van den branden
Assignee: Francesco Chicchiriccò
 Fix For: 2.1.12

 Attachments: COCOON-2295-FOP_1_1.patch, COCOON-2295.patch, 
 jars.patch, jars.xml


 Here are instructions for updating the current FOP-0.95 serializer in 
 Cocoon-2.1.12-dev (see https://issues.apache.org/jira/browse/COCOON-2289):
 1. checkout http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
 2. download (and build) FOP-1.0 from 
 http://xmlgraphics.apache.org/fop/download.html
 3. update jars in %COCOON_HOME%\lib\*:
 -replace %COCOON_HOME%\lib\optional\batik-all-1.6.jar with 
 %FOP_HOME%\lib\batik-all-1.7.jar
 -replace %COCOON_HOME%\lib\optional\fop-0.95.jar with 
 %FOP_HOME%\build\fop.jar
 -replace %COCOON_HOME%\lib\optional\xmlgraphics-commons-1.3.1.jar with 
 %FOP_HOME%\lib\xmlgraphics-commons-1.4.jar
 -copy %FOP_HOME%\lib\xml-apis-ext-1.3.04.jar to %COCOON_HOME%\lib\endorsed
 -copy %FOP_HOME%\lib\serializer-2.7.0.jar to %COCOON_HOME%\lib\optional
 4. update references to these jars in %COCOON_HOME%\lib\jars.xml (see 
 attached file)
 5. build Cocoon

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2330) Release separate source and dependencies packages

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570802#comment-13570802
 ] 

David Crossley commented on COCOON-2330:


Cocoon-2.1 has been using a file called CREDITS.txt which also contains the 
stuff that belongs in NOTICE.txt file. Some of it might be relevant for the 
src package NOTICE file, while the rest belongs in the deps package NOTICE 
file.

There is a new document which attempts to explain both NOTICE and LICENSE.


 Release separate source and dependencies packages
 -

 Key: COCOON-2330
 URL: https://issues.apache.org/jira/browse/COCOON-2330
 Project: Cocoon
  Issue Type: Improvement
  Components: - Build System: Ant
Affects Versions: 2.1.11
Reporter: Francesco Chicchiriccò
 Fix For: 2.1.12


 As recently reported by David Corssley [1] the 2.1.X release must comply with 
 ASF policies about releases, in particular providing a separate source code 
 package (without any external JAR file inside) and dependencies package (with 
 all external JAR files) for distribution.
 [1] http://markmail.org/message/f6rm2ca35eiraf7i

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (COCOON-2330) Release separate source and dependencies packages

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13570802#comment-13570802
 ] 

David Crossley edited comment on COCOON-2330 at 2/5/13 12:44 AM:
-

Cocoon-2.1 has been using a file called CREDITS.txt which also contains the 
stuff that belongs in NOTICE.txt file. Some of it might be relevant for the 
src package NOTICE file, while the rest belongs in the deps package NOTICE 
file.

There is a new document which attempts to explain both NOTICE and LICENSE.
http://www.apache.org/dev/licensing-howto.html

  was (Author: crossley):
Cocoon-2.1 has been using a file called CREDITS.txt which also contains the 
stuff that belongs in NOTICE.txt file. Some of it might be relevant for the 
src package NOTICE file, while the rest belongs in the deps package NOTICE 
file.

There is a new document which attempts to explain both NOTICE and LICENSE.

  
 Release separate source and dependencies packages
 -

 Key: COCOON-2330
 URL: https://issues.apache.org/jira/browse/COCOON-2330
 Project: Cocoon
  Issue Type: Improvement
  Components: - Build System: Ant
Affects Versions: 2.1.11
Reporter: Francesco Chicchiriccò
 Fix For: 2.1.12


 As recently reported by David Corssley [1] the 2.1.X release must comply with 
 ASF policies about releases, in particular providing a separate source code 
 package (without any external JAR file inside) and dependencies package (with 
 all external JAR files) for distribution.
 [1] http://markmail.org/message/f6rm2ca35eiraf7i

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: 2.12 Release: Additions to COCOON-2333 (list of current jars)

[David Crossley]

Francesco Chicchiriccò wrote:
 insigh...@gmail.com wrote:
 
 Was looking through the list of 2.1.12 jars, and notice that many of 
 the jars are quite old.
 
 https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup
  
 
 I also notice that my additions (sent 11 Dec) are not included.

See this dev mail list. On that same day i made efforts to
include some of your notes. See also the commits notifications
mail list around that time, where your contributions were
specifically acknowledged.

As explained by various people, the Java version limitation
must remain. I re-reviewed the list at that time, changed the
format of the notes, and noted the maximum version available
for some of the dependencies.

-David

 What are the plans to upgrade the jars before the 2.1.12 release?
 
 Hi,
 the plans are the ones contained in the SVN link you've reported above: 
 consider that 2.1.12 will run on JDK 1.4, hence even JAR files must 
 comply with this.
 
 I cannot find your additions sent 11 Dec: would you mind to add these 
 as comment to COCOON-2333 in the format of the SVN link above, or - 
 better - as SVN patch? Thanks.
 
 Regards.
 
 -- 
 Francesco Chicchiriccò
 
 ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
 http://people.apache.org/~ilgrosso/
 

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

Francesco Chicchiriccò wrote:
 Cédric Damioli wrote:
 Hi there,
 
 AFAIK the same 3 issues are still opened. Could you give me a hint 
 about the src/bin split?
 
 COCOON-2330 - Could you please tell me (again) how to generate the 
 source and deps packages from SVN? Thanks.

Do ./build.sh dist.

There will also need to be different NOTICE and LICENSE
files for each package.

 Apart, there's the David issue about upgrading all dependencies. I 
 don't know the status of it.
 
 COCOON-2333 - According to [2], there are still few deps to check. I 
 remember I've asked David about how to contribute on this an he said 
 something like update the JAR file an browse if samples still work

See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.

Also the issue is about some dependencies, not all.
For example FOP, Batik, etc. would be good if possible.

 And also an samples issue reopened by David. I don't know either what 
 to do with it.
 
 COCOON-2069 - David, what should we do with this?

See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.

-David

 Regards.
 
 Le 19/01/2013 15:11, Francesco Chicchiriccò a écrit :
 On 11/12/2012 12:29, Cédric Damioli wrote:
 [...]
 Hi all,
 is everything tracked into JIRA [1]?
 From my POV, yes.
 I've added some comments to COCOON-2330. I'm not sure what to 
 include or exclude from the -src package.
 
 
 If so, we are only 3 issues away from releasing 2.1.12, wonderful!
 
 Hello there,
 how's the situation with C2.1.12 in 2013? Any help needed?
 
 Regards.
 
 [1] 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
 [2] 
 http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
  
 
 
 -- 
 Francesco Chicchiriccò
 
 ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
 http://people.apache.org/~ilgrosso/
 

Re: 2.12 Release: Additions to COCOON-2333 (list of current jars)

[David Crossley]

Francesco Chicchiriccò wrote:
 David Crossley wrote:
 insigh...@gmail.com wrote:
 
 Here are some additions to COCOON-2333 (list of current jar files). I'm 
 also attaching a .txt file in case that's easier to use.
 
 Is the plan to upgrade the code to use the newer jar versions for the 
 2.12 release?
 
 Thanks, I will add some of your notes to the list.
 
 The intention was to gather some information about some of the important 
 ones. If necessary or desirable, then we could possibly upgrade some. 
 However there would need to be other Cocoon committers to assist with that.
 
 If you can point me to some procedure to test whether everything is 
 working (if it was Maven I would have known how to do this check) when 
 upgrading some JAR dependency file, I could provide some assistance.

The lib/jars.xml file explains where each jar is used, e.g. which block,
or perhaps core too. So doing ./build.sh to compile and run whatever
code tests are included, then ./cocoon.sh and exercise the relevant Sample.

 IIUC, then Cocoon-2.1 will need to remain at a limited low version of 
 Java. So that will restrict which jars can
 be upgraded, and to what version of their product.
 
 Agreed: 2.1.12 is a bugfix version - coming after years! - and its scope 
 could not interfere with Java version.

The Cocoon-2.1 README.txt says Java 1.3

However for example this is already in our C-2.1 SVN:
lib/optional/xmlgraphics-commons-1.3.1.jar
and version 1.3 is the first to require Java 1.4
http://xmlgraphics.apache.org/commons/#news-2008-06-11

-David

Re: 2.12 Release: Additions to COCOON-2333 (list of current jars)

[David Crossley]

insigh...@gmail.com wrote:

 Here are some additions to COCOON-2333 (list of current jar files). I'm 
 also attaching a .txt file in case that's easier to use.
 
 Is the plan to upgrade the code to use the newer jar versions for the 
 2.12 release?

Thanks, i will add some of your notes to the list.

The intention was to gather some information about some of the
important ones. If necessary or desirable, then we could possibly
upgrade some. However there would need to be other Cocoon
committers to assist with that.

IIUC, then Cocoon-2.1 will need to remain at a limited
low version of Java. So that will restrict which jars can
be upgraded, and to what version of their product.

-David

 Thanks,
 
 Dan

[jira] [Created] (COCOON-2333) C-2.1: upgrade some supporting product dependencies

[David Crossley (JIRA)]

David Crossley created COCOON-2333:
--

 Summary: C-2.1: upgrade some supporting product dependencies
 Key: COCOON-2333
 URL: https://issues.apache.org/jira/browse/COCOON-2333
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Affects Versions: 2.1.12-dev (Current SVN)
Reporter: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


It would be a good opportunity to upgrade some of the supporting product 
dependencies.

This ticket can note which ones are necessary or worthwhile to be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2333) C-2.1: upgrade some supporting product dependencies

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527015#comment-13527015
 ] 

David Crossley commented on COCOON-2333:


List of the set of jars and some upgrade notes in:
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt

 C-2.1: upgrade some supporting product dependencies
 ---

 Key: COCOON-2333
 URL: https://issues.apache.org/jira/browse/COCOON-2333
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Affects Versions: 2.1.12-dev (Current SVN)
Reporter: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


 It would be a good opportunity to upgrade some of the supporting product 
 dependencies.
 This ticket can note which ones are necessary or worthwhile to be updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

Francesco Chicchiriccò wrote:
 David Crossley wrote:
 
 As explained there it would also be good to upgrade some of the
 supporting products dependencies in Cocoon. Forrest has some that
 are newer than Cocoon and vice versa. We probably each have some
 that are out-of-date.
 
 It makes sense: would you like to open an issue for this?

https://issues.apache.org/jira/browse/COCOON-2333
C-2.1: upgrade some supporting product dependencies

That links to a list in SVN at:
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt

Would developers and users please add notes for any jars
that would be necessary or worthwhile to upgrade.

-David

[jira] [Reopened] (COCOON-2069) Cocoon 2.1 is not initialized when building without samples

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley reopened COCOON-2069:



Currently getting an error when starting the default cocoon samples 
application, about it not initialized.

It seems related to this patch (perhaps missing some other changes). Perhaps 
the wsrp thingy is only partially configured.

I took the easy solution, and reversed the configuration to instead be 
Uncomment if need WSRP.
See r1418605

---
Initialization Problem
Message: component: ComponentSelector could not find the component for hint 
[wsrp] (key [wsrp])
Description: org.apache.avalon.framework.configuration.ConfigurationException: 
Unable to lookup coplet adapter wsrp 
@file:/Users/.../cocoon_2_1/build/webapp/WEB-INF/cocoon.xconf:2372:31
-

 Cocoon 2.1 is not initialized when building without samples
 ---

 Key: COCOON-2069
 URL: https://issues.apache.org/jira/browse/COCOON-2069
 Project: Cocoon
  Issue Type: Bug
  Components: - Samples, Blocks: Portal
Affects Versions: 2.1.10, 2.1.11
Reporter: Jeroen Reijn
Assignee: Jeroen Reijn
 Fix For: 2.1.12-dev (Current SVN)

 Attachments: portal.samplesxconf.2069.patch, portal.xconf.2069.patch


 After building Cocoon without the samples it fails with message: Could not 
 find component key org.apache.cocoon.portal.impl.PageLabelManager.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (COCOON-2332) find the missing documentation for the Validation Block

[David Crossley (JIRA)]

David Crossley created COCOON-2332:
--

 Summary: find the missing documentation for the Validation Block
 Key: COCOON-2332
 URL: https://issues.apache.org/jira/browse/COCOON-2332
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Validation
Affects Versions: 2.2, 2.1.11
Reporter: David Crossley


The documentation for the Validation Block is missing. The samples link to docs 
on the zone server, which are now not accessible via Daisy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2332) find the missing documentation for the Validation Block

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526123#comment-13526123
 ] 

David Crossley commented on COCOON-2332:


These are the links from Samples. The URL numbers might help ;-(

Validation Block Documentation
http://cocoon.zones.apache.org/daisy/documentation/683.html

ValidatingTransformer
http://cocoon.zones.apache.org/daisy/documentation/684.html

ValidationReportTransformer
http://cocoon.zones.apache.org/daisy/documentation/691.html

Some links that do still work:

API docs:
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/validation/
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/ValidatingTransformer.html
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/ValidationReportTransformer.html

Subject: JING Transformer...
From: Pier Fumagalli
Date: 2005-08-30
http://s.apache.org/IIH

 find the missing documentation for the Validation Block
 ---

 Key: COCOON-2332
 URL: https://issues.apache.org/jira/browse/COCOON-2332
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Validation
Affects Versions: 2.1.11, 2.2
Reporter: David Crossley

 The documentation for the Validation Block is missing. The samples link to 
 docs on the zone server, which are now not accessible via Daisy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2332) find the missing documentation for the Validation Block

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526126#comment-13526126
 ] 

David Crossley commented on COCOON-2332:


Forrest documentation
http://forrest.apache.org/howto-dev.html#debug-validation
has different links which provide more Daisy numbers, e.g.
http://cocoon.zones.apache.org/daisy/documentation/components/1058/g2/684.html

 find the missing documentation for the Validation Block
 ---

 Key: COCOON-2332
 URL: https://issues.apache.org/jira/browse/COCOON-2332
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Validation
Affects Versions: 2.1.11, 2.2
Reporter: David Crossley

 The documentation for the Validation Block is missing. The samples link to 
 docs on the zone server, which are now not accessible via Daisy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2332) find the missing documentation for the Validation Block

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13526130#comment-13526130
 ] 

David Crossley commented on COCOON-2332:


It would be much better to find the actual source content.

Anyway, many thanks to the Wayback Machine. Here are some:
http://web.archive.org/web/20081011224303/http://cocoon.zones.apache.org/daisy/documentation/864/validation.html
http://web.archive.org/web/20080703172211/http://cocoon.zones.apache.org/daisy/documentation/components/1058/g2/684.html
http://web.archive.org/web/20080703172243/http://cocoon.zones.apache.org/daisy/documentation/components/1058/g2/691.html

 find the missing documentation for the Validation Block
 ---

 Key: COCOON-2332
 URL: https://issues.apache.org/jira/browse/COCOON-2332
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Validation
Affects Versions: 2.1.11, 2.2
Reporter: David Crossley

 The documentation for the Validation Block is missing. The samples link to 
 docs on the zone server, which are now not accessible via Daisy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: using both Xalan and Saxon with C3

[David Crossley]

Peter Hunsberger wrote:
 We've had to do that on Cocoon 2.x in the past when we had a mix of XSLT
 1.0 and XSLT 2.0 stylesheets.  With XSLT 3.0 coming along you may in fact
 need three xslt processors in a single application...

I remembered stuff from the old C-2.1 docs.
Do Google:
 site:cocoon.apache.org/2.1 saxon

XSLT Transformer
http://cocoon.apache.org/2.1/userdocs/xslt-transformer.html

-David

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.

https://issues.apache.org/jira/browse/FOR-1240

Hooray, it works.

As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.

-David

[jira] [Closed] (COCOON-2288) Allow usage of SLF4J for traces

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley closed COCOON-2288.
--

Resolution: Fixed

Add SLF4J to lib/jars.xml (otherwise the build intentionally fails).

Now done in r1417273

 Allow usage of SLF4J for traces
 ---

 Key: COCOON-2288
 URL: https://issues.apache.org/jira/browse/COCOON-2288
 Project: Cocoon
  Issue Type: New Feature
  Components: * Cocoon Core
Reporter: Cédric Damioli
 Fix For: 2.1.12-dev (Current SVN)

 Attachments: SLF4JLogger.java, Slf4jLoggerManager.java, 
 SLF4JLoggerManager.java


 Attached are two classes allowing to use SLF4J as logging facade inside 
 Cocoon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (COCOON-2331) Some Samples have links to associated docs which are now broken

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley closed COCOON-2331.
--

Resolution: Fixed

Done.

 Some Samples have links to associated docs which are now broken
 ---

 Key: COCOON-2331
 URL: https://issues.apache.org/jira/browse/COCOON-2331
 Project: Cocoon
  Issue Type: Task
  Components: - Documentation, - Samples
Affects Versions: 2.1.11
Reporter: David Crossley
Assignee: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


 IIRC then Samples used to link to documentation which could be viewed through 
 the Cocoon server when running the samples. Then IIRC we stopped with 
 generating the docs. So now perhaps need to link directly to the relevant 
 docs at the c.a.o/2.1/ website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (COCOON-2288) Allow usage of SLF4J for traces

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley reopened COCOON-2288:



Need to also add its license file to the legal directory as is done for other 
dependencies.

 Allow usage of SLF4J for traces
 ---

 Key: COCOON-2288
 URL: https://issues.apache.org/jira/browse/COCOON-2288
 Project: Cocoon
  Issue Type: New Feature
  Components: * Cocoon Core
Reporter: Cédric Damioli
 Fix For: 2.1.12-dev (Current SVN)

 Attachments: SLF4JLogger.java, Slf4jLoggerManager.java, 
 SLF4JLoggerManager.java


 Attached are two classes allowing to use SLF4J as logging facade inside 
 Cocoon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2330) Release separate source and dependencies packages

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507121#comment-13507121
 ] 

David Crossley commented on COCOON-2330:


Probably need to include the legal directory into the -deps package, as 
those are the licenses that accompany the jar files. Doing 'ls legal | grep -v 
\.jar' shows some others that might need investigation.

I tried building with only the -src package. The build failed before getting 
to any deps verification step or check-jars step. Perhaps because missing the 
Ant jars. The build.sh script might need to check for the libs before starting.



 Release separate source and dependencies packages
 -

 Key: COCOON-2330
 URL: https://issues.apache.org/jira/browse/COCOON-2330
 Project: Cocoon
  Issue Type: Improvement
  Components: - Build System: Ant
Affects Versions: 2.1.11
Reporter: Francesco Chicchiriccò
 Fix For: 2.1.12-dev (Current SVN)


 As recently reported by David Corssley [1] the 2.1.X release must comply with 
 ASF policies about releases, in particular providing a separate source code 
 package (without any external JAR file inside) and dependencies package (with 
 all external JAR files) for distribution.
 [1] http://markmail.org/message/f6rm2ca35eiraf7i

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (COCOON-2331) Some Samples have links to associated docs which are now broken

[David Crossley (JIRA)]

David Crossley created COCOON-2331:
--

 Summary: Some Samples have links to associated docs which are now 
broken
 Key: COCOON-2331
 URL: https://issues.apache.org/jira/browse/COCOON-2331
 Project: Cocoon
  Issue Type: Task
  Components: - Documentation, - Samples
Affects Versions: 2.1.11
Reporter: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


IIRC then Samples used to link to documentation which could be viewed through 
the Cocoon server when running the samples. Then IIRC we stopped with 
generating the docs. So now perhaps need to link directly to the relevant docs 
at the c.a.o/2.1/ website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (COCOON-2331) Some Samples have links to associated docs which are now broken

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507133#comment-13507133
 ] 

David Crossley commented on COCOON-2331:


For example, see this fix on 2006-12-15
http://svn.apache.org/viewvc?view=revisionrevision=487707

 Some Samples have links to associated docs which are now broken
 ---

 Key: COCOON-2331
 URL: https://issues.apache.org/jira/browse/COCOON-2331
 Project: Cocoon
  Issue Type: Task
  Components: - Documentation, - Samples
Affects Versions: 2.1.11
Reporter: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


 IIRC then Samples used to link to documentation which could be viewed through 
 the Cocoon server when running the samples. Then IIRC we stopped with 
 generating the docs. So now perhaps need to link directly to the relevant 
 docs at the c.a.o/2.1/ website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (COCOON-2331) Some Samples have links to associated docs which are now broken

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley reassigned COCOON-2331:
--

Assignee: David Crossley

 Some Samples have links to associated docs which are now broken
 ---

 Key: COCOON-2331
 URL: https://issues.apache.org/jira/browse/COCOON-2331
 Project: Cocoon
  Issue Type: Task
  Components: - Documentation, - Samples
Affects Versions: 2.1.11
Reporter: David Crossley
Assignee: David Crossley
 Fix For: 2.1.12-dev (Current SVN)


 IIRC then Samples used to link to documentation which could be viewed through 
 the Cocoon server when running the samples. Then IIRC we stopped with 
 generating the docs. So now perhaps need to link directly to the relevant 
 docs at the c.a.o/2.1/ website.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (COCOON-2288) Allow usage of SLF4J for traces

[David Crossley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COCOON-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Crossley reopened COCOON-2288:



Need to add the new dependency to lib/core directory. Currently getting errors 
with ./build.sh

 Allow usage of SLF4J for traces
 ---

 Key: COCOON-2288
 URL: https://issues.apache.org/jira/browse/COCOON-2288
 Project: Cocoon
  Issue Type: New Feature
  Components: * Cocoon Core
Reporter: Cédric Damioli
 Fix For: 2.1.12-dev (Current SVN)

 Attachments: SLF4JLogger.java, Slf4jLoggerManager.java, 
 SLF4JLoggerManager.java


 Attached are two classes allowing to use SLF4J as logging facade inside 
 Cocoon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

In the past releases of Cocoon-2.1, we included the relevant versions
of all supporting product dependencies. That is okay as a convenience.

However we need to provide a source code package which does not contain
those external JAR files, and conduct our release vote against that package.
Then we can construct other convenience packages for distribution.

Forrest got into the same situation. Here is some background and
links to other discussion:
http://s.apache.org/mCW
We solved the immediate situation but still need to adjust our build system.

The Cocoon-2.1 Apache Ant build system should be reasonably easy to tweak
to create separate packages.

-David

Re: [DISCUSS] Releasing 2.1.12

[David Crossley]

Cédric Damioli wrote:
 Francesco Chicchiriccò a écrit:
 Francesco Chicchiriccò wrote:
 [...]
 
   2. Is the release process clear to you? If not, who (maybe active 
 in the past) can provide some hint?
 
 Not really.
 I think there was once a page written by Carsten describing the 
 release process, but I can't find it anymore.
 
 I guess we should directly ask Carlsten, then: let's see if he 
 replies here, otherwise we can try to contact him somehow else.
 
 What about http://wiki.apache.org/cocoon/CocoonReleaseHowTo ?
 
 It seems to be what I was looking for.
 I was searching in the site and didn't remember there was a wiki !

I am still around from the olden days and will try
to help. However my time is very limited.

People on the user list should be invited to
sign up to the dev list and assist, even if
it is just to test samples and tweak docs.

-David

Re: [jira] [Commented] (COCOON-2324) Cocoon 2 - Resource not found

[David Crossley]

Thanks Javier, nicely handled.
See also https://issues.apache.org/jira/browse/FOR-1236 today.

-David

Javier Puerto (JIRA) wrote:
 
 [ 
 https://issues.apache.org/jira/browse/COCOON-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416537#comment-13416537
  ] 
 
 Javier Puerto commented on COCOON-2324:
 ---
 
 Hi Sridhar
 
 Please, use the mailing user list to ask if you have any problem first. You 
 can check the following page: 
 http://cocoon.apache.org/2.1/1175.html#Cocoon+Users
 The user list is read by more people so you can found more help, JIRA is more 
 for developers.
 
 Regarding your problem, seems like Cocoon can't found the sitemap.xmap file 
 to process your request. Could you confirm if the file 
 C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
   exists?
 
 Salu2.
 
  Cocoon 2 - Resource not found
  -
 
  Key: COCOON-2324
  URL: https://issues.apache.org/jira/browse/COCOON-2324
  Project: Cocoon
   Issue Type: Improvement
   Components: - Components: Sitemap
 Affects Versions: 2.1.11
 Reporter: Sridhar Goranti
  Fix For: 2.1.11
 
  Attachments: Cocoon2.1.11 - Resource not found.jpeg
 
 
  Hi, 
  I have deployed my cocoon 2.1.11 web application successfully in JBoss 
  5.1.0 GA application server. But when I try access the cocoon application 
  from Internet Explorer browser, I am getting below message:-
  Cocoon 2 - Resource not found
  
  type resource-not-found
  message Resource not found
  description The requested URI 
  /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
  sender org.apache.cocoon.servlet.CocoonServlet
  source Cocoon servlet
  path-info
  mount/xreporter/en-US/reportcatalog
  request-uri
  /RamsReport/mount/xreporter/en-US/reportcatalog
  JBoss 5.1.0 GA Server console log message:-
  ++
  ERROR   (2012-07-17) 14:08.43:214   [sitemap] 
  (/RamsReport/mount/xreporter/en-US/reportcatalog) 
  http-localhost%2F127.0.0.1-8080-5/DefaultTreeBuilder: Failed to load 
  sitemap from 
  file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
  org.apache.cocoon.ResourceNotFoundException: Resource not found 
  file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap:
   java.io.FileNotFoundException: 
  C:\RamsReportFinal_Workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_1_Server1342385312791\deploy\RamsReport.war\sitemap.xmap
   (The system cannot find the file specified)
  at 
  org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.java:145)
  at 
  org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(AbstractStreamSource.java:161)
  at 
  org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:206)
  at 
  org.apache.cocoon.components.source.DelayedRefreshSourceWrapper.toSAX(DelayedRefreshSourceWrapper.java:156)
  at 
  org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:387)
  at 
  org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(TreeProcessor.java:366)
  at 
  org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:330)
  at 
  org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
  at org.apache.cocoon.Cocoon.process(Cocoon.java:579)
  at 
  org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  at 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  at 
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  at 
  org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  at 
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  at 
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  at 
  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
  at 
  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
  at 
  org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  at 
  

Re: [VOTE] Javier Puerto as cocoon committer

[David Crossley]

Thorsten Scherler wrote:
 
 I propose Javier Puerto as a new Cocoon committer and PMC member.

+1

-David

an issue with Cocoon source package release vote

[David Crossley]

Please see the following thread at Apache Forrest which explains
the problem with conducting our release vote on a package that contained
not only our project sources but also contained other binary files.
That thread links to an important discussion at Apache Incubator, etc.

Subject: [Proposal] re-release 0.9 with proper source code package
http://s.apache.org/mCW

There would be a similar situation for the Cocoon-2.1.11 release vote.

-David

Re: question regarding Apache infrastructure

[David Crossley]

Robby Pelssers wrote:
 Hi all,
 
 I know in the past there was a Cocoon demo app running showing most features 
 of Cocoon.  Is it still possible to host a demo app on Apache infrastructure? 
 And if so, are there any docs out there explaining the conditions and 
 how-to's?

There is an explanation and reference to our Zone/Jail
in this recent thread:
http://thread.gmane.org/gmane.text.xml.cocoon.devel/81763
Subject: resurrect the Cocoon documentation

However remember that the notes are probably for our old Zone.

Also this Google search:
 site:apache.org/dev jail
led to some docs.

Also follow from
http://www.apache.org/dev/#pmc
to see the principles at the top of
Reporting issues and requesting project resources

-David

resurrect the Cocoon documentation

[David Crossley]

TL;DNR
Use the Apache CMS for at least our top-level docs
and the stalled 2.1 and 2.2 docs.


However, i cannot actually do this work, just explain and guide.

I have done some background research to try to gather the
various past threads and docs. Perhaps this will help us to
bring the Cocoon documentation back to life.

In the past we had the sources for the docs in xml format
and then processed by Apache Forrest to generate the html pages.

A few years ago we moved to using the Daisy CMS to store/edit
all content for 2.1 and 2.2 versions, as well as the top-level
project non-version-specific stuff.

For Cocoon-2.2, and the top-level stuff, the Maven site plugin
extracted the content from Daisy and generated the html pages. [4]

For Cocoon-2.1, the Forrest plugin Daisy input plugin extracted
the content from Daisy and generated the html pages. [5]

For Cocoon-3, the source content is stored in xml files
and the Maven site plugin generates the html pages.

All generated html was (and still is) committed to the
Cocoon site SVN [1].

Then 'svn up' on the people.apache.org machine does the
publishing step. (Later that step could move to using svnpubsub.)

The Daisy server operated on our Zones machine cocoon.zones.apache.org
(which also housed the demonstrations for Cocoon 2.1 and 2.2).
The Zones server is managed by the Cocoon project. See [2].

However, the machine that provided the zones for a set of
projects needed to be upgraded. The Cocoon project did not
move our services in time.
IIRC we do now have a freebsd jail which is basically configured,
but not yet re-installed Daisy or Cocoon demo examples,
nor the web server.
IIRC we did get a backup of the Daisy data [3] if that helps.

The Forrest forrestbot neededi to be turned off, as it could not
access the source content for the 2.1 documentation.

For the 2.2 documentation, i presume that Maven also has troubles.

So unless someone can re-instate the new cocoon.zones.apache.org
and the Daisy server, then we need some other solution.

Suggestion to use the Apache CMS:

One other solution would be to use the new Apache CMS. [7]

It can have source content in either Markdown format
or in HTML format and perhaps others.

To resurrect the content, we might be able to use the
last published generated set of html documents, strip off
the outer headers and menu stuff, replace with basic header,
and use that set of content to seed the CMS.


(Some of these resources are only available to Cocoon PMC members.)

[1] http://svn.apache.org/repos/asf/cocoon/site/site/

[2] http://svn.apache.org/repos/private/pmc/cocoon/cocoon.zones.apache.org/

[3] Search the PMC archive for various email from Bertrand

[4] http://cocoon.apache.org/1418_1_1.html
How to publish docs to cocoon.apache.org
(i.e. for Cocoon-2.2 and the top-level of c.a.o)

[5] http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
How to publish Cocoon-2.1 docs

[7] Apache CMS
http://wiki.apache.org/general/ApacheCms2010
http://wiki.apache.org/general/ApacheCMSFAQ
http://www.apache.org/dev/cmsref.html

Re: Releasing new skin version

[David Crossley]

Simone Tripodi wrote:
 Hi all,
 
 apologize for resurrecting zombie-threads but this is something really
 needed - in the last board@ report I reported that we didn't apply the
 TM requirements, I would avoid to report the same in the next
 report...

I do not know. I suggest that someone searches the archives
to find a previous update, and follow that.

-David

 On Mon, Dec 12, 2011 at 10:26 AM, Simone Tripodi
 simonetrip...@apache.org wrote:
  hi again guys,
  any hint, please? I would like to start the skin release process in a
  short while.
 
 
  On Sat, Dec 10, 2011 at 3:43 PM, Simone Tripodi
  simonetrip...@apache.org wrote:
  Hi all guys,
  I've just terminated to modify the old cocoon-thien-maven-site-skin
  according to Apache branding requirements; I took also advantage to
  update the code prettifier, moreover plugging the YUI compressor we
  now have merged/minified css/js.
 
  I would like to push a RC to call for a [VOTE], so once released the
  new skin, I'll proceed updating both sites 2.x and 3.0.
 
  My question is: can anyone remind me the procedure to release a
  Cocoon2.X component? :)

Re: [C3] Import subprojects proposal [WAS: Re: [c3] Log4j injection in target of blocks]

[David Crossley]

Francesco Chicchiriccò wrote:
 
 */site/*
 Merge this with current /cocoon3/trunk/cocoon-docs

I reckon that this site stuff should just stay where it is.

The */site/site/* is the current generated docs for the various versions
and the top-level. This is an SVN checkout on the people.apache.org
machine at /www/cocoon.apache.org/

The */site/* remainder is the old source docs for the top-level.

-David

Re: [sitemap] specification

[David Crossley]

Simone Tripodi wrote:
 do we have a sitemap specification? since I'm on vacations I have some
 time to dedicate to C3 and I would like to put the CLI in a decent
 state according to what we already discussed :)

Probably just the Cocoon-2.1 and Cocoon-2.2 java source code.

There is also this:
http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html
http://cocoon.apache.org/2.1/userdocs/matchers.html

At one stage we did try to develop a RELAX NG grammar,
but we decided to stop trying to define it with any schema.

-David

Re: Welcome Cédric Damioli and Robby Pelssers as Cocoon committers

[David Crossley]

Many thanks to both Cédric and Robby.

You can reply to private AT cocoon if preferred.

Robby already has an Individual Contributor License Agreement.

See the list of already taken committer IDs:
http://people.apache.org/committer-index.html
as a guide to specifying yours (plus an alternative).

As well as the reference [1] below, we will be following
these notes:
http://apache.org/dev/pmc.html#newcommitter

-David

Sylvain Wallez wrote:
 Hi all,
 
 I am very happy to announce that the Cocoon PMC has voted Cédric Damioli 
 and Robby Pelssers as new Cocoon committers, provided of course that 
 they accept it.
 
 Also, once you have your commit rights, you are welcome to join the 
 Cocoon PMC whose member have binding votes for releases and other 
 project matters.
 
 Please read the instructions for committers and PMC members [1], first 
 thing being to send a CLA if not already done, and suggest your 
 preferred account name.
 
 Welcome on board guys!
 
 Sylvain
 
 [1] http://apache.org/dev/#committers
 
 -- 
 Sylvain Wallez - http://bluxte.net
 

[jira] [Commented] (COCOON3-82) Allow Saxon to be used as a XSLT transformer

[David Crossley (Commented) (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON3-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13169095#comment-13169095
 ] 

David Crossley commented on COCOON3-82:
---

Yes Saxon-HE would be okay.

Subject: Re: [C3] Pipeline DSL
Date: 2010-12-14
http://s.apache.org/gx

 Allow Saxon to be used as a XSLT transformer
 

 Key: COCOON3-82
 URL: https://issues.apache.org/jira/browse/COCOON3-82
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Huib Verweij

 In order to use XSLT 2.0 features (and beyond) in a XSLT transform I need to 
 be able to use Saxon as a transformer. In C2.2 this could be done.
 There is a way of defining the transformer to be used in the system settings: 
  
 -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl. 
 This might work, I am not sure, but then the choice of XSLT processor is gone 
 - but that is perhaps not important?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Robby Pelssers as committer and PMC member

[David Crossley]

Been around Cocoon for a long time. On dev around late 2004.
He seems very helpful and respectful.
Late 2009 he asked for Daisy edit rights (and immediately sent iCLA).
Has been keen on Cocoon-2.1, even in recent past.

He was mentioned here, back in July-2008 when we considered a
batch of new ones. IIRC then some people thought that we were
adding too many at once.

-David

Re: Robby Pelssers as committer and PMC member

[David Crossley]

Hmmm, please disregard for now. That was supposed to be sent
to private@ list.

Ooops.

-David

David Crossley wrote:
 Been around Cocoon for a long time. On dev around late 2004.
 He seems very helpful and respectful.
 Late 2009 he asked for Daisy edit rights (and immediately sent iCLA).
 Has been keen on Cocoon-2.1, even in recent past.
 
 He was mentioned here, back in July-2008 when we considered a
 batch of new ones. IIRC then some people thought that we were
 adding too many at once.
 
 -David

Re: [VOTE] Require Java 1.6 for Cocoon3

[David Crossley]

Nathaniel, Alfred wrote:
 
 Please cast your votes before Mon 3 Oct 06:00 UTC.

+1

-David

Re: Using XQJ API with Cocoon3

[David Crossley]

Simone Tripodi wrote:
 Hi Robby,
 AFAIK 3rd parties MPL licensed can be included, see
 http://www.apache.org/legal/resolved.html

Yes. I investigated that once before:
http://s.apache.org/gx

Just follow the Category B instructions.

-David

Re: problem with serialization Cocoon2.2

[David Crossley]

Robby Pelssers wrote:
 
 Hi all,
 
 I have a strange situation I don't really understand.
 
 In my sitemap I have following patterns:
 
!-- 
  {1}: basictype-id
  {2}: state
  {3}: topic-id
 --
map:match pattern=basictype/*/*/*
  map:generate src=xquery/getTopic.xquery 
 type=queryStringXquery
map:parameter name=basictypeId value={1}/ 
map:parameter name=state value={2}/
map:parameter name=topicId value={3}/   
  /map:generate
  map:transform src=xslt/postprocessXqueryResults.xslt 
 type=saxon/
  map:transform src=xslt/urlTransformer.xslt type=saxon
map:parameter name=contextpath 
 value={request:contextPath}/
map:parameter name=drawingExtension 
 value={request-param:drawingExtension}/ 
  /map:transform 
  map:serialize type=p-topic/   
/map:match

map:match pattern=topic2xhtml/**
  map:generate src=cocoon:/{1}/
  map:transform src=xslt/dita/xslhtml/dita2xhtml.xsl 
 type=saxon/
  map:serialize type=xhtml/
/map:match

map:match pattern=test
  map:generate src=data/pinning_information.xml/
  map:serialize type=xml/
/map:match
 
 And configured following serializer:
 
   map:serializer name=p-topic logger=sitemap.serializer.xml  
  mime-type=text/xml;charset=utf-8 
 src=org.apache.cocoon.serialization.XMLSerializer
 encodingUTF-8/encoding
 doctype-public-//NXP//DTD P-Topic//EN/doctype-public
 doctype-system${p-topic-dtd}/doctype-system
   /map:serializer
 
 The pattern basictype/*/*/* generates a DITA topic by transforming the 
 result of an Xquery.
 
 When I invoke 
 http://localhost:/topics/basictype/PH3330L/released/pinning_information?drawingExtension=gif
  in the browser and save the result [1] to filesystem I see that the doctype 
 has been added correctly:
 
 ?xml version=1.0 encoding=ISO-8859-1?
 !DOCTYPE p-topic PUBLIC -//NXP//DTD P-Topic//EN 
 http://nww.qa.spider.nxp.com:8311/xmetal/schemas/p-topic.dtd;
 p-topic id=pinning_information
   ...
 /p-topic
 
 When I invoke 
 http://localhost:/topics/topic2xhtml/basictype/PH3330L/released/pinning_information
  I would expect the topic to get transformed correctly into XHTML.  This does 
 not work however.  Just for testing purpose I added [1] in my app into 
 /data/pinning_information.xml and created a new match pattern which reads [1] 
 from disc
 
 But when i now try to invoke http://localhost:/topics/topic2xhtml/test 
 the DITA topic does get transformed correctly.
 
 Is there a difference between 
 a)  calling a pipeline that generates a DITA topic on the fly and serializes 
 it using my custom serializer which is used as input for the 
 topic2xhtml/**  pattern
 b)  reading the DITA topic from filesystem which is used as input for the 
 topic2xhtml/**  pattern
 
 
 It looks like the class attributes which should be added by the DTD are not 
 added in use-case (a) which is why the transform fails.
 
 Any insight is appreciated.

Is the DTD being resolved and used in both cases?
http://cocoon.apache.org/2.1/userdocs/concepts/catalog.html

Are you using Cocoon's catalog entity resolver to
get a local copy of the DTD? Not that that should
make a difference.

AFAIK the Serializer adds the document type declaration.
It is the next Generator that would resolve and process
the DTD.

At Apache Forrest we have a similar situation. There
are intermediate pipelines that serialise to xml
and add a document type declaration.

When i look at our logs, there are messages about
resolving the DTD for the initial xml source that
is Generated. However there are no DTD resolve messages
for that intermediate pipeline.

I think that this might just be confirming your situation.

-David

Re: Does ValidatingTransformer support DTD validation

[David Crossley]

David Crossley wrote:
 Robby Pelssers wrote:
  
  i am trying to use the validating transformer with a DTD but can't get it 
  to work.
 
 IIRC when i set this up for Apache Forrest a while back,
 then i could not get DTD validation working either.
 So we converted the DTD to RELAX NG using Trang.
 
 Some of the notes and links here might help:
 http://forrest.apache.org/howto-dev.html#debug-validation
 https://issues.apache.org/jira/browse/FOR-1172
 
 (I have been trying to investigate this for ages.
 Sorry, not much time, so i hope this much helps.)
 
 No matter what i do to configure the transformer, there are only
 three default grammar for SchemaParser instantiated
 (DEBUG messages in core.log). Two for RELAX NG and one for
 XML Schema, and none for DTD.
 
 Been twiddling sitemap.xmap (and forrest.xmap) and cocoon.xconf files.
 
 Trying to specify a grammar for the particular use in the
 sitemap match, then requesting the validation report gives
 Unsupported grammar language.
 
 Not specifying a grammar, then requesting the validation report gives
 The markup in the document preceding the root element must be well-formed
 
 The logs show that the DTD has been resolved by the
 catalog entity resolver.
 
 There is a message for Detecting grammar for the DTD,
 but no resolution message for detected for schema like
 there is for RNG validation.
 
 Then we get the error message for markup as above,
 a SAXParseException.
 This line of the DTD is the first !ENTITY ... declaration.
 So it is not parsing it as a DTD.
 
 Note that Forrest still uses Cocoon-2.1 but IIRC then this Validation
 block is the same.
 
 Need to look at the Cocoon Samples. Perhaps there is a reason
 that Pier did provide a DTD sample in the beginning.

Typo: did *not* provide a DTD sample

 Another thought: I wonder if this is because our xml-parser
 is configured in cocoon.xconf to have validate=false.
 
 -David
 
  I already took a look at the source and found this block of code in 
  http://svn.apache.org/repos/asf/cocoon/trunk/blocks/cocoon-validation/cocoon-validation-impl/src/main/java/org/apache/cocoon/components/validation/jaxp/JaxpSchemaParser.java
  
  I tried 
  
   map:transform src=data/p-topic.dtd type=validate
 map:parameter name=grammar 
  value=http://www.w3.org/TR/REC-xml/
   /map:transform  
  which does not work.
  
  -
  /* Detect languages or use the supplied ones */
  Configuration languages[] = 
  conf.getChild(grammars).getChildren(grammar);
  Set grammars = new HashSet();
  if (languages.length  0) {
  
  /* If the configuration specified (formally) a list of grammars 
  use it */
  for (int x = 0; x  languages.length; x++) {
  String language = languages[x].getValue();
  if (fact.isSchemaLanguageSupported(language)) {
  grammars.add(language);
  continue;
  }
  /* If the configured language is not supported throw an 
  exception */
  String message = JAXP SchemaFactory \ + this.className + 
  \  +
   does not support configured grammar  + 
  language;
  throw new ConfigurationException(message, languages[x]);
  }
  } else {
  
  /* Attempt to detect the languages directly using the JAXP 
  factory */
  if 
  (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_SCHEMA)) {
  grammars.add(Validator.GRAMMAR_XML_SCHEMA);
  }
  if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_RELAX_NG)) 
  {
  grammars.add(Validator.GRAMMAR_RELAX_NG);
  }
  if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_DTD)) {
  grammars.add(Validator.GRAMMAR_XML_DTD);  //this equals 
  http://www.w3.org/TR/REC-xml;
  }
  }
  
  
  Is there a way to configure support for DTD validation as well?  XML schema 
  validation seems to work out-of-the-box.
  
  Kind regards,
  Robby
 

Re: Does ValidatingTransformer support DTD validation

[David Crossley]

Robby Pelssers wrote:
 Hi David,
 
 One thing I still need to investigate was Jeroen's reply:
 
 Hi Robby,
 
 have you checked this page [1]? I'm not sure if this is the same
 component, but is might lead you further.
 
 [1] http://wiki.apache.org/cocoon/ValidationTransformer
 
 Jeroen
 
 
 I checked that (probably somewhat deprecated) documentation but i noticed 
 something that could be usefull:
 
 map:transform type='validate' 
 src='validation/xhtml1-transitional.dtd'
   map:parameter name='active' value='true'/ !-- this part --
 /map:transform
 
 If i find some time this week I will check if setting that 'active' parameter 
 to true does any good unless you beat me to it ;-)

This is a different component to the Transformer that is in Cocoon SVN.

-David

Re: Does ValidatingTransformer support DTD validation

[David Crossley]

Robby Pelssers wrote:
 
 i am trying to use the validating transformer with a DTD but can't get it to 
 work.

IIRC when i set this up for Apache Forrest a while back,
then i could not get DTD validation working either.
So we converted the DTD to RELAX NG using Trang.

Some of the notes and links here might help:
http://forrest.apache.org/howto-dev.html#debug-validation
https://issues.apache.org/jira/browse/FOR-1172

(I have been trying to investigate this for ages.
Sorry, not much time, so i hope this much helps.)

No matter what i do to configure the transformer, there are only
three default grammar for SchemaParser instantiated
(DEBUG messages in core.log). Two for RELAX NG and one for
XML Schema, and none for DTD.

Been twiddling sitemap.xmap (and forrest.xmap) and cocoon.xconf files.

Trying to specify a grammar for the particular use in the
sitemap match, then requesting the validation report gives
Unsupported grammar language.

Not specifying a grammar, then requesting the validation report gives
The markup in the document preceding the root element must be well-formed

The logs show that the DTD has been resolved by the
catalog entity resolver.

There is a message for Detecting grammar for the DTD,
but no resolution message for detected for schema like
there is for RNG validation.

Then we get the error message for markup as above,
a SAXParseException.
This line of the DTD is the first !ENTITY ... declaration.
So it is not parsing it as a DTD.

Note that Forrest still uses Cocoon-2.1 but IIRC then this Validation
block is the same.

Need to look at the Cocoon Samples. Perhaps there is a reason
that Pier did provide a DTD sample in the beginning.

Another thought: I wonder if this is because our xml-parser
is configured in cocoon.xconf to have validate=false.

-David

 I already took a look at the source and found this block of code in 
 http://svn.apache.org/repos/asf/cocoon/trunk/blocks/cocoon-validation/cocoon-validation-impl/src/main/java/org/apache/cocoon/components/validation/jaxp/JaxpSchemaParser.java
 
 I tried 
 
  map:transform src=data/p-topic.dtd type=validate
map:parameter name=grammar 
 value=http://www.w3.org/TR/REC-xml/
  /map:transform  
 which does not work.
 
 -
 /* Detect languages or use the supplied ones */
 Configuration languages[] = 
 conf.getChild(grammars).getChildren(grammar);
 Set grammars = new HashSet();
 if (languages.length  0) {
 
 /* If the configuration specified (formally) a list of grammars 
 use it */
 for (int x = 0; x  languages.length; x++) {
 String language = languages[x].getValue();
 if (fact.isSchemaLanguageSupported(language)) {
 grammars.add(language);
 continue;
 }
 /* If the configured language is not supported throw an 
 exception */
 String message = JAXP SchemaFactory \ + this.className + 
 \  +
  does not support configured grammar  + 
 language;
 throw new ConfigurationException(message, languages[x]);
 }
 } else {
 
 /* Attempt to detect the languages directly using the JAXP 
 factory */
 if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_SCHEMA)) 
 {
 grammars.add(Validator.GRAMMAR_XML_SCHEMA);
 }
 if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_RELAX_NG)) {
 grammars.add(Validator.GRAMMAR_RELAX_NG);
 }
 if (fact.isSchemaLanguageSupported(Validator.GRAMMAR_XML_DTD)) {
 grammars.add(Validator.GRAMMAR_XML_DTD);  //this equals 
 http://www.w3.org/TR/REC-xml;
 }
 }
 
 
 Is there a way to configure support for DTD validation as well?  XML schema 
 validation seems to work out-of-the-box.
 
 Kind regards,
 Robby

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

David Crossley wrote:
 Simone Tripodi wrote:
  Hi David!!!
  thanks a lot for your review, I'll work on the problems you notified
  before declaring the vote passed!
 
 Well it does not need to be done at this stage if
 it receives sufficient votes.
 
 In my opinion these issue can wait until the next
 release cycle.

And if we tweak stuff, then need new packages, new md5, new vote.

It is up to the Release Manager (in this case you).

Even if there were sufficient positive votes, and an
issue came up, then the RM can decide to prepare a new
release candidate and re-start the vote.

It is useful to look at the release documentation
of various projects.

-David

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

Simone Tripodi wrote:
 Hi again,
 just to make sure everybody tests the same stuff, please refer to:
 
 http://people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/3.0.0-alpha-3/cocoon-all-3.0.0-alpha-3-dist.tar.gz*
 http://people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/3.0.0-alpha-3/cocoon-all-3.0.0-alpha-3-dist.zip*
 
 Include GPG key and checksum verification!!!

Thanks Simone.

+1 from me.

MD5 (cocoon-all-3.0.0-alpha-3-dist.tar.gz) = 5b2e839101ec53246690b05dbf136b13

There are a couple of things that should get fixed
for next time:

The md5 and sha1 files have extra -n.

All NOTICE.txt files have a year range, so needs 2011.


I don't understand how Maven stuff works. There are some
declared dependencies. They do use suitable licenses.
Do we need to add a copy of their licenses in our distribution?

e.g. some are:
AspectJ : EPL-1.0
Woodstox : Apache License 2.0
Antlr : BSD
MurmurHash : Apache License 2.0

Some of those licenses do require reciprocity:
http://www.apache.org/legal/resolved.html#category-b
e.g.
We already have mentioned in NOTICE.txt the JAXB using CDDL.

However we have not mentioned AspectJ using EPL.

We do mention Java MurmurHash using AL-20 and the original
using MIT, but we do not need to.

-David

Re: Patch list reminders

[David Crossley]

Simone Tripodi wrote:

 can you give more hints how to do it? It was indeed a nice service, if
 I have enough karma I can take care of it.
 Just let me know, many thanks in advance!

The discussion referred to below is at
https://mail-search.apache.org/
On the cocoon-private list (so only PMC members).
Subject: Jira users associated with project mailing lists
Date: 16 Feb 2011 to 20 Feb 2011

There was also related discussion on the Infra mail lists
around that date, and on a previous occasion (we think April 2010).

Sorry, i do not know how other projects have re-instated
those notifications, or even if they have done so.

-David

 David Crossley wrote:
  Andy Stevens wrote:
 
  Is it just me, or have there been no Subscription:
  COCOON-open-with-patch emails from JIRA since the middle of February?
   Has something gone wrong with the link?
 
  That is correct. The technique used to send that report
  was closed down due to other security concerns.
 
  There is email to Cocoon private@ around that time.
  Some Cocoon PMC person needs to reconfigure our JIRA.
 
  Thanks for your interest.
 
  -David
 

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

Simone Tripodi wrote:
 Hi David!!!
 thanks a lot for your review, I'll work on the problems you notified
 before declaring the vote passed!

Well it does not need to be done at this stage if
it receives sufficient votes.

In my opinion these issue can wait until the next
release cycle.

-David

 David Crossley wrote:
  Simone Tripodi wrote:
  Hi again,
  just to make sure everybody tests the same stuff, please refer to:
 
  http://people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/3.0.0-alpha-3/cocoon-all-3.0.0-alpha-3-dist.tar.gz*
  http://people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/3.0.0-alpha-3/cocoon-all-3.0.0-alpha-3-dist.zip*
 
  Include GPG key and checksum verification!!!
 
  Thanks Simone.
 
  +1 from me.
 
  MD5 (cocoon-all-3.0.0-alpha-3-dist.tar.gz) = 
  5b2e839101ec53246690b05dbf136b13
 
  There are a couple of things that should get fixed
  for next time:
 
  The md5 and sha1 files have extra -n.
 
  All NOTICE.txt files have a year range, so needs 2011.
 
 
  I don't understand how Maven stuff works. There are some
  declared dependencies. They do use suitable licenses.
  Do we need to add a copy of their licenses in our distribution?
 
  e.g. some are:
  AspectJ : EPL-1.0
  Woodstox : Apache License 2.0
  Antlr : BSD
  MurmurHash : Apache License 2.0
 
  Some of those licenses do require reciprocity:
  http://www.apache.org/legal/resolved.html#category-b
  e.g.
  We already have mentioned in NOTICE.txt the JAXB using CDDL.
 
  However we have not mentioned AspectJ using EPL.
 
  We do mention Java MurmurHash using AL-20 and the original
  using MIT, but we do not need to.
 
  -David
 
 

Re: Patch list reminders

[David Crossley]

Andy Stevens wrote:
 
 Is it just me, or have there been no Subscription:
 COCOON-open-with-patch emails from JIRA since the middle of February?
  Has something gone wrong with the link?

That is correct. The technique used to send that report
was closed down due to other security concerns.

There is email to Cocoon private@ around that time.
Some Cocoon PMC person needs to reconfigure our JIRA.

Thanks for your interest.

-David

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

Reinhard Pötz wrote:
 Simone Tripodi wrote:
 
 a) where I can find the KEYS file on svn? I'm pretty sure I updated it
 once, but can't remember if it was the cocoon or commons one that I'm
 referring... thanks in advance! :P
 
 I think you have to update it directly in our release directory on 
 people.apache.org.
 
 David, is this correct?

Yes. I just now did ssh people.apache.org
and looked in /www/www.apache.org/dist/cocoon
The 'svn info' shows that most peripheral files
are managed in SVN at
https://svn.apache.org/repos/asf/cocoon/site/mirrors/
but KEYS is not.

FWIW, at Forrest we do. I also checked and the httpd
project does too.

-David

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

Francesco Chicchiriccò wrote:
 Simone Tripodi wrote:
 Hi all guys,
 I'm here to propose the release of Apache Cocoon 3.0.0-alpha-3.
 
 [...]
 Vote will be open for next 72 hours and will be closed on June 12th at
 5:00pm CET.
 So please cast your votes
 
 [ ] +1, let's release Apache Cocoon 3.0.0-alpha-3
 [ ] +/- 0
 [ ] -1, because (explain the reason why)
 
 +1

Thanks Francesco, but we need to wait for the source packages
and vote regarding those.

 Many thanks in advance, all the best!!!
 
 Thanks you for taking care of this task :-)

Yes, definitely, for someone to make the effort to
manage a release is important.

-David

 -- 
 Francesco Chicchiriccò
 
 Apache Cocoon Committer and PMC Member
 http://people.apache.org/~ilgrosso/
 

Re: PS. Re: Cocoon 2.2, STX block, TraxTransformer, transformer-factory

[David Crossley]

Huib Verwey wrote:
 Magic stuff really does not happen. Of course it wasn't the silly attribute 
 that did the trick, it was adding a dependency on the Joost jar that did the 
 trick. Of course, once you know it's obvious ;-).

Thanks Huib, glad that you worked it out and reported back.

Is there something that needs to be modified
in the Cocoon-2.2 SVN?

-David

Re: [VOTE] Release Apache Cocoon 3.0.0-alpha-3

[David Crossley]

Reinhard Pötz wrote:
 Thanks for your great efforts! There are two things that need to be done 
 before I can vote with +1
 
 a) Please add you PGP key to http://www.apache.org/dist/cocoon/KEYS
 
 b) We also need a non-Maven (yes, there are still people that don't use 
 the central Maven repo) distribution.

Thanks Simone. Please be aware that the release is the
source code package and that is what we need to vote on.
http://www.apache.org/dev/release.html#what
http://www.apache.org/dev/#releases

-David

Re: Welcome Francesco Chicchiriccò as new Cocoon Committer

[David Crossley]

Thanks Francesco, and welcome.

-David

Re: How-to disable caching for Cocoon2.2 completely

[David Crossley]

Joerg Heinicke wrote:

 You can switch off caching per pipeline. There is a non-caching 
 pipeline. Please don't ask me for details though - too long ago :-)

These Cocoon 2.1 docs are probably still relevant:
http://cocoon.apache.org/2.1/userdocs/concepts/caching.html

And try search:
 site:cocoon.apache.org/2.2 caching
 site:wiki.apache.org/cocoon/ caching

-David

 Joerg
 
 On 17.02.2011 14:42, Robby Pelssers wrote:
 I would like to check out the performance without any caching and check if 
 I can live with it... if so it will at least solve my corrupted cache 
 issue.
 

Re: About copyright and translation

[David Crossley]

David Crossley wrote:
 David Crossley wrote:
  Grégory Roche wrote:
The documentation is on the site 
   http://www.polymorphisme.com/serveurs/cocoon 
   
   and in some days I add the licence Apache 2. 
  
  As said, you need to clearly say that it is Apache Cocoon.
  I do not see any indication of that.
 
 This will explain and assist you:
 Apache Trademark Policy
 http://apache.org/foundation/marks/

You still need to follow up on this.
The first mention needs to be the term Apache Cocoon.
Other following occasions can then use the single word Cocoon.
See the abovementioned URL.

I suggest that the navigation panel on the left-hand side
be changed to say Apache Cocoon. The Introduction page
should also clearly refer to Apache Cocoon.

-David

Re: About copyright and translation

[David Crossley]

Grégory Roche wrote:
  The documentation is on the site 
 http://www.polymorphisme.com/serveurs/cocoon 
 
 and in some days I add the licence Apache 2. 

As said, you need to clearly say that it is Apache Cocoon.
I do not see any indication of that.

-David

 Thank you.
 
 Grégory Roche 
 
 polymorphisme.com
 webmas...@polymorphisme.org
 fixe : 05.24.07.64.02
 port : 06.89.54.14.84David Crossley cross...@apache.org a écrit :
 
  Grégory Roche wrote:
 
  two weeks ago, I translated a part of the Cocoon's documentation in French.
 
  So, I'm looking for the Licence, the Copyright about this documentation.
 
  Everything is licensed Apache License, Version 2.0 unless
  otherwise noted.
  http://www.apache.org/licenses/
 
  Can I put this translation on my site Web ? Are you interesting by 
  the translation ?
   Sorry, for my bad english. Thank you.
 
  I am not expert, but i think that you are okay to do that
  as long as it is clearly marked and refer to Apache Cocoon.
 
  -David
 
  Grégory Roche
 
  polymorphisme.com
  webmas...@polymorphisme.org
  fixe : 05.24.07.64.02
  port : 06.89.54.14.84
 

Re: About copyright and translation

[David Crossley]

David Crossley wrote:
 Grégory Roche wrote:
   The documentation is on the site 
  http://www.polymorphisme.com/serveurs/cocoon 
  
  and in some days I add the licence Apache 2. 
 
 As said, you need to clearly say that it is Apache Cocoon.
 I do not see any indication of that.

This will explain and assist you:
Apache Trademark Policy
http://apache.org/foundation/marks/

-David

   Grégory Roche wrote:
  
   two weeks ago, I translated a part of the Cocoon's documentation in 
   French.
  
   So, I'm looking for the Licence, the Copyright about this documentation.
  
   Everything is licensed Apache License, Version 2.0 unless
   otherwise noted.
   http://www.apache.org/licenses/
  
   Can I put this translation on my site Web ? Are you interesting by 
   the translation ?
Sorry, for my bad english. Thank you.
  
   I am not expert, but i think that you are okay to do that
   as long as it is clearly marked and refer to Apache Cocoon.

Re: About copyright and translation

[David Crossley]

Grégory Roche wrote:
 
 two weeks ago, I translated a part of the Cocoon's documentation in French. 
 
 So, I'm looking for the Licence, the Copyright about this documentation. 

Everything is licensed Apache License, Version 2.0 unless
otherwise noted.
http://www.apache.org/licenses/

 Can I put this translation on my site Web ? Are you interesting by the 
 translation ?
  Sorry, for my bad english. Thank you.

I am not expert, but i think that you are okay to do that
as long as it is clearly marked and refer to Apache Cocoon.

-David

 Grégory Roche 
 
 polymorphisme.com
 webmas...@polymorphisme.org
 fixe : 05.24.07.64.02
 port : 06.89.54.14.84

Re: [vote] Release Cocoon JNet 1.2.0, Cocoon Maven Plugin 1.0.0 Cocoon Maven Site Skin 1.0.0

[David Crossley]

Reinhard Pötz wrote:
 David Crossley wrote:
 
 -1 for Cocoon Maven Site Skin 1.0.0
 MD5(cocoon-thien-maven-site-skin-1.0.0-sources.jar)= 
 e397a0c3eecf42bd7a2b1d1feeb1a24b
 Due to the missing CLA. Otherwise okay.
 
 Ouch, sorry for not looking into this vote thread until now.
 
 Thanks for voting. Concerning Thien's CLA I will answer on private@ 
 because it contains personal information about Thien and I'm not sure if 
 he wants to see it being published on a public mailing list.

Ah, registered under a different name. Thanks for the clarification.

So i vote +1 for Cocoon Maven Site Skin 1.0.0

-David

Re: [vote] Release Cocoon JNet 1.2.0, Cocoon Maven Plugin 1.0.0 Cocoon Maven Site Skin 1.0.0

[David Crossley]

Reinhard Pötz wrote:
 
 I created release artifacts for following modules:
 
 * Cocoon JNet 1.2.0
   SVN:
http://s.apache.org/cocoon-jnet-1.2.0
   Maven artifacts:
http://s.apache.org/cocoon-jnet-1.2.0-maven
   Distribution files:
http://people.apache.org/~reinhard/cocoon-staging/cocoon-jnet/
   Changes:
http://s.apache.org/cocoon-jnet-1.2.0-changes

+1 for Cocoon JNet 1.2.0

MD5(cocoon-jnet-1.2.0.tar.gz)= a58a8f8727c4603377f15d7e1a3847b5

 * Cocoon Maven Plugin 1.0.0
   SVN:
http://s.apache.org/cocoon-maven-plugin-1.0.0
http://s.apache.org/cocoon-rcl-spring-reloader-1.0.0
http://s.apache.org/cocoon-rcl-webapp-wrapper-1.0.0
   Maven artifacts:
http://s.apache.org/cocoon-maven-plugin-1.0.0-maven
http://s.apache.org/cocoon-rcl-spring-reloader-1.0.0-maven
http://s.apache.org/cocoon-rcl-webapp-wrapper-1.0.0-maven
   Distribution files:
a Maven release only (doesn't make sense to use it ouside the
scope of Maven)
   Changes:
Support Spring 3.0

+1 for Cocoon Maven Plugin 1.0.0

MD5(cocoon-maven-plugin-1.0.0-sources.jar)= 9564e956381e7c47b025ffe5a4270bfc
MD5(cocoon-rcl-spring-reloader-1.0.0-sources.jar)= 
534cc5d27e2cba208146d848e70b1f56
MD5(cocoon-rcl-webapp-wrapper-1.0.0-sources.jar)= 
5c086d4b8918b213d3aee909f5fc93f4

 * Cocoon Maven Site Skin 1.0.0
   SVN:
http://s.apache.org/cocoon-thien-maven-site-skin-1.0.0
   Maven artifacts:
http://s.apache.org/cocoon-thien-maven-site-skin-1.0.0-maven
   Distribution files:
a Maven release only (doesn't make sense to use it ouside the
scope of Maven)
   Changes:
initial release

I cannot see the iCLA recorded for Thien.
You did ask for it in this thread and it looked
like follow-through, but i cannot find it in
the iclas.txt file.

http://s.apache.org/bYK
Date: Tue, 23 Jan 2007 
Subject: Re: Artwork for cocoon.apache.org - next steps

-1 for Cocoon Maven Site Skin 1.0.0
MD5(cocoon-thien-maven-site-skin-1.0.0-sources.jar)= 
e397a0c3eecf42bd7a2b1d1feeb1a24b
Due to the missing CLA. Otherwise okay.

Ouch, sorry for not looking into this vote thread until now.

-David

Re: Going emeritus

[David Crossley]

Grzegorz Kossakowski wrote:
 
 Thanks for a great time and I hope to meet you again in a future.

It was good. Thanks for all that you did for Cocoon.

All the best.

-David

Re: [C3] Pipeline DSL

[David Crossley]

Simone Tripodi wrote:
 Hi Robby,
 nope we're not using Saxon and we can't since, AFAIK, there are legal
 issue due to different licenses, but I don't know more details. For
 the same reason Saxon is not present in any of public Maven central
 repo.
 HTH,
 Simo

It seems that Saxon-HE would be okay.
http://www.saxonica.com/documentation/conditions/intro.xml
http://apache.org/legal/resolved.html#category-b

-David

 Robby Pelssers wrote:
 
  Just reading through lamdaj. They use proxies... interesting...
 
  Anyway, I'm having some strange bugs in a big C2.2 application I built and 
  what worries me is I can't reproduce them locally ;-(
  Flowscript is nice but it becomes dangerous when you start building 
  reusable flowscript components which you might even share between cocoon 
  blocks.  Refactoring has to be done with great care since Eclipse will not 
  blink an eye.
 
  PS.
  One question. Are you using saxon8.7 with cocoon3?
 
  Kind regards,
  Robby

Re: ehcache blows up catalina.out

[David Crossley]

I recall struggling with this at Apache Forrest in the past.
However, sorry cannot remember how.

Search the mail archives should help.

At Forrest, we now have a default configuration file at
 WEB-INF/ehcache.xml
Maybe that will help you to control it.
However, IIRC then we had fixed our ehcache debug log
messages before adding that.

Also, you would probably get a better response from
the Cocoon users mail list.

-David

Gump for Cocoon3

[David Crossley]

At Apache Gump, Stefan has recently added a Gump build of Cocoon3.

See http://thread.gmane.org/gmane.comp.jakarta.gump/14458/focus=14475

Here is the first output:
http://vmgump.apache.org/gump/public/cocoon3/

If not familiar with Gump, then follow:
All Projects : cocoon3
then
Project-level Work : build_cocoon3_cocoon3
then
Output : Complete Output File

Could someone here at Cocoon assist with the build errors.

Not sure if Gump runs more than once per day,
but that last run finished at 19:20 US PDT.

When it settles, we could enable Gump to nag us.

-David

Cocoon/Daisy/Forrest zone problem (Was: ForrestBot build for cocoon-docs FAILED)

[David Crossley]

I have switched the cron job off on the Forrest zone.

This is unfortunate because no Cocoon-2.1 docs will be built.

-David

David Crossley wrote:
 David Crossley wrote:
  Robby Pelssers wrote:
   Glad you asked…. I would also get rid of this daily spam ;-)
  
   From: Jasha Joachimsthal
   
Does anyone know what's going wrong (and more important, how to fix 
this)?
  
  See my reply on 23 March when this issue first started.
  Copied below for convenience.
 
 Actually, looking further back, it first started on 13 March
 then was okay for a while, then started again.
 
 Note that it does not happen on every run.
 The job runs twice per day.
 
 Note that is happens on different documents each time.
 
 Also the Forrest project's own docs production does not have this
 issue. That is why i say that it seems like a Cocoon zone server
 network or Daisy problem.
 
 That is all i know. Other people who are more familiar
 with the Cocoon zone and Daisy will need to take over.
 
  Someone needs to investigate what is happening on the
  Cocoon zone.
  
 Automated build for cocoon-docs FAILED
...
  [java] * [214/145] [0/298]   2.256s 54.0Kb  
 2.1/userdocs/pdf-serializer.html
  [java] X [0] 2.1/856.html
 BROKEN: Stream closed.

These failures with the Cocoon-2.1 docs seem to be sporadic.

It seems to be an intermittent problem with the zone server
or maybe with Daisy.
 

Re: ForrestBot build for cocoon-docs FAILED

[David Crossley]

Torsten Curdt wrote:
 If no one is fixing this - could we at least shut down the bot?

Hah, i had just done it a few minutes ago.

Could any further discussion please go back to the other
recent thread which has the background info.

-David

Re: ForrestBot build for cocoon-docs FAILED

[David Crossley]

Jeroen Reijn wrote:
 Do any of you have an account for the daisy instance or zone? I 
 personally don't, but apparently we need somebody to fix this.

Perhaps ask on the cocoon private mail list. I cannot remember
who is root at our zone and can add users.

There is some info in
https://svn.apache.org/repos/private/pmc/cocoon/cocoon.zones.apache.org/

-David

Re: ForrestBot build for cocoon-docs FAILED

[David Crossley]

Robby Pelssers wrote:
 Glad you asked…. I would also get rid of this daily spam ;-)

 From: Jasha Joachimsthal
 
  Does anyone know what's going wrong (and more important, how to fix this)?

See my reply on 23 March when this issue first started.
Copied below for convenience.

Someone needs to investigate what is happening on the
Cocoon zone.

   Automated build for cocoon-docs FAILED
  ...
[java] * [214/145] [0/298]   2.256s 54.0Kb  
   2.1/userdocs/pdf-serializer.html
[java] X [0] 2.1/856.html
   BROKEN: Stream closed.
  
  These failures with the Cocoon-2.1 docs seem to be sporadic.
  
  It seems to be an intermittent problem with the zone server
  or maybe with Daisy.

Re: ForrestBot build for cocoon-docs FAILED

[David Crossley]

David Crossley wrote:
 Robby Pelssers wrote:
  Glad you asked…. I would also get rid of this daily spam ;-)
 
  From: Jasha Joachimsthal
  
   Does anyone know what's going wrong (and more important, how to fix this)?
 
 See my reply on 23 March when this issue first started.
 Copied below for convenience.

Actually, looking further back, it first started on 13 March
then was okay for a while, then started again.

Note that it does not happen on every run.
The job runs twice per day.

Note that is happens on different documents each time.

Also the Forrest project's own docs production does not have this
issue. That is why i say that it seems like a Cocoon zone server
network or Daisy problem.

That is all i know. Other people who are more familiar
with the Cocoon zone and Daisy will need to take over.

 Someone needs to investigate what is happening on the
 Cocoon zone.
 
Automated build for cocoon-docs FAILED
   ...
 [java] * [214/145] [0/298]   2.256s 54.0Kb  
2.1/userdocs/pdf-serializer.html
 [java] X [0] 2.1/856.html
BROKEN: Stream closed.
   
   These failures with the Cocoon-2.1 docs seem to be sporadic.
   
   It seems to be an intermittent problem with the zone server
   or maybe with Daisy.

[jira] Commented: (COCOON-2289) [2.1] Backport FOPNGSerializer

[David Crossley (JIRA)]

[ 
https://issues.apache.org/jira/browse/COCOON-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12855253#action_12855253
 ] 

David Crossley commented on COCOON-2289:


At Apache Forrest we would be pleased to see this happen.

We have our own modified Cocoon 2.1 block for enabling this. Here are some 
clues that might help ...

Two snippets from our PDF Plugin's changes file ...
-
Updating the fop-library to fop 0.94 and
upgrading the stylesheets to work properly with the new and more
precise fo-interpeter.

Replaced Cocoon FOP Block with special Forrest edition
cocoon-fop-ng-impl-special compiled by jeremias.
The sources are in the jar. See r603892 and the thread
  
http://mail-archives.apache.org/mod_mbox/forrest-dev/200712.mbox/%3c476aa40c.8050...@apache.org%3e
  Re: Plans for integrating FOP .94
-

Subsequent update to fop-0.95

The jar and sources are now at:
https://svn.apache.org/repos/asf/forrest/trunk/plugins/org.apache.forrest.plugin.output.pdf/lib/


 [2.1] Backport FOPNGSerializer
 --

 Key: COCOON-2289
 URL: https://issues.apache.org/jira/browse/COCOON-2289
 Project: Cocoon
  Issue Type: Improvement
  Components: Blocks: FOP
Reporter: Cédric Damioli
 Fix For: 2.1.12-dev (Current SVN)


 Cocoon 2.1 still don't have official support for  FOP 0.9x, while Cocoon 2.2 
 does
 This compatibility is only a matter of FOPSerializer (called FOPNGSerializer 
 in the Cocoon 2.2 fop-ng block)
 I won't put a patch here because it would only be a copy of the 
 FOPNGSerializer.java from Cocoon-2.2, but it would be great if someone could 
 backport the fop-ng block

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [2.1] Is Cocoon 2.1.x officially dead ?

[David Crossley]

Bertrand Delacretaz wrote:
 Cédric Damioli wrote:
 
  ...I'm wondering if someone around here was still willing to maintain the
  Cocoon-2.1 branch ?
  If not, I volunteer to do the job, as this branch is important for us, and I
  don't want to have to fork it in our own repository
 
 I'm +1 on someone maintaining the 2.1 branch and cutting releases as needed.
 
 I don't use Cocoon anymore, but some of the projects that I created
 with 2.1.x a few years ago are still running very well and maintained,
 though more at the application level where they probably don't need
 changes to Cocoon itself.
 
 I think 2.1.x is stable enough for people who use it to stay on that
 version, so maintaining it makes at lot of sense.
 
 Are there any current committers willing to help maintain it?

Yes, i will play a part. I can certainly help with the release
process.

I have tried on various occasions to apply some of the
outstanding patches, but had difficulty.

It would need the help of others.

 If not we might need to elect some new ones based on who's currently
 contributing in this area.

That should be happening anyway.

-David

Re: ForrestBot build for cocoon-docs FAILED

[David Crossley]

 Automated build for cocoon-docs FAILED
...
  [java] * [214/145] [0/298]   2.256s 54.0Kb  
 2.1/userdocs/pdf-serializer.html
  [java] X [0] 2.1/856.htmlBROKEN: 
 Stream closed.

These failures with the Cocoon-2.1 docs seem to be sporadic.

It seems to be an intermittent problem with the zone server
or maybe with Daisy.

-David