Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » AMP » Target Platforms Extensions and Eclipse compatibility issues
Target Platforms Extensions and Eclipse compatibility issues [message #1113129] Fri, 20 September 2013 13:32 Go to next message
Francesco Farina is currently offline Francesco Farina
Messages: 1
Registered: September 2013
Junior Member
Dear Miles Parker,

I'm working on AMP for Academic purpose, looking whether it would be possible to add MASON as a target platform for AMP.

I would like to ask some questions:

- Could you give me some advices on how to start and where to look. Moreover, has this feature (MASON as a target platform) already been developed? Considered? Would it be possible?

- The second question is about the AMP compatibility with Eclipse's releases.
I was able to let it work with Indigo but I had some problem with other releases. I've noticed your commit (Update to use Juno p2), and tried to follow the build from the source guide but I had some problems, for example:
"No suitable provider for component org.eclipse.amp.releng:Buckminster was found in resourceMap
file:/C:/Users/frafar/workspaceJuno/org.eclipse.amp.git/releng/org.eclipse.amp.releng/releng/amp.rmap".
Could I get AMP working with Eclipse Juno or later?

Regards,
Francesco Farina
Re: Target Platforms Extensions and Eclipse compatibility issues [message #1113231 is a reply to message #1113129] Fri, 20 September 2013 16:57 Go to previous message
Miles Parker is currently offline Miles Parker
Messages: 1322
Registered: July 2009
Senior Member
Francesco Farina wrote on Fri, 20 September 2013 13:32
Dear Miles Parker,

I'm working on AMP for Academic purpose, looking whether it would be possible to add MASON as a target platform for AMP.

I would like to ask some questions:

- Could you give me some advices on how to start and where to look. Moreover, has this feature (MASON as a target platform) already been developed? Considered? Would it be possible?


Glad you're interested! I would look at all of the stuff in the amf gen projects:

org.eclipse.amp.amf.gen

org.eclipse.amp.amf.gen.ascape
org.eclipse.amp.amf.gen.escape

Basically, the idea would be to create a

org.eclipse.amp.amf.gen.mason

Specializing the templates based on for example:

org.eclipse.amp.amf.gen.ascape/src/metaabm/ascape/tmpl/*

Quote:
- The second question is about the AMP compatibility with Eclipse's releases.
I was able to let it work with Indigo but I had some problem with other releases. I've noticed your commit (Update to use Juno p2), and tried to follow the build from the source guide but I had some problems, for example:
"No suitable provider for component org.eclipse.amp.releng:Buckminster was found in resourceMap
file:/C:/Users/frafar/workspaceJuno/org.eclipse.amp.git/releng/org.eclipse.amp.releng/releng/amp.rmap".
Could I get AMP working with Eclipse Juno or later?


Oh, that's ironic. I think buckminster is saying that it can't find itself. Smile Sigh.

Actually, it isn't too hard to deal with the dependencies manually. I'd suggest installing all of the dependencies manually. You can see the various update sites in amp-platform.cspec.

My only concern would be w/ xpand. We're using an elder version of that (not the new xtend support) so you need to be sure to get the appropriate version.

It should run fine under Juno, but I can't voich for Kepler+..


Previous Topic:Keybinding conflicts ALT+SHIFT+L
Goto Forum:
  


Current Time: Mon Oct 07 06:38:39 EDT 2013

Powered by FUDForum. Page generated in 0.02251 seconds