jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Gritsch (Jira)" <j...@apache.org>
Subject [jira] [Created] (JCLOUDS-1555) Maven Configuration Cleanup
Date Mon, 26 Oct 2020 09:15:00 GMT
Markus Gritsch created JCLOUDS-1555:

             Summary: Maven Configuration Cleanup
                 Key: JCLOUDS-1555
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1555
             Project: jclouds
          Issue Type: Improvement
    Affects Versions: 2.3.0
            Reporter: Markus Gritsch

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.

This message was sent by Atlassian Jira

View raw message