I think we should be questioning why we need so many child tigris projects.
Initially we had a major a problem in ArgoUML with circular dependencies throughout the whole code and little modularisation. At that time I was in favour of more separation to control that. But we now have that control in the parent ArgoUML project using the eclipse project setting files that Tom set up. I think once an ArgoUML child project has reached a certain level of maturity then we should consider it for inclusion in the base project. That would include any that we automatically package as being part of an ArgoUML release. What advantage is there to keep a separate tigris project for these. I'm surprised that it was decided to split the java source to a separate tigris project. That loses us all the history of that source and now it seems they're already out of step with each other. I seem to have hijacked this thread a bit but Daves question would not be so relevant if we start to amalgamate things a bit more. Bob. 2008/5/16 Dave Thompson <[EMAIL PROTECTED]>: > Hi, > > This is probably a question for Linus. Should we ever be using issue > trackers on subprojects, or should we always use the main argouml > project one? I notice that there are a lot of subprojects listed as > components on the main project issue tracker. Does this imply that we > should submit issues there? > > I've got some issues relating to the argoumlinstaller project, and am > wondering whether to submit them on the subproject's own issue tracker > (which currently has a total of 6 issues), or on the main argouml issue > tracker. > > Regards, > > Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
