Closed jastram closed 9 years ago
I will manage the Plateform / Maven / Feature action if @cecilebraun agree
I just committed the sources in merce_sysml2b branch in commit ec602c63155c943c001f091683edd8fa3e0c7a03.
@MatthieuPERIN : feel free to re-organize the directories as needed. They are 2 directories in top level https://github.com/openETCS/toolchain/tree/merce_sysml2b/tool/bundles/org.openetcs.merce_sysml2b directory:
@idelatorre Regarding documentation of MERCE sysml2b translator, we have a basic documentation here: https://github.com/openETCS/toolchain/blob/merce_sysml2b/tool/bundles/org.openetcs.merce_sysml2b/SysMLTransform/src/README.md
We will help to enhance the documentation and make it fit with the toolchain once integration into the toolchain is done.
I have a concern as this module is exactly labelled as the SysML2B module provided by Fraunhofer.
As I asked @MERCEmentre they have nothing in common.
My question is: do I keep them both and try to rename them correctly or I have to somehow merge them ? @jastram , @cecilebraun It is your call :)
Oops. :-)
they have nothing in common.
Then we should definitely change the namespace of one of those projects. Question is: which one, the one from @MERCEmentre or @astante.
I propose that we leave it to David and Alex to decide between them which project should be renamed. Criteria could be:
@MERCEmentre and @astante, please decide and document your decision here.
Hello,
Le 24/09/2014 14:30, Michael Jastram a écrit :
Then we should definitely change the namespace of one of those projects. Question is: which one, the one from @MERCEmentre https://github.com/MERCEmentre or @astante https://github.com/astante.
You can change the name of the Eclipse module for our code, I don't mind. The main issue is to find a good name. :) A suggestion: "B_blueprint"
Best regards, d.
According to Telco of 25-09-2014 the old plugin should be removed and remplaced by the @MERCEmentre one.
It is alsmost build !
I was away from office but I pushed it on friday the 3rd (commit 276e06ec48d3c0ac6457abb4b03b67696a13c930 ) As far as I know, if the build was made after 15h30 it should be present in the sprint 19 toolchain !
@cecilebraun please confirm, @idelatorre / @MERCEmentre it is up to you for the documentation :)
The code is inside the toolchain but ...as there is no UI integration (no contribution to the menu) the code cannot be executed during runtime (during the standard use of the toolchain).
Nothing to worry but someone have to take the time to link the code with the Eclipse UI (command, menu contribution and all.)
@MERCEmentre do you act on this ?
Could we open a new issue for the Eclipse UI integration ?
Thanks a lot @MatthieuPERIN for putting the code in the toolchain!
The link to the documentation is not correct,
Is the good one : https://github.com/openETCS/toolchain/tree/master/tool/bundles/org.openetcs.sysml2b.transformation/src ?
The following steps are necessary for integrating @MERCEmentre's contribution: