| Workspace aware epackage registry available for download? [message #62930] |
Thu, 23 July 2009 10:46  |
Eclipse User |
|
|
|
Hi,
I'm working on multiple grammars which reference each other. I want to
setup a single workspace to edit the grammars. I then use a runtime
workspace to create xtend and xpand files (required to register the meta
models).
In the primary eclipse workspace I get errors in the grammars which
contain model imports. Those models are unregistered as they are created
right in this workspace. Therefore I need something like the workspace
aware registry, describe here:
http://apps.itemis.de/roller/itemislabkiel/entry/workspace_a ware_epackage_regist
Is this registry available for download somewhere?
I've played around with the different naming scheme for grammar imports
(like "classpath:/", "platform:/resource"). I ended up using the namespace
URI scheme.
Regards
Christoph
|
|
|
| Re: Workspace aware epackage registry available for download? [message #62941 is a reply to message #62930] |
Thu, 23 July 2009 12:51  |
| Eclipse User |
|
|
|
Hi Christoph,
I'm afraid there is no such thing as a Workspace Aware Registry, but
maybe I'm wrong.
Why can't you use platform:/resource uris instead of nsUris? They should
work fine in your scenario of different languages that refer other
abstract syntaxes (meta models).
However, you should not try to use only one workflow to generate all
languages but use different workflows and use the StandaloneSetup in the
workflow to register the generated, referenced packages.
Hope that helps,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 23.07.2009 16:46 Uhr, schrieb Christoph Kulla:
> Hi,
>
> I'm working on multiple grammars which reference each other. I want to
> setup a single workspace to edit the grammars. I then use a runtime
> workspace to create xtend and xpand files (required to register the meta
> models).
>
> In the primary eclipse workspace I get errors in the grammars which
> contain model imports. Those models are unregistered as they are created
> right in this workspace. Therefore I need something like the workspace
> aware registry, describe here:
>
> http://apps.itemis.de/roller/itemislabkiel/entry/workspace_a ware_epackage_regist
>
>
> Is this registry available for download somewhere?
>
> I've played around with the different naming scheme for grammar imports
> (like "classpath:/", "platform:/resource"). I ended up using the
> namespace URI scheme.
>
> Regards
>
> Christoph
>
|
|
|
|
| Re: Workspace aware epackage registry available for download? [message #62980 is a reply to message #62964] |
Fri, 24 July 2009 08:15 |
| Eclipse User |
|
|
|
Hi Christoph,
this is a bug in Xpand. Generally speaking, EMF will transparently
convert platform:/resource to platform:/plugin uris in a runtime
workspace. To get this behaviour, you have to initialize the uri mapping
properly for the resource set, that you are working with. Xpand internal
analyzer did not do this, but it was a one liner to fix it.
It will make it into CVS after a code review.
Thanks for your detailled steps to reproduce this bug.
Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 24.07.2009 11:12 Uhr, schrieb Christoph Kulla:
> Hi Sebastian,
>
> I've also tried the "platform:/resource" URIs. The problems start when
> you are working in a runtime eclipse or export the plugins to another
> eclipse.
>
> My setup is like:
>
> Primary Eclipse:
>
> Grammar A Grammar B with cross references to A (A is referenced by
> platform:/resource/.../A.ecore URI)
>
> Start Eclipse runtime from primary eclipse
>
> Create a new project. Create a xtend file. Import B and try to reference
> cross references to A in the xtend file. This results in error markers.
> This can be avoidd using nsURIs, but then you get the error markers in
> the primary eclipse installation :(. What I trying to achieve is an
> error free setup in both eclipse installations.
>
> Regards
>
> Christoph
>
>
>
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.06908 seconds
Home