Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322483 - [HUTN] Support relative URIs in references to external objects.
Summary: [HUTN] Support relative URIs in references to external objects.
Status: CLOSED FIXED
Alias: None
Product: Epsilon
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dimitris Kolovos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-12 05:00 EDT by Hallvard Traetteberg CLA
Modified: 2012-02-06 10:59 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hallvard Traetteberg CLA 2010-08-12 05:00:27 EDT 
Epsilon's HUTN implementation supports referencing objects in other models, by means of EMF URIs. However, only absolute URIs are supported, so the URIs become long and easily break when files and folders are moved.

I suggest supporting relative URIs that are resolved with the current model's URI as the base.
Comment 1 Louis Rose CLA 2010-08-12 07:03:00 EDT 
I agree that this would be useful. Thanks for the suggestion, Hallvard.

We'll need to change the Spec object to carry the source file's URI, and then to resolve relative URIs against the source file URI.
Comment 2 Louis Rose CLA 2010-08-12 07:36:34 EDT 
This has now been implemented and checked into SVN.

Assigning to Dimitris for inclusion in the next build. Cheers!
Comment 3 Louis Rose CLA 2010-08-31 10:41:19 EDT 
The tests for this feature fail on Windows. I'm about to check a fix into SVN...
Comment 4 Dimitris Kolovos CLA 2010-11-25 08:10:55 EST 
Louis: Has this been resolved?
Comment 5 Louis Rose CLA 2010-11-26 09:49:56 EST 
(In reply to comment #4)
> Louis: Has this been resolved?

Sorry... Yes. the Windows fix passes the test, and has been checked into SVN for a while. The fix will have made it into 0.9.
Comment 6 Louis Rose CLA 2011-06-01 14:09:04 EDT 
This was fixed in 0.9.0.