[EMAIL PROTECTED] wrote:
(Berin, i just want to help !!! I like the Avalon stuff and am not here to fight!)
Neither am I, I'm sorry if you took it that way.
Short answer: when it is done.
Longer answer: We have other things in the queue that we have to take
care of first--and then we can focus as a community on those libraries.
As i understood, assembly and meta will come as the basis of Phoenix, Fortress
and Merlin assemblies ??? In something like a six month time frame. Am i wrong ?
So, what is still to be done ?
Assembly and Meta are still largely contributed by one "super
developer", who is also working on Merlin. Before the community
can get behind a release, they have to get behind his code. That
hasn't happened yet, but we do have a plan to get there.
We want to get everything necessary for Fortress and Cocoon released
so that any users can upgrade. From there we will look at the Merlin
stuff and see how close it is to a release. We really can't say until
we look at it as a whole community how long it will take.
I think i will base my devs on this as i don't want to be container-dependant.
So i would like to know what parts have stable design and stable implementations
?? Which are to be leveraged and validated ??
A5 will have a better level of container independence. If you follow
the container release path, you can gradually gain container
independence while getting real functionality now.
RIght now, we are focusing on #1 ECM, #2 Fortress, #3 Phoenix (it is
already a released product we are still supporting it for the forseeable
future), #4 Merlin, #5 A5 container.
We can get Fortress and ECM out in short order--we just need to get
the supporting components ready as well. It is time consuming, but
worthwhile.
* I can't find a clear recent road map for the whole Avalon project on
the web
site. I know you are in the process to move to avalon.apache.org but
maybe i did
not search enough. Do you have one ? What are the priorities ?
We have one, but we have not put up the document yet.
Could you send it to me please ??
Step one: Release everything that is already released.
Step two: Release Fortress as Avalon Container (embedded level)
Step three: focus on Merlin as the next Avalon Container (embedded
level).
Step three will take some time as it the rest of us will undoubtedly
have some input and change some of the internal structure of it.
Nothing too drastic, but just make it a little easier to digest.
It already is deprecated. All the rest of our documentation needs to
be
updated. Hopefully, this is done and we can get Avalon 4.1.4 released.
Great! The version i got by CVS don't show this ? Is there a place in the CVS
where the framework is complete (apart assembly and meta) ? I could help a lot
on documentation as a start...
It's in there (the Prego commercials).
The Component package is "soft" deprecated, so its use is still
discouraged while trying to move our users off of the legacy code.
It isn't as easy as it looks as several projects have many many
users and several books that describe how to use it for their
own projects (thinking of Cocoon specifically here).
Question by the way: org.apache.avalon.excalibur.* is old design and
org.apache.excalibur.* is the new, right ??
Not really a design, just a new package name idiom.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
