Hello Tom!
Are there issues for these reorganizations? I can't find them.
There are a lot of considerations before doing this work and we need a
plan for how to do it and where different things are to end up after the
change.
This is the first time I learn about these special Eclipse-plugin
requirements. Where shall we document them?
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 15 december 2006 22:18
> To: [email protected]
> Subject: RE: [argouml-dev] Where did all the SVN tags go?
>
> > If we were to add a function that appends information to the
> > subversion:tags property, is it enough to do it on /trunk
> > i.e. the root of the branch or tag or does our Eclipse setup
> > require it to be on /trunk/src_new, /trunk/lib, [etc ...]
>
> As I understand it, Subclipse stores this information on the top level
> directory associated with the Eclipse project, so it would need to be
done
> once for each project.
>
> That brings up another point though. I held off on pushing to get the
> source tree reorganized while we were on CVS and it would cause us to
lose
> all the revision history. Now that we're on SVN, it would be good to
get
> things better organized. For example, we could finally get rid of
src_new
> (which, as I understand it, is counterintuitively the old source
tree).
>
> We also have some issues with our inter-project dependency graph that
need
> to be cleaned up. Model-MDR depends on Model, but then Model contains
a
> reference to Model-MDR in a string literal which introduces a cyclic
> dependency (but not one which can be easily detected). ArgoUML
depends on
> GEF in core-lib, but then it passes in resource references which cause
GEF
> to attempt to do up level references to ArgoUML, creating another
cycle.
> This is an issue when things are deployed as Eclipse plugins because
> Eclipse
> enforces a strict unidirectional dependency graph with no cycles or
> uplevel
> references allowed between plugins.
>
> Tom
>
> ---------------------------------------------------------------------
> 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]
