Hi @Julien_HENRY,
Thank you for your reply.
With our current setup, we build a custom Eclipse IDE with all the plugins we need:
- Official plugins from Eclipse (mainly Java Dev Tooling + other)
- Some 3rd party plugins (I added SonarLint in this category)
- Some custom tools just for our project (something we build and that is only for us)
Then we have a collection of scripts that do: installation/update/reuse of the correct IDE (appropriate stream, depending on the version of the product we are working on), creation of the workspace, checkout of the Git repo and materialization of our project in the Workspace…
=> This could be mostly replaced by Oomph, but our scripts were there before, so we did not change to use Oomph.
This is only for our team.
I will have a look at the plugin_customization.ini that you are describing in the other thread.
I guess for a team as we are, it would be OK to share the token across the team.