I tried inside another Capella Installation, I don’t why it did not work with the first one I will try to figure out the difference later. However as for now, well:
The second capella config seemed to let met open the java extension easily:
Then I made sure i had ONLY the plugins containing my JS in the workspace + the capella project itself (all inside Capella, not CS)
So I was able to add the service into the template
However when generating the doc, only the function with EObject was recognized yet again, the Capablity or CapellaObject not so much!
Validation doc:
Generated doc:
__
What other problem could it be? I really had my plugin INSIDE the capella workspace this time.
You claim I could transform my plugins from CS into an update site and add to them a template that could this time work?
What if I wanted to create a new template in addition to the one put inside the update site?
I never noticed when adding an update site into Capella whether the java extension from odesign could be added through the template wizard? It appears strange to me, this means that ALL Capella Extensions could have their java extensions/classes/JS added into M2DOC Templates? I must try this anyway but if you any any other input please tell, thanks.
(Note: unrelated, I played with the word “static” to see, but that has no correlation whatoever)
A second note:
- Inside Capella, I don’t find the “build path” option to be able to add my external Jar’s (if needed), so I commented out the functions who needed the Jars, i just want to make the test1 and test2 functions work