Bug 520349 - Ability to invoke Acceleo queries located in different project
Summary: Ability to invoke Acceleo queries located in different project
Status: UNCONFIRMED
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 4.1.1   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-07-31 04:16 EDT by Niels Brouwers CLA
Modified: 2017-08-02 10:53 EDT (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 Niels Brouwers CLA 2017-07-31 04:16:38 EDT 
In one of the VSPs, we invoke an Acceleo query that in turn invokes an Acceleo query from another project. This case is similar as described in:
https://www.eclipse.org/forums/index.php/m/1759195/

This approach works when the product containing the VSPs is built using Maven/Tycho. Unfortunately, the query from the other project cannot be resolved in a run-time environment. This introduces a development-test round-trip with an unacceptable long duration. 

Could you please add the ability to invoke queries located in a different project from an Eclipse instance or a run-time Eclipse environment?

PS. The actual version of Sirius being used is 4.1.3.
Comment 1 Laurent Redor CLA 2017-08-02 10:53:06 EDT 
This problem is maybe linked to the Acceleo bug 444209.

We are aware of this but have no plans to work on it in the following weeks.
That said this bug can move forward if you provide a fix for it (see the Contributor Guide) or you contact Obeo for sponsored work.

For information, I quickly check but my external Acceleo query was not found neither in a run-time environment neither when built.