No, only the length of the path (256 characters limit) but I think we already checked that…
You can revert an installation in the installation history of Eclipse maybe you could reach a point where you can reinstall M2Doc or the M2Doc extensions. Or maybe you can start from a fresh install.
Obviously, the situation is complicated and may be not really well structured/designed, because after installing bare Capella + m2doc, everything is ok (jsoup is a RESOLVED bundle), but when adding the Thales dropins, it simply disappears (is not present in the list of bundeles). May be p2 garbage collection removes it. So currently we simply try to install the jsoup bundle. But on jsoup.org only the jar is available and from the m2doc update site it cannot be installed after m2doc has been installed already. Also when creating the plugin project from existing jar in Capella, the plugin has a different structure than the zip files below p/m2doc. Do you know how to create and install the jsoup bundle?
Can you have access to an update site of what you try to use via droppings ? It will probably provide information about what goes wrong. P2 is here to deal with dependencies and also compute what can or can’t be installed and even download missing dependencies.
JSoup can be found in Orbit: https://download.eclipse.org/tools/orbit/downloads/
Affirmative! Every plug-in, add-on, feature should be installed, updated etc. via p2 and p2 only. It seems however, that when we install the dropins from update sites via p2, not all of the addons actually work. Uwe, I think, will write an internal ticket wrt this. This is not related to m2doc, obviously. m2doc is most probably not the actual root cause, it is the effect of that issue that, at the end of the day, the jsoup bundle is not present and thus the m2doc HTML services do not work. Thanks for the support so far - should any progress be made on our part in resolving the issue, I will keep you posted. br, M.
1 Like
I managed now to install all Thales add-ons on from update site. Still, if I install M2Doc on top jsoup is not visible from the user area.
It is visible and working, though, If I run Capella in admin mode (i.e. -configuration is in install area).
It is somehow strange that we have the issue only for the jsoup bundle; all other M2Doc bundles work fine.
My hypotheses is that there is some interference with Thales add-on. I opened an internal Thales ticket and hope to get feedback.
Maybe one of this add-on depend on an other version of jsoup and both versions cant be installed at the sametime. But in this case you should have a warning when installing it with p2…
Let me know when you have more information.
The workaround we have now is to install M2Doc as dropin opposed to install it from update site. (Even though, it is not clear to me why this works better).
We use Capella Extensions from this site: https://s3-eu-west-1.amazonaws.com/obeo-networkaggregation-releases/capella-extensions/1.4.2/full/org.obeonetwork.capella.update.full.zip , which is M2Doc 3.10.
An dropin installation for a new version of M2Doc (3.11) does not work.
I wonder if there is any possibility to get M2Doc3.11?
I’m working on fixing this issue for M2Doc 3.2.0. There is a nightly build if you want to try your installation method:
https://s3-eu-west-1.amazonaws.com/obeo-m2doc-releases/master/nightly/repository zip
We will see if we need to backport this fix to previous versions of M2Doc and M2Doc extensions for Capella.
If I use the nightly from today (26 April) I am able to install it in the dropins way and the ‘fromHTMLBodyString’ does work.
But, then the command line feature does not work any longer. That was the reason why I used Capella extensions.
I wonder if I can combine the nightly with Capella extensions.
We the command line is specific to Capella. It was just to make sure the next release will solve your issue. There is a nightly build of the M2Doc extensions for Capella 5.1.0 (under development):
https://s3-eu-west-1.amazonaws.com/obeo-networkaggregation-releases/capella-extensions/master/nightly/full zip
But you will not be able to install it in an other version of Capella.