RE: [argouml-dev] argouml-emf

Hello Markus!

Please try to avoid forking as long as possible.

Instead, we should use this opportunity to redesign the Model subsystem
interface to fit UML 2.0. 

The difficulties are when new things appear that has no support in the
MDR version. In those cases I hope we can find a way to respond to the
new methods that makes ArgoUML behave well using both implementations.

On a technical note, notice that the model plug-ins in ArgoUML are much
more static than all other plug-ins. They cannot be enabled and disabled
at run-time, they must be available on the classpath when ArgoUML
starts, they cannot coexist with other model plug-ins... This is by
design.

If you want, I can create the basic infrastructure with classes with
empty methods and fix the build scripts and Eclipse configurations that
are needed. I know how this is done. After that you can focus on the
things close to emf i.e. filling the empty methods with emf-specifics.

        /Linus

> -----Original Message-----
> From: Markus Klink [mailto:markus.klink@xxxxxxx]
> Sent: den 1 november 2006 07:06
> To: dev@xxxxxxxxxxxxxxxxxx
> Subject: [argouml-dev] argouml-emf
> 
> Hello *,
> 
> just wanted to let you know that I will very slowly, time permitting,
> start developing the argouml-emf plugin. I will at first try to get
some
> very basic things going, and after that I will probably need to fork
> argouml, or we need to have another strategy how we can work with the
> UML 2.0 metamodel which emf/uml2 require and the UML 1.4 that
> netbeans/mdr requires.
> 
> Markus
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx