[ 
https://issues.apache.org/jira/browse/MNG-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583610#comment-17583610
 ] 

ASF GitHub Bot commented on MNG-7502:
-------------------------------------

slachiewicz opened a new pull request, #790:
URL: https://github.com/apache/maven/pull/790

   Following this checklist to help us incorporate your
   contribution quickly and easily:
   
    - [X] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MNG) filed
          for the change (usually before you start working on it).  Trivial 
changes like typos do not
          require a JIRA issue. Your pull request should address just this 
issue, without
          pulling in other changes.
    - [X] Each commit in the pull request should have a meaningful subject line 
and body.
    - [X] Format the pull request title like `[MNG-XXX] SUMMARY`, where you 
replace `MNG-XXX`
          and `SUMMARY` with the appropriate JIRA issue. Best practice is to 
use the JIRA issue
          title in the pull request title and in the first line of the commit 
message.
    - [X] Write a pull request description that is detailed enough to 
understand what the pull request does, how, and why.
    - [X] Run `mvn clean verify` to make sure basic checks pass. A more 
thorough check will
          be performed on your pull request automatically.
    - [X] You have run the [Core IT][core-its] successfully.
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [X] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   [core-its]: https://maven.apache.org/core-its/core-it-suite/
   




> Upgrade Guice to 5.1.0
> ----------------------
>
>                 Key: MNG-7502
>                 URL: https://issues.apache.org/jira/browse/MNG-7502
>             Project: Maven
>          Issue Type: Dependency upgrade
>            Reporter: Sylwester Lachiewicz
>            Priority: Major
>             Fix For: 3.9.0-candidate, 4.0.x-candidate
>
>
> h3. Release notes:
> https://github.com/google/guice/wiki/Guice510
> https://github.com/google/guice/wiki/Guice501
>  
>  * Java 17 support: updated asm version and fixed unsafe class defining to 
> work with Java 17.
>  * Removed cglib as a core dependency. Guice now uses ASM directly to 
> generate bytecode at runtime for invoking user code and supporting method 
> interception
>  * Improved error messages
>  ** package names in error messages are compressed to make it easier to read
>  ** errors with the same cause are grouped and reported together
>  ** common error now links to a wiki page on how to debug and fix the error
>  ** additional information like parameter names are included when code are 
> compiled with javac {{-parameters}} flag
>  ** rich formatting like bold, color are used when errors are displayed in a 
> supported console (can be disabled with 
> {{-Dguice_colorize_error_messages=DISABLED}} flag)
>  * Removed no-aop build variant.
>  * Updated the Guava and ASM versions



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to