Eclipse Community Forums: TMF (Xtext) » Packages should be imported by their namespace URI.

Help

Home

Home » Modeling » TMF (Xtext) » Packages should be imported by their namespace URI.

Show: Today's Messages :: Show Polls :: Message Navigator

Packages should be imported by their namespace URI. [message #900370]

Mon, 06 August 2012 17:08

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

Pending a response to https://bugs.eclipse.org/bugs/show_bug.cgi?id=366476;

How does an Xtext grammar distinguish between the following scenarios?

a) the imported *.ecore is a concurrent development and so the
platform:/resource rather than platform:/plugin variant should be used.

b) the imported *.ecore is a stable reference and so the
platform:/plugin or http:/... variant should be used.

In Xtext 2.1 it was possible to use

import "platform:/resource/..."

This is still possible in 2.3, but it causes unwanted warnings.

Regards

Ed Willink

Report message to a moderator

Re: Packages should be imported by their namespace URI. [message #960233 is a reply to message #900370]

Sat, 27 October 2012 09:38

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

Ping. What is the warning-free way in which to import an Ecore model
into Xtext so that the Ecore model is resolved to the *.ecore file (or
Java classes) in an active workspace project rather than those in an
installed plugin?

Regards

Ed Willink

On 06/08/2012 19:08, Ed Willink wrote:
> Hi
>
> Pending a response to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=366476;
>
> How does an Xtext grammar distinguish between the following scenarios?
>
> a) the imported *.ecore is a concurrent development and so the
> platform:/resource rather than platform:/plugin variant should be used.
>
> b) the imported *.ecore is a stable reference and so the
> platform:/plugin or http:/... variant should be used.
>
> In Xtext 2.1 it was possible to use
>
> import "platform:/resource/..."
>
> This is still possible in 2.3, but it causes unwanted warnings.
>
> Regards
>
> Ed Willink
>

Report message to a moderator

Re: Packages should be imported by their namespace URI. [message #960499 is a reply to message #960233]

Sat, 27 October 2012 14:44

Sebastian Zarnekow

Messages: 3118
Registered: July 2009

Senior Member

The EPackages are looked up in the index by their nsURI. Therefore you
should always use that one. Things from the workspace are preferred over
packages from the target platform which are in turn preferred over
installed packages from the workbench.

Hope that helps,
Sebastian
--
Looking for professional support for Xtext, Xtend or Eclipse Modeling?
Go visit: http://xtext.itemis.com

Am 27.10.12 11:38, schrieb Ed Willink:
> Hi
>
> Ping. What is the warning-free way in which to import an Ecore model
> into Xtext so that the Ecore model is resolved to the *.ecore file (or
> Java classes) in an active workspace project rather than those in an
> installed plugin?
>
> Regards
>
> Ed Willink
>
>
> On 06/08/2012 19:08, Ed Willink wrote:
>> Hi
>>
>> Pending a response to
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=366476;
>>
>> How does an Xtext grammar distinguish between the following scenarios?
>>
>> a) the imported *.ecore is a concurrent development and so the
>> platform:/resource rather than platform:/plugin variant should be used.
>>
>> b) the imported *.ecore is a stable reference and so the
>> platform:/plugin or http:/... variant should be used.
>>
>> In Xtext 2.1 it was possible to use
>>
>> import "platform:/resource/..."
>>
>> This is still possible in 2.3, but it causes unwanted warnings.
>>
>> Regards
>>
>> Ed Willink
>>
>

Report message to a moderator

Re: Packages should be imported by their namespace URI. [message #960813 is a reply to message #960499]

Sat, 27 October 2012 20:46

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi Sebastian

Ah! That index. That explains somethings, but

a) why do I have to use an index when in Xtext 2.0, I could specify what
I want explicitly? (no need to have index building wasting my CPU cycles
every time EGIT wakes up.)

b) why do I have to add the Xtext nature to my model plugins, just to be
able to reference them via an index?

c) it doesn't work when A.xtext references B.ecore, which references
C.ecore, each in different plugins because
- C.ecore must be imported by nsURI from A.xtext to suit Xtext indexing
- C.ecore must be referenced by relative path from B.ecore to suit Ecore
referencing
This causes Xtext to fail with an unhelpfully conflicting model element
diagnostic. So I still get warnings, though not quite as many as when
using import 'platform:/resource/...' in conventional EMF (and Xtext
2.0) style.

Regards

Ed Willink

On 27/10/2012 15:44, Sebastian Zarnekow wrote:
> The EPackages are looked up in the index by their nsURI. Therefore you
> should always use that one. Things from the workspace are preferred
> over packages from the target platform which are in turn preferred
> over installed packages from the workbench.
>
> Hope that helps,
> Sebastian

Report message to a moderator

Re: Packages should be imported by their namespace URI. [message #961276 is a reply to message #960813]

Sun, 28 October 2012 05:55

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Ed, 
 
Comments below. 
 
<div class="moz-cite-prefix">On 27/10/2012 10:46 PM, Ed Willink
wrote: 
</div>
<blockquote cite="mid:k6hh84$dm5$1@xxxxxxxxe.org" type="cite">Hi
Sebastian
 
 
Ah! That index. That explains somethings, but
 
 
a) why do I have to use an index when in Xtext 2.0, I could
specify what I want explicitly? (no need to have index building
wasting my CPU cycles every time EGIT wakes up.)
 
</blockquote>
Because the grammars themselves depend on the index for importing
other grammars. 
<blockquote cite="mid:k6hh84$dm5$1@xxxxxxxxe.org" type="cite">
 
b) why do I have to add the Xtext nature to my model plugins, just
to be able to reference them via an index?
 
</blockquote>
Because projects in the workspace are indexed only if they have an
Xtext nature to save those CPU cycles if you don't want your project
indexed. 
<blockquote cite="mid:k6hh84$dm5$1@xxxxxxxxe.org" type="cite">
 
c) it doesn't work when A.xtext references B.ecore, which
references C.ecore, each in different plugins because
 
- C.ecore must be imported by nsURI from A.xtext to suit Xtext
indexing
 
- C.ecore must be referenced by relative path from B.ecore to suit
Ecore referencing
 
</blockquote>
I'm hopeful that between fixing these two bugs (the first committed
yesterday and the second pending review of the Xtext team) this
problem will be fully addressed. 
<blockquote><a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=220218">https://bugs.eclipse.org/bugs/show_bug.cgi?id=220218</a> 
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=390411">https://bugs.eclipse.org/bugs/show_bug.cgi?id=390411</a> 
</blockquote>
 
<blockquote cite="mid:k6hh84$dm5$1@xxxxxxxxe.org" type="cite">This
causes Xtext to fail with an unhelpfully conflicting model element
diagnostic. So I still get warnings, though not quite as many as
when using import 'platform:/resource/...' in conventional EMF
(and Xtext 2.0) style.
 
</blockquote>
I'd suggest making a small example along with the steps to reproduce
them so we can make sure that this problem disappears with the above
two issues addressed.  I imagine it should be the case that either
platform:/resource or nsURI should work properly (because with the
first bugzilla addressed, the EMF models for all target platform
bundles will be visible as platform:/resource/<bundle-id>,
even the ones that aren't really physically in the workspace)... 
<blockquote cite="mid:k6hh84$dm5$1@xxxxxxxxe.org" type="cite">
 
    Regards
 
 
        Ed Willink
 
 
On 27/10/2012 15:44, Sebastian Zarnekow wrote:
 
<blockquote type="cite">The EPackages are looked up in the index
by their nsURI. Therefore you should always use that one. Things
from the workspace are preferred over packages from the target
platform which are in turn preferred over installed packages
from the workbench.
 
 
Hope that helps,
 
Sebastian
 
</blockquote>
 
</blockquote>
 
</body>
</html>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	How to execute two different types of resolution in same unit of work?
Next Topic:	Could I create jdt projects in the workspace as result of a xtext generator ?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 03:05:06 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter