You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/09/03 08:25:02 UTC
[jira] [Updated] (ARIA-357) Detect plugin dependencies collisions
at plugin installation
[ https://issues.apache.org/jira/browse/ARIA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ran Ziv updated ARIA-357:
-------------------------
Priority: Minor (was: Trivial)
> Detect plugin dependencies collisions at plugin installation
> ------------------------------------------------------------
>
> Key: ARIA-357
> URL: https://issues.apache.org/jira/browse/ARIA-357
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Priority: Minor
>
> ARIA plugins are isolated from one another, yet their dependencies may collide with Python packages installed in the general ARIA python environment.
> To avoid messing up the ARIA installation, when plugins are installed, a constraint file is used to limit changes to existing packages in the ARIA environment in the case of collisions.
> This could lead to a problem where a plugin gets successfully installed, but then is unable to run properly since some of its dependencies are set in the wrong versions.
> ARIA could detect these issues at plugin installation time, and alert the user about this issue.
> Note: This would not help in the case where changes to the environment are made after the plugin has already installed - However, since this would require a manual installation of Python packages to the general ARIA environment, it makes sense that the user making this installation be required to be responsible and avoid such collisions, or use a separate Python environment for this installation.
> See [this thread|https://lists.apache.org/thread.html/7f2a6a7981efc9a53d8910db0fd300318078eac549c98e6659bd0956@%3Cdev.ariatosca.apache.org%3E] for more information.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)