dependabot[bot] opened a new pull request, #1627:
URL: https://github.com/apache/maven-mvnd/pull/1627

   Bumps 
[org.codehaus.gmavenplus:gmavenplus-plugin](https://github.com/groovy/GMavenPlus)
 from 4.3.1 to 5.0.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/groovy/GMavenPlus/releases";>org.codehaus.gmavenplus:gmavenplus-plugin's
 releases</a>.</em></p>
   <blockquote>
   <h2>5.0.0</h2>
   <h2>Bugs</h2>
   <ul>
   <li>Fix Javadoc mismatch in <code>ReflectionUtils.getDeclaredMethods</code> 
(<a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/365";>#365</a>)</li>
   <li>Remove unneeded fork parameter (<a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/361";>#361</a>)</li>
   <li>Fix Groovy 5 shell support (closes <a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/367";>#367</a>) (<a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/380";>#380</a>)</li>
   </ul>
   <h2>Enhancements</h2>
   <ul>
   <li>Support Groovy 6 changes to GroovyDoc (closes <a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/381";>#381</a>) (<a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/382";>#382</a>)</li>
   </ul>
   <h2>Potentially breaking changes</h2>
   <ul>
   <li>Removed the <code>fork</code> parameter</li>
   <li>GMavenPlus no longer includes JLine, Jansi, Ant, or Ivy dependencies</li>
   </ul>
   <h2>Notes</h2>
   <ul>
   <li>GMavenPlus used to include the Jansi 2.4 and JLine 2.14.6 so that Groovy 
2.2.0-beta-1 and newer would have colors work in Groovysh out of the box. 
However, JLine 2 is EOL, Groovy 5.x uses Jline 3, and Groovy 6.x uses JLine 4. 
Additionally, Maven 3.9 introduces a JLine 2.x into the classpath. This meant 
that Groovy 5.x and 6.x would never have their colors work with Maven 3.9.</li>
   <li>GMavenPlus used to include Ant and Ivy, to make it easy to use 
<code>@Grab</code> and <code>AntBuilder</code> in scripts, Groovysh, and Groovy 
Console. The need to remove JLine/Jansi gave a reason to revisit this 
philosophy. Here are the reasons why this was abandoned.
   <ul>
   <li>The plugin version can win over the version in the project (unless you 
make sure to use an <code>&lt;exclusion&gt;</code></li>
   <li>To avoid downloading dependencies you may or may not need</li>
   <li>If future Groovy versions use other versions of Ant/Ivy (like we ran 
into with JLine/Jansi), we'll have a similar breaking change needed</li>
   </ul>
   </li>
   <li>Here are examples of how to add back the dependencies you need
   <pre lang="xml"><code>&lt;plugin&gt;
     &lt;groupId&gt;org.codehaus.gmavenplus&lt;/groupId&gt;
     &lt;artifactId&gt;gmavenplus-plugin&lt;/artifactId&gt;
     &lt;version&gt;5.0.0&lt;/version&gt;
     &lt;executions&gt;
       &lt;execution&gt;
         &lt;goals&gt;
           &lt;goal&gt;execute&lt;/goal&gt;
         &lt;/goals&gt;
       &lt;/execution&gt;
     &lt;/executions&gt;
     &lt;dependencies&gt;
       &lt;!-- Add Apache Ant if using AntBuilder --&gt;
       &lt;dependency&gt;
         &lt;groupId&gt;org.apache.ant&lt;/groupId&gt;
         &lt;artifactId&gt;ant&lt;/artifactId&gt;
         &lt;version&gt;1.10.15&lt;/version&gt;
       &lt;/dependency&gt;
       &lt;!-- Add Apache Ivy if using @Grab --&gt;
       &lt;dependency&gt;
         &lt;groupId&gt;org.apache.ivy&lt;/groupId&gt;
         &lt;artifactId&gt;ivy&lt;/artifactId&gt;
         &lt;version&gt;2.5.3&lt;/version&gt;
       &lt;/dependency&gt;
       &lt;!-- Add JLine 2 if using shell with Groovy 2.x/3.x/4.x --&gt;
       &lt;dependency&gt;
         &lt;groupId&gt;jline&lt;/groupId&gt;
         &lt;artifactId&gt;jline&lt;/artifactId&gt;
         &lt;version&gt;2.14.6&lt;/version&gt;
   </code></pre>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/52163dc69b869a46c003351745b27df02555a8df";><code>52163dc</code></a>
 [maven-release-plugin] prepare release 5.0.0</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/959772b96f4ce3f1c8384e5f4308fd7d53eff80e";><code>959772b</code></a>
 [maven-release-plugin] rollback the release of 5.0.0</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/f80ff7fc428d79e1306fb55e7ae2104d6b88a34c";><code>f80ff7f</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/36c703f42adbdbfc80b825de0cdc4281f8853568";><code>36c703f</code></a>
 [maven-release-plugin] prepare release 5.0.0</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/d0758619b7f548ccdd39a2a19f2da7e53c9901ec";><code>d075861</code></a>
 build: Upgrade Maven wrapper to 3.9.16</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/1a93e6a9d8d65cd7a455b3a8750a90ffba9a3266";><code>1a93e6a</code></a>
 Merge pull request <a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/382";>#382</a> from 
groovy/381</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/7283058ba7bd70de39649fa11d29815a4a67cf2d";><code>7283058</code></a>
 feat: Add version check and warning for all Groovy 6 GroovyDoc properties 
whe...</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/e2b0566b662ba07ca0ebfc769ef398d7feb126b5";><code>e2b0566</code></a>
 feat: Add version check and warning when preLanguage is used with older 
Groov...</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/fab97d2dd9d3dd2eab50ab3baf49f92d8757d5a4";><code>fab97d2</code></a>
 feat: Support Groovy 6 changes to GroovyDoc (closes <a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/381";>#381</a>)</li>
   <li><a 
href="https://github.com/groovy/GMavenPlus/commit/ddc14ad5131f197a6c0938a6768cfe3382c9984b";><code>ddc14ad</code></a>
 fix: Fix Groovy 5 shell support (closes <a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/367";>#367</a>) (<a 
href="https://redirect.github.com/groovy/GMavenPlus/issues/380";>#380</a>)</li>
   <li>Additional commits viewable in <a 
href="https://github.com/groovy/GMavenPlus/compare/4.3.1...5.0.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.codehaus.gmavenplus:gmavenplus-plugin&package-manager=maven&previous-version=4.3.1&new-version=5.0.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to