I would suggest both (c) and (d). I would suggest as soon as possible. I think it was originally delayed waiting until a release takes place first. We had no idea it would take so long till the next release happens and we have no real guarantees now. Lets not wait.
I think that putting this into the repository as a module has some benefits. We have a concept of subsystems (often a one to one relationship to the subcomponents in IZ). But most of our subsystems don't have a defined API. Instead many of the subsystem are within the main project/jar which is argouml-core To place this into svn as a separate eclipse project shows it clearly as a separate subsystem physically. I would hope we can then follow on similarly with the other diagrams. I've been trying to find the email with lack of success so far but I have seen mentioned somewhere that the concept of breaking the main project up into modules this way fits far better with eclipse architecture. Parts of the application are discovered at runtime. Whether we release the new sequence diagrams as part of the next release I think is a separate matter and should not be part of this decision to bring the source into the ArgoUML project. By having this as a module then the decision to include it in a release later will require hardly any change, just a change in the build script. Where the modules architecture helps our subsystem is in dependancies. A subsystem like sequence diagram needs to be dependant on the core application but we don't want any cyclic references with the main application being aware of sequence diagram. But we do somehow need the core application to become aware of the sequence diagrams at runtime in order to present the correct "New Sequence Diagram" button etc. We will need a way to define modules that are core modules as opposed to external/optional modules which is all we have at the moment. Bob. \ On 05/04/2008, Christian López Espínola <[EMAIL PROTECTED]> wrote: > Hi, > > This week I have some holidays, so I planned to work on the sequence > diagrams and merge them into the trunk, so they'll have more > visibility, you'll blame at me, and I'll be more motivated to work on > them. > > BTW, we have a release plan again and a repository restructure, so I > wonder what should I do. We have some options: > a) Wait until the release to integrate them on the svn repos (It's not > ready for a release, but maybe source code could be on trunk by then) > b) Wait until the svn repos restructuring. > c) Do it ASAP > d) Leave it as a module (this doesn't like me, because it won't be seen) > > I'd like to get feedback from you until Wednesday/Thursday, when I'll > be able to work on it. > > TIA. > > -- > Regards, > > > Christian López Espínola > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
