Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » GMT (Generative Modeling Technologies) » [AM3]Strange situations
[AM3]Strange situations [message #380849] Thu, 10 January 2008 11:49 Go to next message
Eclipse User
Originally posted by: zappasan.gmail.com

Hi.
I'm tring to install Am3 from the cvs repository, but I've this problem:
in the org.eclipse.gmt.am3.gmm4atl.ui plugin there are a lot of references
to a getRootMegaModel() method. This method is into the
org.eclipse.gmt.am3.platform.core plugin. The problem is that this method
is declared private and when I try to export all the am3 plugins I've a
lot errors about a reference to a private method.
The first thing I've thinked for solve this problem is changing the method
declaration from private to public, but I'm not so sure that this the
right solution, because I've experienced it and when I open the Megamodel
perspective I've no actions about Entity, Relationship, etc. in the
context menu. More, I've no menu about creating Megamodel, or add resource
to a metamodel, etc. In conclusion, I can't think that changing the
declaration is the right solution.
Anyone has experienced this situation? Anyone has some advice for
overcoming this problem.

Thanks to all.

Emanuele
Re: [AM3]Strange situations [message #380851 is a reply to message #380849] Fri, 11 January 2008 10:10 Go to previous messageGo to next message
Hugo Bruneliere is currently offline Hugo Bruneliere
Messages: 588
Registered: July 2009
Senior Member
Hi Emanuele,

Emanuele Zapparoli a écrit :
> Hi.
> I'm tring to install Am3 from the cvs repository, but I've this problem:
> in the org.eclipse.gmt.am3.gmm4atl.ui plugin there are a lot of
> references to a getRootMegaModel() method. This method is into the
> org.eclipse.gmt.am3.platform.core plugin. The problem is that this
> method is declared private and when I try to export all the am3 plugins
> I've a lot errors about a reference to a private method. The first thing
> I've thinked for solve this problem is changing the method declaration
> from private to public, but I'm not so sure that this the right
> solution, because I've experienced it and when I open the Megamodel
> perspective I've no actions about Entity, Relationship, etc. in the
> context menu. More, I've no menu about creating Megamodel, or add
> resource to a metamodel, etc. In conclusion, I can't think that changing
> the declaration is the right solution.
> Anyone has experienced this situation? Anyone has some advice for
> overcoming this problem.
>

The plugins which are located in the "plugins" folder implement a new
prototype which will be the future version of AM3 but which is currently
still in development. This new prototype is completely independent from
the "old" AM3 (i.e. the plugins located at the root of the AM3
repository location).

The "old" AM3 plugins (providing the "AM3 Perspective" including the
"AM3 Resource Navigator") are still available as they are very useful
when developing with ATL.

However, we are very interesting in people who want to test the new AM3
prototype (a first documentation on it will be available in the coming
weeks) and on getting feedback on these first experiments. For
information, the new "Megamodel Navigator" view is available in the
MegaModel view category.

We are sorry for the confusion we involuntarily introduce here. We plan
to start to really communicate on this new prototype in the coming weeks.

> Thanks to all.
>
> Emanuele
>
>

Best regards,

Hugo

--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------


------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (Inria, EMN & LINA)
Ecole des Mines de Nantes
Nantes - France
------------------------------------------
Re: [AM3]Strange situations [message #380855 is a reply to message #380851] Tue, 15 January 2008 12:06 Go to previous messageGo to next message
Eclipse User
Originally posted by: zappasan.gmail.com

Hi Hugo.
Sorry for my delayed reply, but Im'm very busy in this period.

Hugo Bruneliere wrote:

> The plugins which are located in the "plugins" folder implement a new
> prototype which will be the future version of AM3 but which is currently
> still in development. This new prototype is completely independent from
> the "old" AM3 (i.e. the plugins located at the root of the AM3
> repository location).

> The "old" AM3 plugins (providing the "AM3 Perspective" including the
> "AM3 Resource Navigator") are still available as they are very useful
> when developing with ATL.


Ok I understand the situation.

> However, we are very interesting in people who want to test the new AM3
> prototype (a first documentation on it will be available in the coming
> weeks) and on getting feedback on these first experiments. For
> information, the new "Megamodel Navigator" view is available in the
> MegaModel view category.

I've fixed the error changing the visibility of the method that has given
me the errors. I've changed from private to public. Anyway, when a I start
the Megamodel perspective, after exporting all the am3 plugins, I've a
strange Megamodel view with 3 issues only (Entyty, Relationship, Chain)
organized like a tree. When I click on one of this issues I have no
contextual menu.
But if I run the org.eclipse.gmt.am3 like an Eclipse's application, AM3
works and I can open all the node of the tree (and I can see nodes like
Megamodel, Terminal Model, etc.) and every contextual menu of every leaf
works. I don't know why this not happens when I run am3 like an integreted
plug-in.

> We are sorry for the confusion we involuntarily introduce here. We plan
> to start to really communicate on this new prototype in the coming weeks.

No problem. Anyeway, thank you for your help.

Emanuele
Re: [AM3]Strange situations [message #380857 is a reply to message #380855] Tue, 15 January 2008 12:42 Go to previous messageGo to next message
Hugo Bruneliere is currently offline Hugo Bruneliere
Messages: 588
Registered: July 2009
Senior Member
Hi Emanuele,

Emanuele Zapparoli a écrit :
> Hi Hugo.
> Sorry for my delayed reply, but Im'm very busy in this period.
>
> Hugo Bruneliere wrote:
>
>> The plugins which are located in the "plugins" folder implement a new
>> prototype which will be the future version of AM3 but which is
>> currently still in development. This new prototype is completely
>> independent from the "old" AM3 (i.e. the plugins located at the root
>> of the AM3 repository location).
>
>> The "old" AM3 plugins (providing the "AM3 Perspective" including the
>> "AM3 Resource Navigator") are still available as they are very useful
>> when developing with ATL.
>
>
> Ok I understand the situation.
>> However, we are very interesting in people who want to test the new
>> AM3 prototype (a first documentation on it will be available in the
>> coming weeks) and on getting feedback on these first experiments. For
>> information, the new "Megamodel Navigator" view is available in the
>> MegaModel view category.
>
> I've fixed the error changing the visibility of the method that has
> given me the errors. I've changed from private to public. Anyway, when a
> I start the Megamodel perspective, after exporting all the am3 plugins,
> I've a strange Megamodel view with 3 issues only (Entyty, Relationship,
> Chain) organized like a tree. When I click on one of this issues I have
> no contextual menu. But if I run the org.eclipse.gmt.am3 like an
> Eclipse's application, AM3 works and I can open all the node of the tree
> (and I can see nodes like Megamodel, Terminal Model, etc.) and every
> contextual menu of every leaf works. I don't know why this not happens
> when I run am3 like an integreted plug-in.

About the encountered errors, I recently updated the "gmm4atl" plugins
(because some methods had been modified in the "plaform.core" plugin).
If you checkout these plugins latest version, it should solve your
problem without having to modify the code by yourself.

Regarding your second problem, we have never encountered this before. We
will try to see if we can find an explanation.

>> We are sorry for the confusion we involuntarily introduce here. We
>> plan to start to really communicate on this new prototype in the
>> coming weeks.
>
> No problem. Anyeway, thank you for your help.
>
> Emanuele
>
>
>

Best regards,

Hugo

--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------


------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (Inria, EMN & LINA)
Ecole des Mines de Nantes
Nantes - France
------------------------------------------
Re: [AM3]Strange situations [message #381203 is a reply to message #380857] Wed, 16 January 2008 09:46 Go to previous messageGo to next message
user is currently offline user
Messages: 296
Registered: July 2009
Senior Member
Hi Emanuele,

Thanks for your report, the future version of AM3 is currently under
development, as Hugo mentioned.

I recently fixed the build of AM3 plugins, so now you can export them.

Regards,
--
Brahim Khalil LOUKIL,
ATLAS Group (INRIA & LINA)
Eclipse Committer : GMT Project
Sourceforge.net Contributor : OWL VE project
http://brlouk2008.teamsoftsuite.com


Hugo Bruneliere a écrit :
> Hi Emanuele,
>
> Emanuele Zapparoli a écrit :
>> Hi Hugo.
>> Sorry for my delayed reply, but Im'm very busy in this period.
>>
>> Hugo Bruneliere wrote:
>>
>>> The plugins which are located in the "plugins" folder implement a new
>>> prototype which will be the future version of AM3 but which is
>>> currently still in development. This new prototype is completely
>>> independent from the "old" AM3 (i.e. the plugins located at the root
>>> of the AM3 repository location).
>>
>>> The "old" AM3 plugins (providing the "AM3 Perspective" including the
>>> "AM3 Resource Navigator") are still available as they are very useful
>>> when developing with ATL.
>>
>>
>> Ok I understand the situation.
>>> However, we are very interesting in people who want to test the new
>>> AM3 prototype (a first documentation on it will be available in the
>>> coming weeks) and on getting feedback on these first experiments. For
>>> information, the new "Megamodel Navigator" view is available in the
>>> MegaModel view category.
>>
>> I've fixed the error changing the visibility of the method that has
>> given me the errors. I've changed from private to public. Anyway, when
>> a I start the Megamodel perspective, after exporting all the am3
>> plugins, I've a strange Megamodel view with 3 issues only (Entyty,
>> Relationship, Chain) organized like a tree. When I click on one of
>> this issues I have no contextual menu. But if I run the
>> org.eclipse.gmt.am3 like an Eclipse's application, AM3 works and I can
>> open all the node of the tree (and I can see nodes like Megamodel,
>> Terminal Model, etc.) and every contextual menu of every leaf works. I
>> don't know why this not happens when I run am3 like an integreted
>> plug-in.
>
> About the encountered errors, I recently updated the "gmm4atl" plugins
> (because some methods had been modified in the "plaform.core" plugin).
> If you checkout these plugins latest version, it should solve your
> problem without having to modify the code by yourself.
>
> Regarding your second problem, we have never encountered this before. We
> will try to see if we can find an explanation.
>
>>> We are sorry for the confusion we involuntarily introduce here. We
>>> plan to start to really communicate on this new prototype in the
>>> coming weeks.
>>
>> No problem. Anyeway, thank you for your help.
>>
>> Emanuele
>>
>>
>>
>
> Best regards,
>
> Hugo
>
Re: [AM3]Strange situations [message #381206 is a reply to message #381203] Wed, 16 January 2008 11:30 Go to previous message
Eclipse User
Originally posted by: zappasan.gmail.com

Hi Brahim.
Now the Megamodel perspective works fine. What about the problem that you
have fixed? Is it concerned with some configuration file?
Anyway, I will say thank you to Hugo and Brahim for their help.

Emanuele
Re: [AM3]Strange situations [message #611168 is a reply to message #380849] Fri, 11 January 2008 10:10 Go to previous message
Hugo Bruneliere is currently offline Hugo Bruneliere
Messages: 588
Registered: July 2009
Senior Member
Hi Emanuele,

Emanuele Zapparoli a écrit :
> Hi.
> I'm tring to install Am3 from the cvs repository, but I've this problem:
> in the org.eclipse.gmt.am3.gmm4atl.ui plugin there are a lot of
> references to a getRootMegaModel() method. This method is into the
> org.eclipse.gmt.am3.platform.core plugin. The problem is that this
> method is declared private and when I try to export all the am3 plugins
> I've a lot errors about a reference to a private method. The first thing
> I've thinked for solve this problem is changing the method declaration
> from private to public, but I'm not so sure that this the right
> solution, because I've experienced it and when I open the Megamodel
> perspective I've no actions about Entity, Relationship, etc. in the
> context menu. More, I've no menu about creating Megamodel, or add
> resource to a metamodel, etc. In conclusion, I can't think that changing
> the declaration is the right solution.
> Anyone has experienced this situation? Anyone has some advice for
> overcoming this problem.
>

The plugins which are located in the "plugins" folder implement a new
prototype which will be the future version of AM3 but which is currently
still in development. This new prototype is completely independent from
the "old" AM3 (i.e. the plugins located at the root of the AM3
repository location).

The "old" AM3 plugins (providing the "AM3 Perspective" including the
"AM3 Resource Navigator") are still available as they are very useful
when developing with ATL.

However, we are very interesting in people who want to test the new AM3
prototype (a first documentation on it will be available in the coming
weeks) and on getting feedback on these first experiments. For
information, the new "Megamodel Navigator" view is available in the
MegaModel view category.

We are sorry for the confusion we involuntarily introduce here. We plan
to start to really communicate on this new prototype in the coming weeks.

> Thanks to all.
>
> Emanuele
>
>

Best regards,

Hugo

--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------


------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (Inria, EMN & LINA)
Ecole des Mines de Nantes
Nantes - France
------------------------------------------
Re: [AM3]Strange situations [message #611172 is a reply to message #380851] Tue, 15 January 2008 12:06 Go to previous message
Eclipse User
Originally posted by: zappasan.gmail.com

Hi Hugo.
Sorry for my delayed reply, but Im'm very busy in this period.

Hugo Bruneliere wrote:

> The plugins which are located in the "plugins" folder implement a new
> prototype which will be the future version of AM3 but which is currently
> still in development. This new prototype is completely independent from
> the "old" AM3 (i.e. the plugins located at the root of the AM3
> repository location).

> The "old" AM3 plugins (providing the "AM3 Perspective" including the
> "AM3 Resource Navigator") are still available as they are very useful
> when developing with ATL.


Ok I understand the situation.

> However, we are very interesting in people who want to test the new AM3
> prototype (a first documentation on it will be available in the coming
> weeks) and on getting feedback on these first experiments. For
> information, the new "Megamodel Navigator" view is available in the
> MegaModel view category.

I've fixed the error changing the visibility of the method that has given
me the errors. I've changed from private to public. Anyway, when a I start
the Megamodel perspective, after exporting all the am3 plugins, I've a
strange Megamodel view with 3 issues only (Entyty, Relationship, Chain)
organized like a tree. When I click on one of this issues I have no
contextual menu.
But if I run the org.eclipse.gmt.am3 like an Eclipse's application, AM3
works and I can open all the node of the tree (and I can see nodes like
Megamodel, Terminal Model, etc.) and every contextual menu of every leaf
works. I don't know why this not happens when I run am3 like an integreted
plug-in.

> We are sorry for the confusion we involuntarily introduce here. We plan
> to start to really communicate on this new prototype in the coming weeks.

No problem. Anyeway, thank you for your help.

Emanuele
Re: [AM3]Strange situations [message #611174 is a reply to message #380855] Tue, 15 January 2008 12:42 Go to previous message
Hugo Bruneliere is currently offline Hugo Bruneliere
Messages: 588
Registered: July 2009
Senior Member
Hi Emanuele,

Emanuele Zapparoli a écrit :
> Hi Hugo.
> Sorry for my delayed reply, but Im'm very busy in this period.
>
> Hugo Bruneliere wrote:
>
>> The plugins which are located in the "plugins" folder implement a new
>> prototype which will be the future version of AM3 but which is
>> currently still in development. This new prototype is completely
>> independent from the "old" AM3 (i.e. the plugins located at the root
>> of the AM3 repository location).
>
>> The "old" AM3 plugins (providing the "AM3 Perspective" including the
>> "AM3 Resource Navigator") are still available as they are very useful
>> when developing with ATL.
>
>
> Ok I understand the situation.
>> However, we are very interesting in people who want to test the new
>> AM3 prototype (a first documentation on it will be available in the
>> coming weeks) and on getting feedback on these first experiments. For
>> information, the new "Megamodel Navigator" view is available in the
>> MegaModel view category.
>
> I've fixed the error changing the visibility of the method that has
> given me the errors. I've changed from private to public. Anyway, when a
> I start the Megamodel perspective, after exporting all the am3 plugins,
> I've a strange Megamodel view with 3 issues only (Entyty, Relationship,
> Chain) organized like a tree. When I click on one of this issues I have
> no contextual menu. But if I run the org.eclipse.gmt.am3 like an
> Eclipse's application, AM3 works and I can open all the node of the tree
> (and I can see nodes like Megamodel, Terminal Model, etc.) and every
> contextual menu of every leaf works. I don't know why this not happens
> when I run am3 like an integreted plug-in.

About the encountered errors, I recently updated the "gmm4atl" plugins
(because some methods had been modified in the "plaform.core" plugin).
If you checkout these plugins latest version, it should solve your
problem without having to modify the code by yourself.

Regarding your second problem, we have never encountered this before. We
will try to see if we can find an explanation.

>> We are sorry for the confusion we involuntarily introduce here. We
>> plan to start to really communicate on this new prototype in the
>> coming weeks.
>
> No problem. Anyeway, thank you for your help.
>
> Emanuele
>
>
>

Best regards,

Hugo

--
--------------------------------------------------------
Hugo Bruneliere - R&D Engineer
ATLAS Group (INRIA & LINA) - University of Nantes
2, rue de la Houssiniere
44322 Nantes Cedex 3 - France
office +33 2 51 12 58 10 /\ cell.+33 6 07 42 45 30
EMail: Hugo.Bruneliere@univ-nantes.fr
http://www.sciences.univ-nantes.fr/lina/atl/
--------------------------------------------------------


------------------------------------------
Hugo Bruneliere - R&D Engineer
AtlanMod research team (Inria, EMN & LINA)
Ecole des Mines de Nantes
Nantes - France
------------------------------------------
Re: [AM3]Strange situations [message #611177 is a reply to message #380857] Wed, 16 January 2008 09:46 Go to previous message
user is currently offline user
Messages: 296
Registered: July 2009
Senior Member
Hi Emanuele,

Thanks for your report, the future version of AM3 is currently under
development, as Hugo mentioned.

I recently fixed the build of AM3 plugins, so now you can export them.

Regards,
--
Brahim Khalil LOUKIL,
ATLAS Group (INRIA & LINA)
Eclipse Committer : GMT Project
Sourceforge.net Contributor : OWL VE project
http://brlouk2008.teamsoftsuite.com


Hugo Bruneliere a écrit :
> Hi Emanuele,
>
> Emanuele Zapparoli a écrit :
>> Hi Hugo.
>> Sorry for my delayed reply, but Im'm very busy in this period.
>>
>> Hugo Bruneliere wrote:
>>
>>> The plugins which are located in the "plugins" folder implement a new
>>> prototype which will be the future version of AM3 but which is
>>> currently still in development. This new prototype is completely
>>> independent from the "old" AM3 (i.e. the plugins located at the root
>>> of the AM3 repository location).
>>
>>> The "old" AM3 plugins (providing the "AM3 Perspective" including the
>>> "AM3 Resource Navigator") are still available as they are very useful
>>> when developing with ATL.
>>
>>
>> Ok I understand the situation.
>>> However, we are very interesting in people who want to test the new
>>> AM3 prototype (a first documentation on it will be available in the
>>> coming weeks) and on getting feedback on these first experiments. For
>>> information, the new "Megamodel Navigator" view is available in the
>>> MegaModel view category.
>>
>> I've fixed the error changing the visibility of the method that has
>> given me the errors. I've changed from private to public. Anyway, when
>> a I start the Megamodel perspective, after exporting all the am3
>> plugins, I've a strange Megamodel view with 3 issues only (Entyty,
>> Relationship, Chain) organized like a tree. When I click on one of
>> this issues I have no contextual menu. But if I run the
>> org.eclipse.gmt.am3 like an Eclipse's application, AM3 works and I can
>> open all the node of the tree (and I can see nodes like Megamodel,
>> Terminal Model, etc.) and every contextual menu of every leaf works. I
>> don't know why this not happens when I run am3 like an integreted
>> plug-in.
>
> About the encountered errors, I recently updated the "gmm4atl" plugins
> (because some methods had been modified in the "plaform.core" plugin).
> If you checkout these plugins latest version, it should solve your
> problem without having to modify the code by yourself.
>
> Regarding your second problem, we have never encountered this before. We
> will try to see if we can find an explanation.
>
>>> We are sorry for the confusion we involuntarily introduce here. We
>>> plan to start to really communicate on this new prototype in the
>>> coming weeks.
>>
>> No problem. Anyeway, thank you for your help.
>>
>> Emanuele
>>
>>
>>
>
> Best regards,
>
> Hugo
>
Re: [AM3]Strange situations [message #611178 is a reply to message #381203] Wed, 16 January 2008 11:30 Go to previous message
Eclipse User
Originally posted by: zappasan.gmail.com

Hi Brahim.
Now the Megamodel perspective works fine. What about the problem that you
have fixed? Is it concerned with some configuration file?
Anyway, I will say thank you to Hugo and Brahim for their help.

Emanuele
Previous Topic:am3 ant tasks outside eclipse workspace
Next Topic:[AM3] About using am3
Goto Forum:
  


Current Time: Mon Apr 21 08:49:24 EDT 2014

Powered by FUDForum. Page generated in 0.02222 seconds