If there is not going to be any changes to the core argouml until after
0.26, I see no problem in this. The details will have to be synchronized
with the plan for the first few 0.27 releases but I don't think it will be a
problem.
/Linus
2008/5/16, Thomas N. <[EMAIL PROTECTED]>:
>
> > Is there any reason to keep both? Is it too risky to just commit to
> > the transition after 0.26 is released and move everything over to the
> > new module? My preference would be to keep the transition period as
> > short as feasible to minimize the extra work.
>
> I'd suggest a step-by-step transition, based on the moving of parts of the
> Java support. Java import is the first available part, so something I can
> definitely promise is:
>
> Step 1: After 0.26 (when working towards 0.27.1), switch to the module for
> Java sources import, which includes:
> - adding the module to the ArgoUML deployment
> - freeze org/argouml/uml/reveng/java (and later remove it)
> - for Java source import, only work in the module (fixes/enhancements)
> - in the module, add an ant task that only packages the import code into
> the module (alternative: use svn branching)
>
> Step 2 then would be the move of another part (e.g. code generation) with
> similar steps, and so on. A roadmap has to be made.
>
> What do you think, is this feasible?
>
> Thomas
> --
> Psssst! Schon vom neuen GMX MultiMessenger gehört?
> Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
