Bug 469814 - Wizard "Viewpoint Specification Project" explicitely depends on Acceleo3
Summary: Wizard "Viewpoint Specification Project" explicitely depends on Acceleo3
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-06-10 05:03 EDT by Laurent Redor CLA
Modified: 2015-06-12 10:17 EDT (History)
2 users (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 Laurent Redor CLA 2015-06-10 05:03:09 EDT 
When using the "Viewpoint Specification Project", the MANIFEST.MF file always contains a dependency to org.eclipse.sirius.common.acceleo.mtl, even if the optional support of Acceleo3 is not installed. The Acceleo 3 is currently the default query language. But it is not mandatory, so this dependency should be an option in the wizard. 
Ideally, the wizard should propose the query language to use (according to those installed) and according to the user choice, the wizard should add the necessary dependencies.
Comment 1 Maxime Porhel CLA 2015-06-10 05:30:34 EDT 
The manifest .mf is created in ViewpointSpecicationProject.convert(), line 352:

ViewpointSpecificationProject.createFileFromTemplate(prj, "META-INF/MANIFEST.MF", "resources/MANIFEST.MF", replacements, monitor); //$NON-NLS-1$ $NON-NLS-2$

The template file explicitetly contains the dependency to org.eclipse.sirius.common.acceleo.mtl

At the end of the convert() method, the addAcceleoNature() is called. It adds the Acceleo nature only if the Acceleo bridge is present (if the conversion command defined in org.eclipse.sirius.common.acceleo.mtl.ide exists).