See plugin validation documentation to better understand what to do when your build suffers from such warnings. Plugins and extensions used by your build are checked against Maven supported APIs and conventions: this “plugin validation” may report WARNINGs at the end of your build.As a consequence, this may introduce breakage in environments where the user properties were used to set system properties or other way around, for example see MNG-7887. System and user properties handling cleanup, see MNG-7556.That is, if the file contains multiple arguments, these must now be placed on separate lines, see MNG-7684. mvn/nfig is now interpreted as a single argument. Mojos are prevented to bootstrap new instance of RepositorySystem (for example by using deprecated ServiceLocator), they should reuse RepositorySystem instance provided by Maven instead.The workaround for affected plugin users is to add this dependency to plugin dependencies until issue is fixed by the affected plugin maintainer. The fix for affected plugin maintainers is to explicitly declare a dependency on plexus-utils. Starting with Maven 3.9, it does not happen anymore. Maven 2.x was auto-injecting an ancient version of plexus-utils dependency into the plugin classpath, and Maven 3.x continued doing this to preserve backward compatibility.The Maven Resolver transport has changed from Wagon to “native HTTP”, see Resolver Transport guide.Potentially Breaking Core Changes (if migrating from 3.8.x) See Resolver configuration and named locks Most notably MNG-7819 got fixed that was affecting Maven 3.9.2, but the fix have important implication:ĭue file locking naming scheme changes, Maven 3.9.3 with file locking will not be able to share local repository with another Maven version that Updated Resolver brings transport and locking related fixes and improvements.Furthermore, the precision of warnings and some badly worded messages are fixed. To enjoy them, one needs explicitly to enable (and requires a release and updating in current project POM) are NOT displayed anymore by default. Plugin non-configuration issues, that can be fixed by corresponding plugin developer only User: issues that user can fix by editing the project POM. Moreover, by default only “project local” messages are displayed to Validation messages are always collected (asīefore), but default display mode is again “inline” as it was in Maven 3.9.1. Plugin validation did shake up Maven users community, hence, on users request, they are “toned down”.Released with same plugin versions as Maven 3.9.1 and 3.9.0). Huge effort of updating ASF Maven plugins is ongoing, and Maven received a ton of lifecycle bound plugin version updates since Maven 3.9.2 (that was.The full list of changes can be found in our issue management system. Regression fixes and changes based on user feedback from Maven 3.9.2.If you have any questions, please consult: Further releases of plugins will be made separately. The core release is independent of plugin releases. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting, and documentation from a central place. Maven is a software project management and comprehension tool. The Apache Maven team would like to announce the release of Maven 3.9.3.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |