Sam Ruby wrote:
Responding out of order.
Berin Loritsch wrote:
Note that this is the same Berin Loritsch who is concerned about depending
on componentry outside of the Avalon family due to perceived loss of
control.
I never said I couldn't be convinced, I just said that there are things I need
to know first.
You'll find me alot easier to convince than the Axis crowd ;)
Could you more expound on these fears toward Avalon that you are aware of,
since I was honest and forthcoming enough to share the ones I have toward
Commons?
There are quite a few projects under the Apache umbrella that I see as
simultaneously unwilling to depend on others, and puzzled that more people
are not willing to depend on them.
Do I want to increase the Avalon community? Definitely! I don't see how
moving Avalon code outside of Avalon increases *Avalon's* community. I
can
see how it increases *Commons* community.
Sigh.
Turbine and Struts are generally polar opposites, but at least they can
share a set of collections classes.
Perhaps, but as I said before, I can't commit the Avalon team on my own, and I
haven't seen any of the other committers input on this yet. In the end, it is
a team decision.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
