Eclipse Community Forums: M2T (model-to-text transformation)

Home » Modeling » M2T (model-to-text transformation) » MWE(Resource and platform behaviour)

Wed, 17 February 2010 04:08

Eclipse User

Hi,

I am not exactly sure this is the correct forum but I don't see any dedicated place for MWE subjects...

I am using the fornax maven plugin to run the MWE workflows and I am having problems with platform;:/resource uri if I am building a hierarchical project structure with Maven instead of flat projects...

If Ib uild everything flat, platform uri's are working correctly with platformUri=".." configuration but if I configure the projects hierharchically it complains that there is no mapping for the projects...

so flat project from Maven look like this, if I start the build from projectA it is able to resolve projectB with following uri platform:/resouce/projectB/...

projectA
projectB
projectC

in the hierarchical project, if I start the build from projectA the previous uri naturally doesn't function platform:/resouce/projectB/... but unfortunately platformUri is like projectA/projectA setted so platform:/resouce/projectA/projectB/... doesn't function also..

projectA
+-----projectB
+-----projectC

So the question for me, I now that eclipse favors flat structures so that mean I have no chance with the hierarchical structure or this is just bug....

PS. I also tried platformUri="." that doesn't function

Re: MWE [message #515198 is a reply to message #514931]

Thu, 18 February 2010 01:59

Eclipse User

Hi,

salgarm@gmx.de schrieb:
> I am not exactly sure this is the correct forum but I don't see any
> dedicated place for MWE subjects...

The right place to ask MWE questions would be the emft newsgroup (MWE is
part of EMFT).

> I am using the fornax maven plugin to run the MWE workflows and I am
> having problems with platform;:/resource uri if I am building a
> hierarchical project structure with Maven instead of flat projects...
>
> If Ib uild everything flat, platform uri's are working correctly with
> platformUri=".." configuration but if I configure the projects
> hierharchically it complains that there is no mapping for the projects...

I org.eclipse.emf.mwe.utils.StandaloneSetup.setPlatformUri(Str ing) we
just iterate over the contents of the specified folder (ie '..') and add
an entry to the platform resource map for each contained folder.

> so flat project from Maven look like this, if I start the build from
> projectA it is able to resolve projectB with following uri
> platform:/resouce/projectB/...
>
> projectA
> projectB
> projectC
>
> in the hierarchical project, if I start the build from projectA the
> previous uri naturally doesn't function platform:/resouce/projectB/...
> but unfortunately platformUri is like projectA/projectA setted so
> platform:/resouce/projectA/projectB/... doesn't function also..

Are you saying that platform:/resource/projectA works, while
platform:/resource/projectA/projectB doesn't work.
Although projectB physically resides within projectA?

Sven

--
Need professional support for Xtext and EMF?
Go to: http://xtext.itemis.com
Twitter : @svenefftinge
Blog : blog.efftinge.de

Re: MWE [message #515204 is a reply to message #515198]

Thu, 18 February 2010 02:44

Eclipse User

Exactly,

In the hierarchical structure projectA contains the projectB but as platformUri '/projectA/projectA' which naturally not true that is what I am seeing from log output...

I tried all possible versions of platformUri="..", platformUri=".", platformUri="../.", platformUri="../.." all to no avail...

Btw, thx for the tip, I would create the thread also in EMFT forums...

Previous Topic:	Any way to generate only one file?
Next Topic:	[Acceleo] Generators interface ?

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 11:40:31 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter