Is your feature request related to a problem? Please describe.
Plugins are central pieces for the development environment. In a team, usage of IDE is diverse: Some would use odo + Eclipse IDE or odo + vscode, or Eclipse Che. The problem is that IDE plugins to install or activate can not be easily shared. If a project needs tooling like a MySQL plugin, how could we have the right plugin installed in VSCode, Eclipse IDE and Eclipse Che?
Describe the solution you'd like
A devfile should allow a user to define the plugins he wishes to install. It would be up to the IDE to install them or not.
A way to do could be to include plugins recommandation that are not tight to an IDE.
these plugins recommandation could be identified with IDs for instance:
Each IDE that supports the devfile (natively, with a plugin or generator) could then have a mapping between the devfile plugin IDs and the real plugins or extensions to install.
So these are some example on the plugins id we could have:
language/java11
language/quarkus
guide/didact
connector/openshift
scm/git
scm/github
database/mysql
database/postgresql
database/mongo
issues/bugzilla
issues/github
issues/jira
etc.
It would then be up to the IDE or a generator to consume the recommanded plugins from the devfile and install/activate the right ones in the IDE.
We could have a dedicated section plugins with a list of plugins that are recommended to be activated or install:
Is your feature request related to a problem? Please describe. Plugins are central pieces for the development environment. In a team, usage of IDE is diverse: Some would use odo + Eclipse IDE or odo + vscode, or Eclipse Che. The problem is that IDE plugins to install or activate can not be easily shared. If a project needs tooling like a MySQL plugin, how could we have the right plugin installed in VSCode, Eclipse IDE and Eclipse Che?
Describe the solution you'd like A devfile should allow a user to define the plugins he wishes to install. It would be up to the IDE to install them or not. A way to do could be to include plugins recommandation that are not tight to an IDE. these plugins recommandation could be identified with IDs for instance: Each IDE that supports the devfile (natively, with a plugin or generator) could then have a mapping between the devfile plugin IDs and the real plugins or extensions to install.
So these are some example on the plugins id we could have:
language/java11
language/quarkus
guide/didact
connector/openshift
scm/git
scm/github
database/mysql
database/postgresql
database/mongo
issues/bugzilla
issues/github
issues/jira
It would then be up to the IDE or a generator to consume the recommanded plugins from the devfile and install/activate the right ones in the IDE.
We could have a dedicated section
plugins
with a list of plugins that are recommended to be activated or install:IDE that doesn't support a plugin could just ignore it.
Additional context Related to : https://github.com/eclipse/che/issues/18892