Optimizing the Build Process for SySON EasyMod Extension

[imeneazouzi]

I’m working on SySON EasyMod to extend SySON. Currently, to build each time, I need to regenerate a new JAR file. Is there an alternative method, like creating a Spring Boot project and adding SySON dependencies along with the SySON services from EasyMod?

[jessymallet]

Do you mean you want to quickly test what you are developing?

Build and launch the backend

In this way, you can use a STS Eclipse IDE. Then you import your EasyMod maven modules and you import also SysON maven module. You modify then the class SysONApplication.java to scan your EasyMod maven module

@ComponentScan(basePackages = { "org.eclipse.syson", "org.eclipse.sirius.web", "org.eclipse.sirius.components", "org.eclipse.easymod" })

Finally, you can launch your backend like a spring boot application

Launch the frontend

You can launch the frontend from the frontend folder (SysON\frontend\syson) of your SysON repository with the command npm start.
(You will have built and install the dependencies that go well before with commands npm ci and npm run build)

[imeneazouzi]

What I understand is that SysML v2 can be extended using metadata and libraries. What my team and I are trying to achieve is an editor based on SySON, tailored to a specific domain, with customized components, styles, and a dedicated palette.

To achieve this, would you recommend using libraries or metadata? I believe libraries might be the best choice for this purpose, but I'd be grateful to hear your opinion.

[AxelRICHARD]

Hello,

Libraries and metadata are not exclusive.
You may create a library containing metadata.
So, I can't tell you if one solution is better than the other.

Regards,