> So the only reason someone would use the library is if they didn't want to
> work with Avalon? Is that correct? So you think we shout start a process of

No. I would turn it around - because  Avalon doesn't provide what
we need.

It's never the people fault for not "working with" any project - it's the
project fault for not attracting the people and failing to get them to
"work with it". 


You don't get because you allways compare some generic avalon goals (
which are far from the current reality ) and would include everything in
jakarta with just a bit more stretching.

Again, what is Avalon ? 

The code ? We are talking clearly about a different code base, based on
existing code from projects, so it'll be clearly distinct ( it may include
avalong code )

The community ? It seems we have here a quite different set of people.

The goals ? It seems you imply that in all your answeres, and the goals
are almost identical with the goals of jakarta - they could include
everything. 



Costin



Reply via email to