> I would like to see Merlin become the "one true container" that it
> promises.
> I would like to see ECM, Fortress, and Pheonix completely done away with.
> I'm fine with there being more than one Avalon container out there (I'm
> for
> that).  But the "official" (reference implementation if you will)
> container
> should be Merlin.  It is difficult enough for the community to maintain a
> single container.

+1

> I would like to see Avalon PI.

+1

> I would like to see better communication between Avalon and other Apache
> projects (such as Commons and Maven).  There is too much duplicated code
> and
> functionality between Apache projects.

+1 and absolutely critical to our success.  A lot of the junk I added to
that env package (env vars stink by the way) is available in commons and
in ant.  So is the discovery stuff.  I need to keep my mental catalog of
what's out there up to date.  

Also when we start out on something we should post to lists to double
check whether functionality already exists in other projects.  Writing 
code is a responsibility and not a privilege so the less of it you can
write to obtain the same functionality the better.

> I have a dream!

I have too many to come true.

Alex



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to