You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the Maven plugin on v2.5.1 with -Dmaven.plugin.validation=verbose in the MAVEN_ARGS results in the following warning:
[WARNING] Mojo EXTERNAL issue(s):
[WARNING] * Mojo apigee-enterprise:configure (io.apigee.buildTools.enterprise4g.mavenplugin.ConfigureMojo)
[WARNING] - Mojo implements `Contextualizable` interface from Plexus Container, which is EOL.
[WARNING]
[WARNING]
[WARNING] Fix reported issues by adjusting plugin configuration or by upgrading above listed plugins. If no upgrade available, please notify plugin maintainers about reported issues.
[WARNING] For more or less details, use 'maven.plugin.validation' property with one of the values (case insensitive): [NONE, INLINE, SUMMARY, BRIEF, VERBOSE]
[WARNING]
The use of Plexus can be replaced with the use of Eclipse Sisu, which should also reduce some complexity as it implements the Java CDI spec, and is the recommended way to achieve CDI in Maven Plugins now.
The use of end-of-life features should probably be fixed since it would pose a blocker to Maven 4.0 migration once it becomes available.
The text was updated successfully, but these errors were encountered:
@ascopes - thanks for sharing. Apologies for the delayed response
I am not seeing any docs around this. The GitHub repo is marked as publicly archived and the main repo links seems to be broken. Can you share any info on this so that I can take a look and see how much work is needed?
Running the Maven plugin on v2.5.1 with
-Dmaven.plugin.validation=verbose
in theMAVEN_ARGS
results in the following warning:The use of Plexus can be replaced with the use of Eclipse Sisu, which should also reduce some complexity as it implements the Java CDI spec, and is the recommended way to achieve CDI in Maven Plugins now.
The use of end-of-life features should probably be fixed since it would pose a blocker to Maven 4.0 migration once it becomes available.
The text was updated successfully, but these errors were encountered: