Re: Avalon Project Hierarchy

[Nicola Ken Barozzi]

Paul Hammant wrote:

We use the code in a real company and I don't see any real
impact for us by these changes directly.

Kew;

Of course, there
should be some "compatibility packaging", when it comes
to the distribution, so that you don't have to download
35 different jars to get the same as you now get by downloading
one package.

Nobody downloads 35 different jars to begin a project.  They download one container (which bundles
some jars), then add others as and when.  We're all doing Agilesque development these days?  If
yes, then it is possible we do not even start with the container.

Wawawawait... where did we start this 35 different jars issue?

Avalon Components would package each component separately *exactly* like Exaclibur components for example.
And each container would continue to distribute what the hack it wants?

Please, let's not stumble on details, and let's be constructive.

--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


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