dependabot[bot] opened a new pull request, #16340:
URL: https://github.com/apache/camel/pull/16340

   Bumps 
[io.github.ascopes:protobuf-maven-plugin](https://github.com/ascopes/protobuf-maven-plugin)
 from 2.6.6 to 2.7.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/ascopes/protobuf-maven-plugin/releases";>io.github.ascopes:protobuf-maven-plugin's
 releases</a>.</em></p>
   <blockquote>
   <h2>v2.7.0</h2>
   <p>A fairly big release with lots of bug fixes and a couple of new 
features.</p>
   <h2>New features</h2>
   <ul>
   <li>Introduced an experimental incremental compilation mode. The aim is to 
avoid regenerating the entire codebase with protoc if only a subset of sources 
have changed. This should significantly speed up development build times on 
codebases with large numbers of proto files.
   <ul>
   <li>Set 
<code>&lt;incrementalCompilation&gt;true&lt;/incrementalCompilation&gt;</code> 
or set <code>protobuf.compiler.incremental</code> to <code>true</code> to opt 
into using it.</li>
   <li>This feature is disabled by default to avoid risking breaking existing 
builds.</li>
   <li>Since this is experimental, the feature may be subject to change in how 
it works internally for future bugfixes.</li>
   <li>This mechanism tracks dependencies and sources between builds and 
selectively recompiles only the files that may need changes. It is currently 
unable to act 'intelligently' respecting the logical dependency graph between 
files but this may be improved in the future.</li>
   <li>Integrity of existing generated sources is not tracked at this time, but 
may be in the future.</li>
   <li>This does not affect how the maven-compiler-plugin compiles sources.</li>
   <li><code>mvn clean</code> will purge the cache and trigger a full 
rebuild.</li>
   </ul>
   </li>
   <li>Archive extraction has been reworked and now supports loading JARs 
recursively from other JARs (and other archive types that were already 
supported).</li>
   </ul>
   <h2>Bugfixes and performance improvements</h2>
   <ul>
   <li>Fixed a bug that caused a NullPointerException if dependencies were 
added with invalid classifiers that did not correspond to a real artifact. 
Correct errors are now raised to the user in this case.</li>
   <li>Fixed a bug where fatal artifact resolution errors were being 
ignored.</li>
   <li>Fixed a bug where non-fatal artifact resolution errors were not being 
logged. These are now emitted as warning logs.</li>
   <li>Fixed a bug where ConcurrentExecutor was not a singleton, which meant 
multiple threadpools were being initialised.</li>
   <li>Fixed a bug where dependency digests used paths rather than URIs for 
their seed, which could create a case where two JARs with nested dependencies 
produce a duplicate digest and thus break the import path for protoc.</li>
   <li>Generated source directories are now registered prior to invoking protoc 
rather than after. This supports incremental compilation by allowing the 
maven-compiler-plugin to still see all sources correctly if only a subset or no 
generated files change between builds.</li>
   <li>ConcurrentExecutor now uses a cached thread pool rather than a 
fixed-size thread pool if virtual threads are unavailable on the platform. The 
change should improve dependency analysis times.</li>
   <li>Fixed debug logs for paths discovered in JARs so that they use a 
representation that makes them explicitly clear to the user that they are a JAR 
virtual file system.</li>
   <li>Fixed incorrect logger name on proto source resolver components.</li>
   </ul>
   <h2>Internal improvements</h2>
   <ul>
   <li>Updated logging to be clearer in several places.
   <ul>
   <li>Some log entries have been removed.</li>
   <li>Some log entries have changed between debug, trace, and info levels.</li>
   </ul>
   </li>
   <li>Moved source code resolution and import resolution to a new set of 
components to assist in code maintainability in the future.</li>
   <li>System path order is now guaranteed at compile time rather than being an 
implicit assumption. This logically does not change the existing behaviour or 
fix any bugs but reduces the risk of regression in the future.</li>
   <li>Integration test dependencies have been refactored to use a common setup 
POM, reducing the work needed to keep dependencies up to date in the 
future.</li>
   <li>Integration test common dependencies are now managed by Dependabot for 
weekly updates.</li>
   <li>Renamed several internal components and moved items between packages to 
improve code clarity and structure.</li>
   <li>Fixed a number of warnings in unit tests.</li>
   <li>Fixed a few typos in logs and exception messages.</li>
   <li>Improved JVM protoc plugin resolution exception handling.</li>
   <li>The archive extractor has been inlined and allowed the removal of 
duplicate code.</li>
   <li>Upgraded test dependencies to the latest version.
   <ul>
   <li>Includes Scala, gRPC, reactor, and protobuf libraries.</li>
   <li>Test against Kotlin v2 rather than Kotlin v1.</li>
   </ul>
   </li>
   </ul>
   <p><strong>Full Changelog</strong>: <a 
href="https://github.com/ascopes/protobuf-maven-plugin/compare/v2.6.6...v2.7.0";>https://github.com/ascopes/protobuf-maven-plugin/compare/v2.6.6...v2.7.0</a></p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/9aaabc1d84c1a190217ce6b0e087ca86e84e309f";><code>9aaabc1</code></a>
 [maven-release-plugin] prepare release v2.7.0</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/b09f452adc2d7e472afe24cd29ed23e9eac303bb";><code>b09f452</code></a>
 Merge pull request <a 
href="https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/464";>#464</a>
 from ascopes/dependabot/maven/protobuf-maven-plugin/s...</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/88df086eced512d03bcb1ce8b78ce5ab02f5f3a0";><code>88df086</code></a>
 Update install-protoc-to-github-runner.sh to use protoc 4.28.3</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/56ca667dddcb23307041d62a72cc05614a9e5a1e";><code>56ca667</code></a>
 Merge pull request <a 
href="https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/463";>#463</a>
 from ascopes/dependabot/maven/main/com.fasterxml.jack...</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/92eba654b7143030ebefa508e22d1018a12a604f";><code>92eba65</code></a>
 Update README.md with new features</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/720a4d31cd5f2b12f655471152c6113d25a74db6";><code>720a4d3</code></a>
 Update ProtobufBuildOrchestrator.java logging for registrar operations to 
log...</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/d2f14d03f1eb1d6c0e47ae411f708d34a329b4ef";><code>d2f14d0</code></a>
 Convert timing logic in IncrementalCacheManager to use debug logs</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/92a1bce1c59a85f1147449d3558f09fb99756526";><code>92a1bce</code></a>
 Bump com.google.api.grpc:proto-google-common-protos</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/3659564f14e679a9634695fc4e1d0f2aa3ad54ff";><code>3659564</code></a>
 Bump com.fasterxml.jackson:jackson-bom from 2.16.1 to 2.18.1</li>
   <li><a 
href="https://github.com/ascopes/protobuf-maven-plugin/commit/0ddce2b6a314095e4984f8f183f8221ddf8ee2ec";><code>0ddce2b</code></a>
 Merge pull request <a 
href="https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/459";>#459</a>
 from ascopes/feature/GH-438-incremental-compilation</li>
   <li>Additional commits viewable in <a 
href="https://github.com/ascopes/protobuf-maven-plugin/compare/v2.6.6...v2.7.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.github.ascopes:protobuf-maven-plugin&package-manager=maven&previous-version=2.6.6&new-version=2.7.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 merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@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