Should share models library accross projects

[GoogleCodeExporter]

Currently, the library of existing alloy models appear inside each alloy 
project.

As a consequence, if one creates 10 alloy projects, Xtext will go through 10 
times the same files.

One way to avoid that can be to have the library of models shared across all 
Alloy projects, by creating a special top level project called A4library for 
instance, containing all the current links to the models.

When creating a new project, a reference to A4library could be added in the 
path.

Not sure how flexible is Xtext about accessing resources outside a project.

Original issue reported on code.google.com by daniel.l...@gmail.com on 19 May 2011 at 7:15

[GoogleCodeExporter]

This improvement has been added with revisions r1005-r1006

Original comment by kapusta....@gmail.com on 1 Jun 2011 at 11:35

[GoogleCodeExporter]

Fixed. Thanks.

Original comment by daniel.l...@gmail.com on 1 Jun 2011 at 12:07

• Changed state: Verified

[GoogleCodeExporter]

Imported resources not found on my Linux machine (open util/integer).

Original comment by daniel.l...@gmail.com on 1 Jun 2011 at 12:54

• Changed state: Started

[GoogleCodeExporter]

A4 Models Library project misses the Xtext nature.

Original comment by daniel.l...@gmail.com on 1 Jun 2011 at 1:03

[GoogleCodeExporter]

After fixing a few issues related to bundles, it looks like working now, after 
a clean on the projects. I wonder however is the project needs to be a Xtext 
nature or not.

Original comment by daniel.l...@gmail.com on 1 Jun 2011 at 10:07

[GoogleCodeExporter]

I confirm that the shared project requires the xtext nature to work properly.

Original comment by daniel.l...@gmail.com on 2 Jun 2011 at 9:45

[GoogleCodeExporter]

All this is fixed in release 0.3.0.

Original comment by daniel.l...@gmail.com on 7 Jun 2011 at 6:10

• Changed state: Verified