> serve different markets. They can quite easily sit together as could
> jasper/velocity/php/xsp. My contention is that Avalon is intending to serve
> the same market as library.

Ok, Avalon and library will sit togheter as well - as part of the jakarta
project.

We are not going to solve anything by continuing to argue about that - 
whatever we say, avalon goal is to do that too :-)

There is a simple solution - vote. It's a decision that is to be made by
this community, I think we understand your argumensts good enough.

I'm +1 on having "Commons" as a separate project from avalon, even if they
have some ( or all ) goals in common ( since Avalon has all the possible
goals ).

Ted can count my vote, and I'll stop writing mails about this issue.

Costin


Reply via email to