Hi Leo, > Nah...there's work going on in avalon in different areas. > Everything you > find at http://www.apache.org/dyn/closer.cgi/avalon is in development > and supported. Everything not there is "in development" and > unstable by > definition.
Well, I started with newest Avalon and Excalibur from this location, but run into a lot of deprecated API usage and Fortress is not part of this Excalibur archive anyway ... further comments below. > Merlin is alpha code, fortress and ECM aren't. ECM has been stable a > long time. Fortress is basically finished and we're cleaning > things up > so it can be released (basic roadmap: logkit release coming up, then > framework, then ECM, then fortress, then phoenix). I think you'll see > lots of development and work going into merlin, with lots of changes, > after those releases (I for one have lots of plans :D). Yes, I've seen the plans for the dveelopment lines :) > yep. Merlin _is_ a quickly moving target. It is not intended for > 'newbies' at this stage. Yes and no. No from a "product view", yes from a "technical view", since any of the other containers will be adapted/integrated into Merlin at some stage. > It doesn't make too much sense to write a lot of docs right > now because > things will change and the docs will no longer be correct. Perfectly understandable. > > Looking at the time I already spent and the results I reached, I am > > currently really somewhat frustrated. Any help welcome ... > > I hear ya. Merlin is a complex beast (but becoming less so). I would > suggest that if you just want to actually develop software, you stick > with stable (or at least beta) packages. Running along with merlin is > cool (interesting stuff going on), but you have to realize it > is out on the edge. Yes, I realize this, but well, see below. >[...] > > PS: don't worry too much about those deprecation warnings. > The Component > interface and friends are about as deprecated as > java.util.Vector, but > slightly less so. IOW: They'll be around. See my way: I started with pure Avalon framework, when I stumbled over ECM in DwA. Analog code to DwA based on ECM resulted in the usage of deprecated API. This is something our QA will not accept. I realized, that the deprecation became soft for 4.1.4 and therefore I started to compile the necessary Avalon stuff myself. The framework and LogKit compiled fine for a distribution - Excalibur did not, because of errors in intrument-manager. Now AltRMI is in transition state and I still have not working Fortress. But, you may have read my answer to Steve already, I do not feel to comfortable running all my components in separate threads ... what does Fortress? Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
