Re: Code freeze - over

Reinhard Poetz pisze: All release artifacts and their docs have been created. This means that the code freeze is over and our SVN is happily awaiting your commits again! Currently trunk doesn't build because the parent pom references are not set correctly. I will take care for this

Re: ObjectModel exception

Leszek Gawron pisze: Grzegorz Kossakowski wrote: Leszek Gawron pisze: Because comparison is made by low-level class like ArrayList that is unaware of wrapping objects. Do you want to say that NativeObjects should be unwrapped always whenever they are used in Java code? Seems natural to

Re: Renewing Apache Fop processor

On 9/28/07, Robby Pelssers [EMAIL PROTECTED] wrote: ... I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version?... I think that's what http://issues.apache.org/jira/browse/COCOON-1795 does - some assembly required

Re: Renewing Apache Fop processor

Bertrand Delacretaz wrote: On 9/28/07, Robby Pelssers [EMAIL PROTECTED] wrote: ... I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version?... I think that's what http://issues.apache.org/jira/browse/COCOON-1795

Re: Renewing Apache Fop processor

On 28.09.2007 5:05 Uhr, Robby Pelssers wrote: I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version? So far it should still be pretty straight-forward to use a 2.2 block in 2.1 as long as it has not been

Re: Java 1.5

Reinhard Poetz wrote: I think for 2.2 it is fine to stick with Java 1.4 and go for Java 5 with 2.3. This should also give the Websphere 6 users enough time and is for all the Java 5 fans motivation to make 2.3 happen soon ;-) Exactly. Vadim

Re: Branching cocoon-forms

Giacomo Pati wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reinhard Poetz wrote: Grzegorz Kossakowski wrote: Hmmm, does such structure and directory naming makes sense? I would expect creation of directory like this: cocoon/branches/cocoon-forms-1.0.x Putting Cocoon Forms 1.0.0 into

Re: BookDefinition instead of NavigationDocument

Grzegorz Kossakowski wrote: Grzegorz Kossakowski pisze: Hi, You have probably noticed that I'm doing some documentation work. I wanted to have better (meaningful) URLs for documents I create and recalled that Daisy has support for this. Then I found that we use BookDefinition instead of

Cocoon 2.2 documentation online!

While I was creating all the release artifacts of Cocoon 2.2RC2 I also published our 2.2 docs. See http://cocoon.apache.org/2.2/ I have to say that I'm really proud of seeing this long-term effort finally materializing :-) Thanks to all the involved helping hands! The only missing part is

Re: Cocoon 2.2 documentation online!

Reinhard Poetz wrote: While I was creating all the release artifacts of Cocoon 2.2RC2 I also published our 2.2 docs. See http://cocoon.apache.org/2.2/ I have to say that I'm really proud of seeing this long-term effort finally materializing :-) Thanks to all the involved helping hands!

Re: Renewing Apache Fop processor

Vadim Gritsenko vadim at reverycodes.com writes: ... I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version?... I think that's what http://issues.apache.org/jira/browse/COCOON-1795 does - some assembly

Re: Cocoon 2.2 documentation online!

Vadim Gritsenko wrote: Reinhard Poetz wrote: While I was creating all the release artifacts of Cocoon 2.2RC2 I also published our 2.2 docs. See http://cocoon.apache.org/2.2/ I have to say that I'm really proud of seeing this long-term effort finally materializing :-) Thanks to all the

Re: BookDefinition instead of NavigationDocument

Grzegorz Kossakowski pisze: Hi, You have probably noticed that I'm doing some documentation work. I wanted to have better (meaningful) URLs for documents I create and recalled that Daisy has support for this. Then I found that we use BookDefinition instead of NavigationDocument for our

Re: Renewing Apache Fop processor

Robby Pelssers wrote: Hi Vadim, I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version? It _should_ work fine with it, even with 2.1.9. Vadim Cheers, Robby -Oorspronkelijk bericht- Van: Vadim

Re: Branching cocoon-forms

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Reinhard Poetz wrote: Grzegorz Kossakowski wrote: Hmmm, does such structure and directory naming makes sense? I would expect creation of directory like this: cocoon/branches/cocoon-forms-1.0.x Putting Cocoon Forms 1.0.0 into cocoon-2.2 does

Re: svn commit: r580303 - /cocoon/branches/cocoon-2.2/cocoon-forms-avalon-based/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grzegorz Kossakowski wrote: [EMAIL PROTECTED] pisze: Author: giacomo Date: Fri Sep 28 04:13:23 2007 New Revision: 580303 URL: http://svn.apache.org/viewvc?rev=580303view=rev Log: branch Avalon based CForm blocks Added:

Branching cocoon-forms

Grzegorz Kossakowski wrote: [EMAIL PROTECTED] pisze: Author: giacomo Date: Fri Sep 28 04:13:23 2007 New Revision: 580303 URL: http://svn.apache.org/viewvc?rev=580303view=rev Log: branch Avalon based CForm blocks Added: cocoon/branches/cocoon-2.2/cocoon-forms-avalon-based/ - copied

Re: svn commit: r580303 - /cocoon/branches/cocoon-2.2/cocoon-forms-avalon-based/

[EMAIL PROTECTED] pisze: Author: giacomo Date: Fri Sep 28 04:13:23 2007 New Revision: 580303 URL: http://svn.apache.org/viewvc?rev=580303view=rev Log: branch Avalon based CForm blocks Added: cocoon/branches/cocoon-2.2/cocoon-forms-avalon-based/ - copied from r580301,

Re: Code freeze - over

Reinhard Poetz pisze: Grzegorz Kossakowski wrote: Reinhard Poetz pisze: Thanks Reinhard for taking care! It's nice that we will be able to start creating buzz about Cocoon 2.2 shortly! :-) ;-) btw, I've forgotten to mention that I'm waiting for the solution(s) that fix(es) Giacomo's

Re: Code freeze - over

Grzegorz Kossakowski wrote: Reinhard Poetz pisze: All release artifacts and their docs have been created. This means that the code freeze is over and our SVN is happily awaiting your commits again! Currently trunk doesn't build because the parent pom references are not set correctly. I will

RE: Renewing Apache Fop processor

Hi Vadim, I forgot to mention we are working with cocoon-2.1.10. Did somebody already try to use a newer version of FOP for this cocoon version? Cheers, Robby -Oorspronkelijk bericht- Van: Vadim Gritsenko [mailto:[EMAIL PROTECTED] Verzonden: donderdag, september 2007 19:18 Aan:

Re: Code freeze - over

Grzegorz Kossakowski wrote: Reinhard Poetz pisze: Grzegorz Kossakowski wrote: Reinhard Poetz pisze: Thanks Reinhard for taking care! It's nice that we will be able to start creating buzz about Cocoon 2.2 shortly! :-) ;-) btw, I've forgotten to mention that I'm waiting for the solution(s)

Re: Java 1.5

Hi, On 28 Sep 2007, at 05:38, Joerg Heinicke wrote: And what's the use of it? I just don't get it why a framework should set restrictions on its user base. Well, by that argument we should make cocoon work with Ruby, C++, Lisp, Erlang, etc etc ... don't want to restrict our users to just

Re: Cocoon 2.2 documentation online!

Reinhard Poetz schrieb: While I was creating all the release artifacts of Cocoon 2.2RC2 I also published our 2.2 docs. See http://cocoon.apache.org/2.2/ I have to say that I'm really proud of seeing this long-term effort finally materializing :-) Thanks to all the involved helping hands!