Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336109 - Unhelpful definition of MODULE_FILE_NAME
Summary: Unhelpful definition of MODULE_FILE_NAME
Status: CLOSED FIXED
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows Vista
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-02 12:28 EST by Ed Willink CLA
Modified: 2011-04-06 09:56 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 Ed Willink CLA 2011-02-02 12:28:52 EST 
MODULE_FILE_NAME is currently auto-generated as a simple name such as

public static final String MODULE_FILE_NAME = "generateXtextVisitors";

This is unhelpful because if a subclass of GenerateXtextVisitors is created, findModuleURL fails to find the module since it is unable to locate the bin path.

If instead the definition is e.g.

public static final String MODULE_FILE_NAME = "/org/eclipse/ocl/examples/build/acceleo/generateXtextVisitors";

findModuleURL continues to work regardless of the location of the generator class.
Comment 1 Stephane Begaudeau CLA 2011-04-06 09:56:08 EDT 
The fix has been contributed on HEAD. It will be available in Acceleo 3.1.0M7.