Cannot deploy a plugin if another plugin doesn't compile anymore in the repository

[lesquoyb]

As the title says, it is currently impossible to deploy a perfectly working plugin if there's another one that doesn't compile in the repository.

As this repository is maintained by multiple people, each with their own schedule and priorities, it's not something uncommon that a plugin does not keep up with the most recent changes in the gama platform and thus does not compile anymore, which impacts all the other plugins as they can't be individually deployed.

So I'd like the deployment process of the plugins to be done independently. We could still deploy all the plugins at once as it's currently the case, but the failure of one would only impact its own deployment. What could also be interesting is to be able to manually deploy only one plugin

[RoiArthurB]

Progression status :

• Done
  • Generate release 1.9.3 stable packages
  • Publish those packages on p2 https://updates.gama-platform.org/1.9.3
  • Note: This update site is both compliant with Maven repo (default) and tycho's p2 repo
• Next
  • Verify experimental compile with this updated p2