Acceleo 7June 2011 Release Help (version 3.1) [message #685728] |
Sat, 18 June 2011 11:44  |
Dharam  Messages: 18 Registered: December 2010 |
Junior Member |
|
|
ERROR:
The template contains a main annotation (@main) but it isn't accessible. the package org.eclipse.acceleo.module.sample.JuneTest.common must be exported via the MANIFEST file.
Please find the attachment below for that. This error comes when I try to crate main module. Model has been removed due to security reasons.
Other Issues:
When I was using Eclipse Acceleo version (3.1M5), it was almost working fine except it was giving annotation error when we try to import one module in other.
In current version this error has been resolved but again annotation error comes for main module creation.
In release Acceleo 3.1M5, it was allowing to create simple acceleo module file (not main module file) without restricting user to enter metamodel uri, but in this version user has to enter that.(See Attachment) (Mandatory feature is pain)
If user is having his/her own meta model in ecore, yes that uri would not be available until he generates genmodel & code & run it as Eclipse plugin, but because in version 3.1M5 metamodel uri was not mandatory while creating module file, user can write at his own if he remembers uri without creating genmodel.
In version (3.1M5) whenever user creates any module file, acceleo engine was immediately creating .java file for that but in current version release it does for main module file only.
Requesting to provide guidance for that.
[Updated on: Tue, 21 June 2011 06:34] Report message to a moderator
|
|
|
Re: Acceleo 7June 2011 Release Bug (version 3.1) [message #685839 is a reply to message #685728] |
Mon, 20 June 2011 10:59   |
|
Dharam wrote on Sat, 18 June 2011 13:44
ERROR:
The template contains a main annotation (@main) but it isn't accessible. the package org.eclipse.acceleo.module.sample.JuneTest.common must be exported via the MANIFEST file.
If you create a main module, the package containing the main module always has to be exported. It always had to be exported. You just have to open the MANIFEST.MF file and go to the runtime tab, then you add a package to export it, in your case "org.eclipse.acceleo.module.sample.JuneTest.common".
Dharam wrote on Sat, 18 June 2011 13:44
In release Acceleo 3.1M5, it was allowing to create simple acceleo module file (not main module file) without restricting user to enter metamodel uri, but in this version user has to enter that.(See Attachment) (Mandatory feature is pain)
An Acceleo module without its metamodel uri is not valid. The wizard should not produce an invalid metamodel. The fact that it used to let the user produce an invalid module was the bug.
Dharam wrote on Sat, 18 June 2011 13:44
If user is having his/her own meta model in ecore, yes that uri would not be available until he generates genmodel & code & run it as Eclipse plugin, but because in version 3.1M5 metamodel uri was not mandatory while creating module file, user can write at his own if he remembers uri without creating genmodel.
So we need to improve it to show also the metamodel in the workspace (it is not be trivial since the popup where the user select the metamodel is provided by EMF).
Dharam wrote on Sat, 18 June 2011 13:44
In version (3.1M5) whenever user creates any module file, acceleo engine was immediately creating .java file for that but in current version release it does for main module file only.
Acceleo has stop to create a Java file for all modules almost two years ago in the 0.8 version. Acceleo 3.x has never created a Java launcher except if there is a [comment @main/] in a template of the module. You can remove the comment and the Java file will still be there we won't remove it since it may have been changed by the user but we only are creating it for main modules.
Regards,
Stephane Begaudeau, Obeo
--
Twitter: @sbegaudeau
Blog: http://stephanebegaudeau.tumblr.com
Acceleo Documentation: http://docs.obeonetwork.com/acceleo
|
|
|
|
Powered by
FUDForum. Page generated in 0.02396 seconds