Home » Modeling » TMF (Xtext) » Xtext 2.3 M6 Grammar Editor can't resolve JavaVMTypes import correctly(When I import "http://www.eclipse.org/xtext/common/JavaVMTypes" a warning marker is created)
| Xtext 2.3 M6 Grammar Editor can't resolve JavaVMTypes import correctly [message #842482] |
Thu, 12 April 2012 10:38  |
 Jochen Schmich
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
Hi everybody,
if I introduce the following statement:
import "ht tp://www.eclipse.org/xtext/common/JavaVMTypes" as types
...a warning marker tells me that:
Quote:The imported package is not on the classpath of this project
which may lead to follow up errors.
The MANIFEST.MF looks correct:
Require-Bundle: org.eclipse.xtext;bundle-version="2.1.0";visibility:=reexport,
org.eclipse.xtext.common.types;visibility:=reexport,
org.eclipse.xtext.xbase;bundle-version="2.1.0";resolution:=optional;visibility:=reexport,
org.eclipse.xtext.generator;resolution:=optional,
org.eclipse.emf.codegen.ecore;resolution:=optional,
org.eclipse.emf.mwe.utils;resolution:=optional,
org.eclipse.emf.mwe2.launch;resolution:=optional,
org.eclipse.xtext.util,
org.eclipse.emf.ecore,
org.eclipse.emf.common,
org.antlr.runtime,
org.eclipse.xtext.xbase.lib
Import-Package: org.apache.commons.logging,
org.apache.log4j,
org.eclipse.xtext.xbase.lib
The editor seems to work anyway (at least after a restart) - in terms of content assistance etc. JvmType, for example, can be referenced and used correctly. The generator doesn't complain either.
I do currently use Xtext SDK 2.3.0.v201204101126.
|
|
|
| Re: Xtext 2.3 M6 Grammar Editor can't resolve JavaVMTypes import correctly [message #842489 is a reply to message #842482] |
Thu, 12 April 2012 10:43  |
Sebastian Zarnekow
Messages: 3118
Registered: July 2009 |
Senior Member |
|
|
Hi Jochen,
That's probably a PDE issue. Please remove the common.types bundle from
your manifest, save it, re-add that bundle and save the manifest again.
That may help.
Regards,
Sebastian
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Am 12.04.12 12:38, schrieb Jochen Schmich:
> Hi everybody,
>
> if I introduce the following statement:
>
> import "ht tp://www.eclipse.org/xtext/common/JavaVMTypes" as types
>
>
> ...a warning marker tells me that:
> Quote:
>> The imported package is not on the classpath of this project
>> which may lead to follow up errors.
>
>
> The MANIFEST.MF looks correct:
>
> Require-Bundle:
> org.eclipse.xtext;bundle-version="2.1.0";visibility:=reexport,
> org.eclipse.xtext.common.types;visibility:=reexport,
> org.eclipse.xtext.xbase;bundle-version="2.1.0";resolution:=optional;visibility:=reexport,
>
> org.eclipse.xtext.generator;resolution:=optional,
> org.eclipse.emf.codegen.ecore;resolution:=optional,
> org.eclipse.emf.mwe.utils;resolution:=optional,
> org.eclipse.emf.mwe2.launch;resolution:=optional,
> org.eclipse.xtext.util,
> org.eclipse.emf.ecore,
> org.eclipse.emf.common,
> org.antlr.runtime,
> org.eclipse.xtext.xbase.lib
> Import-Package: org.apache.commons.logging,
> org.apache.log4j,
> org.eclipse.xtext.xbase.lib
>
> The editor seems to work anyway (at least after a restart) - in terms of
> content assistance etc. JvmType, for example, can be referenced and used
> correctly. The generator doesn't complain either.
>
> I do currently use Xtext SDK 2.3.0.v201204101126.
|
|
| | | | | |
Goto Forum:
Current Time: Sat Apr 20 03:14:26 GMT 2024
Powered by FUDForum. Page generated in 0.03028 seconds |
] 
Search
Help
Register
Login
Home
