You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some automatically generated methods lack of proper @generated annotations. Thus, in order to apply model changes existing java files must be deleted so that a full generation is done, and no in-place update is possible.
This is only a small example. Inspect generation templates for other cases. On a quick look, I see other methods such as toPNML (without args), fromPNML, idRefHang, validateOCL, etc.
The text was updated successfully, but these errors were encountered:
Some automatically generated methods lack of proper
@generated
annotations. Thus, in order to apply model changes existing java files must be deleted so that a full generation is done, and no in-place update is possible.See an example of the issue in the template https://github.com/lip6/pnmlframework/blob/master/pnmlFw-Low_Level_API_Generation/templates-2.2.0/ToPNML/ToPNMLNIO.javajet which generates the
toPNML(FileChannel fc)
method in all domain classes.For an example of generated code, see:
pnmlframework/pnmlFw-PT-HLPNG/src/fr/lip6/move/pnml/pthlpng/booleans/impl/AndImpl.java
Line 105 in 346b9f9
A properly generated
toPNML(FileChannel fc)
should look like:This is only a small example. Inspect generation templates for other cases. On a quick look, I see other methods such as
toPNML
(without args),fromPNML
,idRefHang
,validateOCL
, etc.The text was updated successfully, but these errors were encountered: