Daisy backups

Hi, I still have Daisy backups running on people.apache.org (https://issues.apache.org/jira/browse/COCOON-1925) but I must admit I'm not watching or checking them regularly. Could someone who's currently more involved in Cocoon than me setup a second backup? I can provide my scripts if needed,

Re: Plugging that big XSP shaped hole

Kamal wrote: Hi, As has probably been discussed numerous times on this list, XSPs are deprecated (or at least perceived to be, I won't get into the philosophical discussion ) and flowscript + JXTemplates are the new deal. As I (as well as others) have said in the past, I don't think that

Import my key into the KEYS file

Hi all, I uploaded the Cocoon 2.1.11 jars a couple of weeks ago into the m1 synch repository using the script from SVN. It turned out that when I ran the script it did not create .asc files. As a complete newbie to this kind of thing, I got a nice email from the repository team that told me

Re: Import my key into the KEYS file

Jeroen Reijn wrote: Hi all, I uploaded the Cocoon 2.1.11 jars a couple of weeks ago into the m1 synch repository using the script from SVN. It turned out that when I ran the script it did not create .asc files. As a complete newbie to this kind of thing, I got a nice email from the

Re: Import my key into the KEYS file

Thanks Carsten! I'll give it a try. If found this message, but it was a but inclear, but after reading it 3 times.. I get it. I'll give it a go. Once I commit it into SVN will it also appear on the /dist/ or is SVN the only place it has to go in? Regards, Jeroen Reinhard Pötz wrote:

Re: Plugging that big XSP shaped hole

As the author of xsp-action, I have to say it was an ugly hack, meant primarily for speeding up development cycles at a time when we did not have flowscript nor hot code replace in Java debuggers. Now your use case is right, and I agree that flowscript is overly complex when all you need

Re: Plugging that big XSP shaped hole

Kamal wrote: As the author of xsp-action, I have to say it was an ugly hack, meant primarily for speeding up development cycles at a time when we did not have flowscript nor hot code replace in Java debuggers. Now your use case is right, and I agree that flowscript is overly complex when

[jira] Subscription: COCOON-open-with-patch

Issue Subscription Filter: COCOON-open-with-patch (106 issues) Subscriber: cocoon Key Summary COCOON-2213 Change check on mime-type to enable custom encoding of the body https://issues.apache.org/jira/browse/COCOON-2213 COCOON-2212 jx:attribute does not check name is correct

Re: Plugging that big XSP shaped hole

Sylvain Wallez wrote: Kamal wrote: As the author of xsp-action, I have to say it was an ugly hack, meant primarily for speeding up development cycles at a time when we did not have flowscript nor hot code replace in Java debuggers. Now your use case is right, and I agree that flowscript

Re: Plugging that big XSP shaped hole

Kamal escribió: Sylvain Wallez wrote: Note that there is a BSFAction that can be used for actions using any of the scripting languages supported by BSF (including JS), but it isn't closely integrated with the flowscript data. What do you mean by closely integrated with Flowscript? Where is