Peter Donald wrote:
> Hiya,
>
> I just got asked *again* about when Fortress is going to be stable and
> released. Quite a few people still use ECM and want to migrate to it's
> successor with zero if any significant impact. I would really like to see
> Fortress released sooner rather than later and with ECM features closely
> matched.
>
> I don't know the status of metadata stuff but it may be a an idea to put it
> off till Fortress2 or work on it in a branch or something. However I would
> love to see a release soon. If needs be could we go back in time and branch
> fortress then to provide a stable release?
We need to add support for the old Recycleable interface (for
compatibility reasons). My take is to use reflection, and determine if
the class has a public recycle() method and just use it. That way we
don't have to migrate interfaces or anything like that.
The MetaData stuff is not working yet, but it is being worked on in a
way so as not to interfere with the DefaultContainer (i.e. the current
way of doing things).
That said, we need to add the proper docs (as outlined in another
thread) for Fortress, and all its dependencies. We can release
Fortress then. If we have any volunteers, we can get this party
started sooner than later. I have a class I need to get to the point
where it compiles, and after that I can tackle the "Recyclable" issue.
I need help with documentation and getting the other pieces released.
Fortress uses a lot of other pieces:
Concurrent
Collections
Container (for the legacy compatibility)
Event
I18n (for Meta)
Meta (for the metadata stuff)
SourceResolver
AltRMI (for Instrumentation)
Instrument
Instrument-Manager
Util (for System--haven't moved that over yet)
Logger
ThreadContext
I can release it as Beta which will allow us to use all the other
stuff whether it is released or not. A final release will require
getting everything else released.
--
"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]>
