m2m-dev

Hi Everyone,
 Per bug 376927 this list is being moved to mmt-dev.  All of your 
subscriptions have already been updated, so you can post to the new list 
immediately.  This list has been closed to new postings, and will be 
shutdown at midnight.  The archives will remain online.
-Webmaster.
--
Eclipse WebMaster - webmaster@xxxxxxxxxxx
Questions? Consult the WebMaster FAQ at 
http://wiki.eclipse.org/index.php/Webmaster_FAQ

View my status at http://wiki.eclipse.org/index.php/WebMaster
Hi
The Juno release of MDT/UML2 adds UML 2.4 and 2.4.1 support and 
consequently many more namespaces whose content handlers need to be 
correctly registered.
When running within Eclipse, the magic of extension points should ensure 
that this happens automatically.
When running standalone, these registrations have been a consumer 
responsibility. Most modeling tools have emerged in the last few years 
while UML2 has been stable with support for UML 2.2 and so the 
complexities of multi-version support is easily overlooked in some 
handcrafted UML initialisation code.
In the latest MDT/UML2 I-build, there is a UML standalone initialization 
routine (https://bugs.eclipse.org/bugs/show_bug.cgi?id=364419). Just 
invoke UMLResourcesUtil.init(null). This does all the hard work, and 
should hide the next generation of changes for UML 2.5. Only the 
physical location URI mappings are missing; i.e. from the resolution of 
"platform:/resource/org.eclipse.uml2.uml.resources/profiles/" to 
URI.createURI(UMLResource.PROFILES_PATHMAP); similarly for 'metamodels' 
and 'libraries'. If you have automated plugin location, using classpath 
analysis as performed by MWE2's StandaloneSetup scanPath, or 
org.eclipse.ocl.examples.domain.utilities.StandaloneProjectMap, this 
missing step may be done automatically as well.
A patch to upgrade org.eclipse.ocl.uml.OCL.initialize(resourceSet) to 
call UMLResourcesUtil.init(resourceSet) is in the pipeline, so consumers 
of OCL.initialize need take no action other than taking the opportunity 
to remove their duplicate initializations.
Other tools are encouraged to start using UMLResourcesUtil.init(null) as 
soon as possible so that any residual bugs are fixed for Juno, ensuring 
that UML 2.5 can be introduced without a further downstream 
initialization ripple.
    Regards
        Ed Willink
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev

Hi Dennis
I think I can do that one myself.
I'll wait a couple of days, or until Sergey comments before raising the 
webmaster request. Once renamed, I can try to adjust the components as 
required.
    Regards
        Ed Willink
On 18/04/2012 08:04, Dennis Wagelaar wrote:

+1
N.B. I would like to have a separate ATL.emftvm component for the new research vm as well.
Dennis Wagelaar
-----Origineel bericht-----
Van: William Piers
Verz.: 17-04-2012, 17:54
Aan: m2m-dev@xxxxxxxxxxx
Ondrw.: Re: [m2m-dev] M2M to MMT Bugzilla migration

+1
Le 16/04/2012 22:09, Ed Willink a Ãcrit :

Hi
Rather than just move Bugzilla across from M2M to MMT, I suggest we
also follow the new component naming convention so I propose to
request the following changes
M2M/ATL-Contribution =>  MMT.ATL/Contribution
M2M/ATL-Doc =>  MMT.ATL/Doc
M2M/ATL-emfvm =>  MMT.ATL/emfvm
M2M/ATL-Engine =>  MMT.ATL/Engine
M2M/ATL-UI =>  MMT.ATL/UI
M2M/ATL-Website =>  MMT.ATL/Website
M2M/QVT_OML-Doc =>  MMT.QVTo/Doc
M2M/QVT_OML-Engine =>  MMT.QVTo/Engine
M2M/QVT_OML-UI =>  MMT.QVTo/UI
M2M/QVT_OML-Website =>  MMT.QVTo/Website
M2M/QVT_Relations-Doc =>  MMT.QVTd/Doc
M2M/QVT_Relations-Engine =>  MMT.QVTd/Engine
M2M/QVT_Relations-Parser=>  MMT.QVTd/Parser
M2M/QVT_Relations-UI =>  MMT.QVTd/UI
M2M/QVT_Relations-Website =>  MMT.QVTd/Website
M2M/Releng =>  MMT/Releng
M2M/Website =>  MMT/Website
Any objections or better ideas?
     Regards
         Ed Willink
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev

_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2411/4942 - Release Date: 04/17/12

+1

N.B. I would like to have a separate ATL.emftvm component for the new research vm as well.

Dennis Wagelaar

-----Origineel bericht-----
Van: William Piers
Verz.: 17-04-2012, 17:54 
Aan: m2m-dev@xxxxxxxxxxx
Ondrw.: Re: [m2m-dev] M2M to MMT Bugzilla migration

+1

Le 16/04/2012 22:09, Ed Willink a Ãcrit :
> Hi
>
> Rather than just move Bugzilla across from M2M to MMT, I suggest we 
> also follow the new component naming convention so I propose to 
> request the following changes
>
> M2M/ATL-Contribution => MMT.ATL/Contribution
> M2M/ATL-Doc => MMT.ATL/Doc
> M2M/ATL-emfvm => MMT.ATL/emfvm
> M2M/ATL-Engine => MMT.ATL/Engine
> M2M/ATL-UI => MMT.ATL/UI
> M2M/ATL-Website => MMT.ATL/Website
> M2M/QVT_OML-Doc => MMT.QVTo/Doc
> M2M/QVT_OML-Engine => MMT.QVTo/Engine
> M2M/QVT_OML-UI => MMT.QVTo/UI
> M2M/QVT_OML-Website => MMT.QVTo/Website
> M2M/QVT_Relations-Doc => MMT.QVTd/Doc
> M2M/QVT_Relations-Engine => MMT.QVTd/Engine
> M2M/QVT_Relations-Parser=> MMT.QVTd/Parser
> M2M/QVT_Relations-UI => MMT.QVTd/UI
> M2M/QVT_Relations-Website => MMT.QVTd/Website
> M2M/Releng => MMT/Releng
> M2M/Website => MMT/Website
>
> Any objections or better ideas?
>
>     Regards
>
>         Ed Willink
> _______________________________________________
> m2m-dev mailing list
> m2m-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2m-dev
>

_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev

+1
Le 16/04/2012 22:09, Ed Willink a écrit :

Hi
Rather than just move Bugzilla across from M2M to MMT, I suggest we 
also follow the new component naming convention so I propose to 
request the following changes
M2M/ATL-Contribution => MMT.ATL/Contribution
M2M/ATL-Doc => MMT.ATL/Doc
M2M/ATL-emfvm => MMT.ATL/emfvm
M2M/ATL-Engine => MMT.ATL/Engine
M2M/ATL-UI => MMT.ATL/UI
M2M/ATL-Website => MMT.ATL/Website
M2M/QVT_OML-Doc => MMT.QVTo/Doc
M2M/QVT_OML-Engine => MMT.QVTo/Engine
M2M/QVT_OML-UI => MMT.QVTo/UI
M2M/QVT_OML-Website => MMT.QVTo/Website
M2M/QVT_Relations-Doc => MMT.QVTd/Doc
M2M/QVT_Relations-Engine => MMT.QVTd/Engine
M2M/QVT_Relations-Parser=> MMT.QVTd/Parser
M2M/QVT_Relations-UI => MMT.QVTd/UI
M2M/QVT_Relations-Website => MMT.QVTd/Website
M2M/Releng => MMT/Releng
M2M/Website => MMT/Website
Any objections or better ideas?
    Regards
        Ed Willink
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev
begin:vcard
fn:William Piers
n:Piers;William
org:Obeo
email;internet:william.piers@xxxxxxx
title:MDA Consultant
version:2.1
end:vcard

+1
Le 17/04/2012 16:36, Ed Willink a écrit :

Hi
I've raisedhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=376927 to 
migrate m2m-dev to mmt-dev, but unfortunately renaming is not an option.
It has to be a new list with a shutdown message on the old list. 
m2m-dev is a relatively small amount of traffic for hopefully 
intelligent users who can cope.
The same problem will occur on the newsgroup, which is more annoying. 
Do we want to take the opportunity to create per TX engine newsgroups 
since it is slightly confusing getting QVTo and ATL traffic 
intermingled, particularly when users omit a prefix?
eclipse.modeling.mmt
eclipse.modeling.mmt.atl
eclipse.modeling.mmt.qvtd
eclipse.modeling.mmt.qvto
eclipse.modeling.mmt.viatra2 (soon)
    Regards
        Ed Willink
_______________________________________________
m2m-dev mailing list
m2m-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2m-dev
begin:vcard
fn:William Piers
n:Piers;William
org:Obeo
email;internet:william.piers@xxxxxxx
title:MDA Consultant
version:2.1
end:vcard

Hi
I've raisedhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=376927 to 
migrate m2m-dev to mmt-dev, but unfortunately renaming is not an option.
It has to be a new list with a shutdown message on the old list. m2m-dev 
is a relatively small amount of traffic for hopefully intelligent users 
who can cope.
The same problem will occur on the newsgroup, which is more annoying. Do 
we want to take the opportunity to create per TX engine newsgroups since 
it is slightly confusing getting QVTo and ATL traffic intermingled, 
particularly when users omit a prefix?
eclipse.modeling.mmt
eclipse.modeling.mmt.atl
eclipse.modeling.mmt.qvtd
eclipse.modeling.mmt.qvto
eclipse.modeling.mmt.viatra2 (soon)
    Regards
        Ed Willink
Hi
Rather than just move Bugzilla across from M2M to MMT, I suggest we also 
follow the new component naming convention so I propose to request the 
following changes
M2M/ATL-Contribution => MMT.ATL/Contribution
M2M/ATL-Doc => MMT.ATL/Doc
M2M/ATL-emfvm => MMT.ATL/emfvm
M2M/ATL-Engine => MMT.ATL/Engine
M2M/ATL-UI => MMT.ATL/UI
M2M/ATL-Website => MMT.ATL/Website
M2M/QVT_OML-Doc => MMT.QVTo/Doc
M2M/QVT_OML-Engine => MMT.QVTo/Engine
M2M/QVT_OML-UI => MMT.QVTo/UI
M2M/QVT_OML-Website => MMT.QVTo/Website
M2M/QVT_Relations-Doc => MMT.QVTd/Doc
M2M/QVT_Relations-Engine => MMT.QVTd/Engine
M2M/QVT_Relations-Parser=> MMT.QVTd/Parser
M2M/QVT_Relations-UI => MMT.QVTd/UI
M2M/QVT_Relations-Website => MMT.QVTd/Website
M2M/Releng => MMT/Releng
M2M/Website => MMT/Website
Any objections or better ideas?
    Regards
        Ed Willink

m2m-dev

[m2m-dev] m2m-dev is moving to mmt-dev

[m2m-dev] UML Standalone Initialization

Re: [m2m-dev] M2M to MMT Bugzilla migration

Re: [m2m-dev] M2M to MMT Bugzilla migration

Re: [m2m-dev] M2M to MMT Bugzilla migration

Re: [m2m-dev] M2M to MMT Bugzilla migration

Re: [m2m-dev] M2M to MMT Bugzilla migration

Re: [m2m-dev] Mailing list migration from M2M to MMT

[m2m-dev] Mailing list migration from M2M to MMT

[m2m-dev] M2M to MMT Bugzilla migration