J.Pietschmann wrote:
Leo Simons wrote:
the alternative is to only depend on
http://www.apache.org/dist/avalon/excalibur/latest/
What worries me is that excalibur depends on a class
distributed with Xalan.
which package are you referring to, and why is it worrying it depends on
Xalan? Something
Leo Simons wrote:
which package are you referring to,
IIRC org.apache.xml.utils.PrefixResolver
and why is it worrying it depends on Xalan?
I'd like to rip out the Xalan jar, put in Saxon, and start
Cocoon without being surprised by a ClassDefNotFound exception.
J.Pietschmann
Carsten Ziegeler [EMAIL PROTECTED] writes:
I would like to a add one more point: Most of us do not care about
releasing new versions. We *must* come back to release often - release
early. But each time, we try to get a new version out, someone comes
up and says: Wait XYZ is not
Carsten Ziegeler wrote:
Stefano Mazzocchi wrote:
There are a few things that we are doing wrong. I'll make a dump of my
random thoughts about these in order to foster a discussion.
Ah, it's time again to write an email that is larger than four lines. Hmpf.
Now, I think the problems you mention
First, Stefano, relax - I didn't want to attack you directly.
Don't assume that all my comments were hinting at something you did!
So...
Stefano Mazzocchi wrote:
I'm doing refactoring because I want to release, not the opposite.
Dito and see comment above.
Removing dependencies will improve
Carsten Ziegeler wrote:
First, Stefano, relax - I didn't want to attack you directly.
Don't assume that all my comments were hinting at something you did!
Sorry but it looked pretty personal to me.
Apologies if it was not the case.
Moving the SourceFactory to Avalon made a mess. This is what I'm
Stefano Mazzocchi wrote:
Carsten Ziegeler wrote:
First, Stefano, relax - I didn't want to attack you directly.
Don't assume that all my comments were hinting at something you did!
Sorry but it looked pretty personal to me.
Sorry for that - I really hate writing long emails and perhaps
I want to know if somebody feels like I'm doing this but remains silent
because of any reason.
Perhaps because you are Stefano? Think about it :-).
Matthew
--
Open Source Group Cocoon { Consulting, Training, Projects }
=
Jeff Turner wrote:
What would removal of the Scratchpad force on the community?
* More controlled innovation. Instead of anybody using it as their
personal playground, it would force the development to be more in
the face of the community.
Hence schecoon would have been shot down in flames,
Matthew Langham wrote:
I want to know if somebody feels like I'm doing this but remains silent
because of any reason.
Perhaps because you are Stefano? Think about it :-).
There are many things I can do but the only one thing I cannot possibly
do is to avoid being who I am.
If you think you
Stefano Mazzocchi wrote:
Recently on avalon-dev I expressed my concerns about their habit of
moving stuff around for elegance-sake, but I'm starting to think that
Cocoon is abusing avalon and this places too much pressure on their
shoulders.
ah, the load, the load! I can't take it anymore
Leo Simons wrote:
Stefano Mazzocchi wrote:
(AltRMI is no longer part of avalon though; that's in incubator now)
Of this list, if it is possible and sensible to remove the cocoon deps on
cli,
Easy enough.
collections,
concurrent,
Both done--all that is required is a new ECM
IO,
I don't think
Stefano Mazzocchi wrote:
Recently on avalon-dev I expressed my concerns about their habit of
moving stuff around for elegance-sake, but I'm starting to think that
Cocoon is abusing avalon and this places too much pressure on their
shoulders.
Example: the instrumentation. The Cocoon core
Stefano Mazzocchi wrote:
ah, the load, the load! I can't take it anymore
action type=jump-of-cliff entity=avalon/
Aaa a a a ah!
:D:D Just kiddin' :D
LOL :)
Anyone know the album cocoon crash by K's Choice? Sounds a bit
different :D
I have to be honest with you: I find the
Leo Simons wrote:
I have to be honest with you: I find the dependency on tons of small
jars disturbing to say the least. I know it's probably possible to
move from excalibur-cli to commons-cli or whatever, but I don't know
how, nor, to be honest, I even dare to touch it. And this is just an
Stefano Mazzocchi wrote:
Leo Simons wrote:
I have to be honest with you: I find the dependency on tons of small
jars disturbing to say the least. I know it's probably possible to
move from excalibur-cli to commons-cli or whatever, but I don't know
how, nor, to be honest, I even dare to touch
Leo Simons wrote:
the alternative is to only depend on
...
http://www.apache.org/dist/avalon/excalibur/latest/
What worries me is that excalibur depends on a class
distributed with Xalan.
J.Pietschmann
Stefano Mazzocchi wrote:
I'm slowly working at finding out the internal dependencies of Cocoon
core myself. Let's not step on each other toes.
I wouldn't worry 'bout that. Me not cocoon committer, nor intending to
become one :D
cheers,
- Leo
There are a few things that we are doing wrong. I'll make a dump of my
random thoughts about these in order to foster a discussion.
Building on sand
We developped a habit of building on sand.
Recently on avalon-dev I expressed my concerns about their habit of
moving stuff
Stefano Mazzocchi wrote:
There are a few things that we are doing wrong. I'll make a dump of my
random thoughts about these in order to foster a discussion.
Building on sand
We developped a habit of building on sand.
Recently on avalon-dev I expressed my concerns about their
Stefano Mazzocchi wrote:
I repeat my proposal to kill the scratchpad
Totally +1, since it will hopefully also motivate people to start a
project next to and depending on Cocoon rather than inside it.
enough for now. i need food.
Bon appétit ;-)
/Steven
--
Steven Noels
Steven Noels wrote:
Stefano Mazzocchi wrote:
I repeat my proposal to kill the scratchpad
Totally +1, since it will hopefully also motivate people to start a
project next to and depending on Cocoon rather than inside it.
Actually, I have a need to do this, and I wonder what the best
approach
Stefano Mazzocchi wrote, On 25/02/2003 19.55:
There are a few things that we are doing wrong. I'll make a dump of my
random thoughts about these in order to foster a discussion.
Building on sand
We developped a habit of building on sand.
Recently on avalon-dev I expressed my
Nicola Ken Barozzi wrote:
snip/
Scratchpad considered harmful
-
I proposed to remove the scratchpad and no consensus was reached. I
try again but this time harder: I think the scratchpad is harmful.
Reasons:
1) for non-core stuff, alpha blocks will do just fine and
On Tue, Feb 25, 2003 at 05:37:07PM -0500, Berin Loritsch wrote:
Nicola Ken Barozzi wrote:
...
I repeat my proposal to kill the scratchpad
Hmmm... how could we have done the flow without the scratchpad?
Do you really think that Schecoon could have been done in head?
Make the
On Tuesday, Feb 25, 2003, at 20:57 US/Pacific, Jeff Turner wrote:
What would removal of the Scratchpad force on the community?
* More controlled innovation. Instead of anybody using it as their
personal playground, it would force the development to be more in
the face of the community.
Stefano Mazzocchi wrote:
There are a few things that we are doing wrong. I'll make a dump of my
random thoughts about these in order to foster a discussion.
Ah, it's time again to write an email that is larger than four lines. Hmpf.
Now, I think the problems you mention have all the same
27 matches
Mail list logo
