[argouml-dev] How to prevent breaking modules/plug-ins...

[Michiel van der Wulp]

Hi *,

Long, long ago, there were a few ArgoUML developers, that agreed on a
solution for the problem of being able to modify ArgoUML code, while
preventing breaking external plug-ins / modules.

The argouml-sequence project did not compile this morning due to a (very
welcome) argouml core change.

The solution is to have all these projects installed in Eclipse, so that you
will get compile errors when you break something.
This is also the reason that the main ArgoUML developers have commit rights
in these external projects.

So, this message to all core devs:
Please install all the team project-set (.psf) files contained in
argouml-core-tools/eclipse!

And this message to all module devs:
Please provide a team project set (.psf) file for your project, to be
put in argouml-core-tools/eclipse, and maintain it!

This morning, I corrected the current problem, and submitted a
argouml-sequence.psf, to prevent this case in the future.
Regards,
Michiel

[Tom Morris]

If I break something, please feel free to send me email directly. It'll get
read and fixed faster than sending oblique comments to the dev list, which I
read less frequently.

Post by Michiel van der Wulp
Please install all the team project-set (.psf) files contained in
argouml-core-tools/eclipse!

To be effective, projects need to be not only loaded, but also open and the
more open projects Eclipse has, the slower it gets. There are only two
project set files that I consider mandatory: 1) core and 2) modules. If
something is agreed to be a module that is supported by the core team, it
should get added to argouml-modules-projectset.psf. The are psf files in
that directory which have nothing to do with core ArgoUML (gef, swidgets,
etc) and others which are huge and not needed by most people (www, doc).

I don't really understand why the sequence diagram work is being done as a
plugin, but regardless, this isn't really any different than all the other
GSoC projects which are running on separate private branches. I think it's
the job of the developers on those branches to synchronize with the trunk
when it's convenient for them. It's too much work to force the core
developers to maintain all these private projects/branches.

Tom

[Linus Tolke]

Hello Michiel!

You have simplified the description of the problem and solution very much in
this so the real problem is not at all that simple and the solution is not
that clear.

I am hoping that this will be addressed by the upcoming source
reorganization and have not bothered to much with it.

How can the setup instructions for Eclipse be improved to clarify this?

/Linus

Post by Michiel van der Wulp
Hi *,
Long, long ago, there were a few ArgoUML developers, that agreed on a
solution for the problem of being able to modify ArgoUML code, while
preventing breaking external plug-ins / modules.
The argouml-sequence project did not compile this morning due to a (very
welcome) argouml core change.
The solution is to have all these projects installed in Eclipse, so that you
will get compile errors when you break something.
This is also the reason that the main ArgoUML developers have commit rights
in these external projects.
Please install all the team project-set (.psf) files contained in
argouml-core-tools/eclipse!
Please provide a team project set (.psf) file for your project, to be
put in argouml-core-tools/eclipse, and maintain it!
This morning, I corrected the current problem, and submitted a
argouml-sequence.psf, to prevent this case in the future.
Regards,
Michiel
---------------------------------------------------------------------