Issues with dropings/viewpoints after adding Python4Capella-

Hello,
It happened to me twice, I suspect it to be a recurrect issue.
So there are 2 types of occurences:

  • A) Launching a new fresh Capella installation, adding/creating your model, and adding the required dropings (let’s say the requirement one) in the dropings folder.

    Opening the Viewpoint manager, the viewpoints are available.

    Restarting Capella. Installing Python4Capella (installation), configuring editors and develop capability, configure the python paths.

    The viewpoints are still available.

  • B) Installing Python4Capella following all the steps, then adding dropings in your dropings folder.
    Restarting and opening the Viewpoint manager → the viewpoints will not show up. It’s a problem.

    Any idea why would that happen? And how to solve it?
    My solution right now will be to do a fresh install whenever i need to add a new viewpoint, which is not convenient.

So too sum up, no newpoint seem to be taken in account after a Python4Capella full “instal"/

When droppings are installed no check are done regarding the dependencies. So it’s possible that Python4Capella install newer versions of some dependencies that prevent droppings to work. The best way to solve this is to use update sites instead of droppings if possible to install add-ons. This way p2 will make sure all dependencies are present and can be resolved.

1 Like

This includes using the “Add…” button and installing directly from a folder/or an archive, even if that does not come from an url site?
The requirement addon would not be added using the add folder/archive method, although, some addons cannot be found on the internet and can only be added using folder/archives.

Thanks for the answer by the way.
(subNote, i did not answer you yet in the generation doc subforum, i will later)

Yes use the Help/Install new Software… menu then add a p2 update site either and archive or an URL. You can also try to revert the Python4Capella installation (click already installed in the installation dialog then the installation history tab), then install your new addon then reinstall Python4Capella… not ideal but might work.

The other solution is to use the OSGi console to see why some bundles can’t be started. You will need to install the PDE (Plug-in Development Environment) to have access to the OSGi console.

1 Like

I thought PDE was already installed, since it is possible to change the viewpoint in Capella into PD:
image

In any case, i cant see the OSGi thing.


My requirement droping cannot be installed using the update site, the only was I was able to make it work was by drag and drop it in the dropings unfortunately (and restart).
Sorry for asking this but what is “p2’” ?
I am used to install things through the archives or files (Proof: M2DOC).

__
Ok i went searching for a more complete PDE just in case, and i found these ( Eclipse software repository | The Eclipse Foundation) but the “url” method never work me, as i have a restrcited netrork suspcious of this random downloads, only method is to download an archive/folder and add it manually.
Example:
image

p2 is the Eclipse package (OSGi bundle) management system, some information here. It make sure the installation is consistant and install dependencies if needed.
Yes the installation process is the same as M2Doc or Python4Capella.
The PDE can be installed from the Eclipse update site. You can check the Eclipse update site corresponding to your version of Capella in the M2Doc target platforms. For instance for Capella 1.4.0 it’s https://download.eclipse.org/releases/2019-06.

Ok so for Capella 5.1 which I am using, it is 2020-06 Eclipse software repository | The Eclipse Foundation
However as I mentioned, my restriced network prevent me from using the “url” method of installing new “software/addon” inside Capella/eclipse. At least it seems so.
After pressing enter, and after the error message, it leaves me with nothing:

I suppose i can browse “directory contents” until I find the PDE and download it manually then install it as a folder/archive pack.


More importantly for me, I hope have an opinion/idea about this, here is goes:

  • Are there some parameters to check/configure before packaging an addon, in order to make it possible for it to be installed using the menu > help > install > Add…?
    I am asking this because lot of dropins that I am using, or even the one I am making, can only be inserted to cappela through a simple drag and drop to the dropings folder. I mean that, if I try to do a menu > help > install > Add… I would get no option, such like this:

    It is the case for the Requirement viewpoint Official Capella Add-n, for instance.

To sum up:

  • i CANNOT install anything using URLS, because of the restrictions my internet network has.
  • I can only use the drag and drop method.
  • If the addon does actually need to be installed using the menu > help > install > Add…(such as M2DOC), then the addon can be put anywhere and installed anyway.
  • If the addon “would not” display any result with “menu > help > install > Add…”, then it can ONLY be added to my capella if i drag and drop it directly to the dropings folder. Thats the extent of my understanding.

I was wondering if I was missing anything.

And if it was possible to make the addons which cannot be installed with though menu, … well make them installable through the menu >… > add?

If that was ever related to the configuration of the packaging somehow when creating an addon? And if that configuration existed, then IF that configuration was missed before/during packaging, i was wondering if there was any other tweak to do after the packaging to make it "installable through the …add menu)? I would do that to the requirement addon which is already packaged. Among other packages which I would like to apply that.

Hope this is clear. Thanks a lot for every answer, it is really appreciated, that’s the least can be said honestly, thanks.

You can define a proxy in Eclipse preferences, this might help with your network.

You will need to build an update site. You can check the M2Doc Capella addon code. Check the update site project.

Basically if nothing shows up in the installation dialog, you did not provide a p2 update site.

Maybe you can recreate a p2 update site from your Capella installation using this. Then use it for re-installation… You can also check tools like p2 director for scripting installation.

1 Like