mirror of https://github.com/apache/jclouds.git
40d2b1227f
- Increase version of Guava dependency from 22.0 to 27.1-jre. Note: In an OSGi runtime, Guice version 4.2.3 expects Guava with an exact version of 27.1-jre. For now, higher versions of Guava are not possible. - Separate version numbers from dependencies and plugins Following is a description of the purpose of the feature. New contributors find it difficult to understand the function and intent of different plugins integrated into JClouds. The primary goal is to simplify and streamline the overall setup. On closer examination of the integrated plugins you will notice that, - different plugins are used for the same or a similar goal - the development activity of used plugins has been terminated - modified integration requirements through Maven. The development of used plugins is progressing. Versions of the plugins integrated into JClouds are not up to date. Newer plugin versions require an adjustment to how integration into a project is done. Basically the setup of the plugins used in the Maven project POM was done a long time ago. The project POM file of the JClouds project serves as a parent for all modules in JClouds. The first step is to consolidate the used plugins. The same aspects apply to the build profiles used in the project. On closer look these must be considered obsolete. A deconstruction of declared build profiles is aimed at. In order to support newer runtime environments, for example JDK11 and above, we aim to integrate build profiles. In the respective build profile the libraries which are no longer contained in the respective target JDK but needed in JClouds are to be integrated. In the course of this rebuild, a property-based way of declaring the version number of dependencies and plugins will be implemented. |
||
|---|---|---|
| .. | ||
| src/etc | ||
| bnd.bnd | ||
| pom.xml | ||