Hey Jorg,
w00t! Good goings! This has been a lng process :-)
On Feb 14, 2007, at 6:46 PM, Jorg Heymans wrote:
The new release of excalibur is long overdue, but finally here it is :
http://people.apache.org/~jheymans/excalibur-release.tar.bz2
...
Also-1: i have provided the release
Hi Reinhard!
look for all nag/ tags and comment them out, and that will stop the flow
of e-mail. Note it isn't quite spamming -- cocoon requested these e-mails,
really!
Please don't simply remove the files, they contain valuable gems of info!
To work with the 2.1.x branch, if the build
Hi gang,
So, Peter Royal and I decided to do a BoF Thursday night at 20:30 (GMT+2).
It looks like a lot of people might actually make it. We found some worried
users and some worried developers and some curious people :-). We're going
to be trying to answer some of the unanswered questions
On 16-06-2005 17:00, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Thu, 16 Jun 2005, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
Now, I would be totally in favor of granting the gump committers
commit access to the cocoon project.
Should be quite trivial to add a rule to asf-authorization that
On 17-06-2005 05:24, Stefano Mazzocchi [EMAIL PROTECTED] wrote:
Should be quite trivial to add a rule to asf-authorization that grants
rw to @gump for just that file, at least I think it allows
file-granularity.
Even better. Can we do it or is it something that infra@ has to do?
All pmc
possible, but a few packages will need to be changed to get things
compiling again.
Let me know if you have any questions or concerns.
Cheers,
Leif
Leo Simons wrote:
Hi gang,
gump just said:
---
prepare:
[echo] Apache Cocoon 23102004 [1999-2004]
snip/
compile-core:
[copy] Copying
Hi gang!
As you may well be aware, avalon-excalibur has split out and is now
excalibur.apache.org. All the content that used to be in the
avalon-excalibur cvs module is now @
https://svn.apache.org/repos/asf/excalibur/trunk/
this includes the fortress and ecm containers, by-the-way.
Just like
Stefano Mazzocchi wrote:
Rolf Kulemann wrote:
After the vote we have to do many more things like doing the incubator
request. It would be fine if someone can give me a hint how the requests
for endorsement and release should look like.
Eh, good question, I've never done it before. Let's ask the
a year exploring solutions to these kinds of things and so far I
just haven't encountered any fundamental issue which you seem to be
fearing exists. When you say not elegantly possible people believe it
and that may be a bad thing if you're wrong ;)
--
cheers,
- Leo Simons
Leo Sutic wrote:
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
write a failing testcase that doens't require me to understand every
little detail of cocoon internals and I could try.
Easy.
snip/
made that into an actual testcase :-D:
public abstract class ReloadingProxyTestCase
around the reference. With java, barriers are way easier (because of
synchronization being available), but very expensive too.
If you want a hotswapping kernel, you probably want to look into
hotswapping kernels. Mach (now darwin) is a textbook example I think.
--
cheers,
- Leo Simons
Leo Sutic wrote:
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Leo Simons
again, from memory, the real tough part is the barrier that's
in place around the reference.
I'd say the hard part is when A has significant state that isn't
preserved when it dies.
right! Any reason it can't
/platform/container-integration/src/test/org/jicarilla/container/test/integration/avalon/
if I can figure out how to do this all on my own, surely the cocoon
community will have no trouble whatsoever attaining interoperability
between new-style and old-style blocks you need.
--
cheers,
- Leo Simons
13 matches
Mail list logo
