> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Based on the build file there appear to be the following dependencies. > > commons-collections 1.0 RELEASED (imp > version 2.0)
The most recent version (post 2.0) > excalibur-instrument 0.3 UNRELEASED > excalibur-instrument-manager 0.3 UNRELEASED > excalibur-instrument-manager-interfaces 0.3 UNRELEASED Yep, we need to release these. I think only the implementation stuff has really changed, the interface is fairly constant. > needs updating > util-concurrent 1.3.1 no This is Doug Lea's concurrent stuff--It is released. I just provided a convenience Jar. > excalibur-container 1.0 UNRELEASED This is the extensions stuff, and it should not be critical because this is an *experimental* feature. > excalibur-thread-context 1.0 RELEASED > manifest Not really needed--we can get rid of this dependency. > needs updating > excalibur-altrmi-registry 0.7 UNRELEASED > excalibur-altrmi-common 0.7 > UNRELEASED > > excalibur-altrmi-server-impl 0.7 UNRELEASED > excalibur-altrmi-server-interfaces 0.7 UNRELEASED > excalibur-altrmi-client-impl 0.7 UNRELEASED > excalibur-altrmi-client-interfaces 0.7 UNRELEASED This is only needed for the Instrument Manager stuff. If Instrument Manager can be built without it, then Fortress doesn't need it. > And I'm not sure about the following: > > excalibur-pool 1.1 ? (manifest > inconsistent) > excalibur-monitor 1.0 ? > excalibur-xmlutil 1.0 ? Only used in the comparative testing of Fortress vs. ECM. All the above are released. > Can you fill in any of the above information? > Also, is the AltRMI dependency hard or optional? I believe it is optional. > >Who wants to take on the various tasks? > > > > I'm really constrained on current tasks and still have the > refactoring > in Merlin to complete. I'll try to help where I can but > don't count on > a lot (too much internal stuff). Its a question to the community at large. How soon do we want to see Fortress released? It is currently stable, and I am holding off on any of the proposed changes until later. > >I can take on the JavaDoc tasks and the final distributable (which > >has to wait for the other documentation tasks). I need help getting > >the rest of the docs up to par. Think we can get this done > by Christmas? > > > > I would prefer to answer that after we discuss "a roadmap related to > Fortress. I.e. answering question like the relationship between the > release and future containment strategies - probable lifespan > - etc.", > and secondly, review the dependencies and release plan for > those dependencies. We already agreed that the current stuff will have their own life until Avalon 5 has something concrete. Fortress 1.0 was on a fast track to a release before the Avalon PMC talks derailed its momentum. I would like to see this out there because current users have a current need for it. They want to leave the ECM, and for now Fortress is the quickest way to do it. Pete Royal seems happy with it, and has been using it a long time. > My own feeling is that Christmas may be optimistic. It may be. :( -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
