Hello Bob!
The dependency issues is on another level than the split in tigris projects.
That is handled by creating separate source trees. Note also that there is
no difference between a subsystem (from argouml/src) and a separate tigris
project w.r.t. the organization of source, tests, location of resulting
jars, Eclipse project set-up.
There are two reasons for keeping separate tigris projects. The most
important one is the authorization issues. I feel we can be very generous
with granting developer status in the small projects, especially if they are
not included in the release or has a slim change of disrupting the release
like an internationalization project. For the core project, that also
includes authorization for all projects, I would like to have a better
feeling for the person before granting a developer role and I can get
that by allowing them to work in other projects.
Putting the java code generation and reverse engineering in a separate
project is an important statement. It signals that Java is just another
language supported by ArgoUML (because all other languages are in separate
projects). Not looking at the authentication and message issues, it could
just as well have been a separate subsystem within the core project.
The created subsystems each have a separate interest group or competence and
I think that is a good match for persons and authorization.
/Linus
2008/5/16, Bob Tarling <[EMAIL PROTECTED]>:
>
> 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]
>
>
