Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347317

Summary: Resolution of uriFragment 'xtextLink_::0.1.6.32.4.0.0::0::/2' failed
Product: [Modeling] TMF Reporter: Serano Colameo <serano.colameo>
Component: XtextAssignee: Project Inbox <tmf.xtext-inbox>
Status: CLOSED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: sebastian.zarnekow
Version: 2.0.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
error log
none
error-log.txt
none
mvn.log none

Description Serano Colameo CLA 2011-05-26 09:44:12 EDT 
Build Identifier: Xtext 2.0.0.v201105230203

This exception happens quite a lot:

org.eclipse.xtext.linking.lazy.LazyLinkingResource  - resolution of uriFragment 'xtextLink_::0.1.6.32.4.0.0::0::/2' failed.

An exception stack trace is not available.


Reproducible: Always

Steps to Reproduce:
1. see details & error log file
2.
3.
Comment 1 Serano Colameo CLA 2011-05-26 09:45:17 EDT 
Created attachment 196662 [details]
error log
Comment 2 Sebastian Zarnekow CLA 2011-05-26 09:46:55 EDT 
Hi Serano,

does the exception lead to an error dialog in the ui or did you see it in the log? Could you share some input files that reproduce the exception?
Comment 3 Sebastian Zarnekow CLA 2011-08-28 12:52:36 EDT 
Since I've no idea on how to reproduce this and the available information is not sufficient to get down to the root cause, I'll close this one as invalid. Please reopen and add some more data if the problem persists.
Comment 4 Amit Mendapara CLA 2011-09-23 15:41:39 EDT 
Created attachment 203938 [details]
error-log.txt

I am seeing a similar issue.

I observed that this happens when we have multiple projects open in workspace and `Project -> Build Automatically` enabled and one of the project (of Xtext nature, using some DSL) depends on another project.

If I disable the `Build Automatically` and do `Project/Clean...` => `Clean all projects & Build entire workspace` then it works fine.

I think, as automatic build generates code on the fly, the type system sometime fails to resolve some types resulting in this error.
Comment 5 Krzysztof Rzymkowski CLA 2013-06-27 09:13:50 EDT 
Created attachment 232839 [details]
mvn.log

"resolution of uriFragment 'xtextLink_::0.1.0.5.4.5.0.9.7.0.1.0.3::8::/1' failed. " error triggered from maven plugin 2.4.1-SNAPSHOT