Re: [A4:Proposal][fortress] refactoring

[Nicola Ken Barozzi]

Berin Loritsch wrote:

Leo Simons wrote:

Hi peeps,

I just committed lots of new files to fortress. I've moved fortress to a new package, org.apache.avalon.fortress, and also moved around lots of other things, basically like proposed and discussed before. Could y'all please check it out and tell me if you're okay with it?

If so, I'll update the examples and remove the old materials.

thanks!

cheers,

Now how would that affect the fact that we are trying to do Avalon
Container with codenames?  The first release being codename Fortress?

As we switch codenames, we should not have our users change the
package that they use.

I was thinking the same thing ;-)

But looking at current implementations, I don't think they will be able to use Merlin2 as a drop-in replacement to Fortress... or will they?

Are Fortress' APIs gonna become our standard container APIs?

Hmmm...

--
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]>