dependabot[bot] opened a new pull request, #13258: URL: https://github.com/apache/maven/pull/13258
Bumps `domtripVersion` from 1.7.0 to 1.8.0. Updates `eu.maveniverse.maven.domtrip:domtrip-core` from 1.7.0 to 1.8.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/maveniverse/domtrip/releases">eu.maveniverse.maven.domtrip:domtrip-core's releases</a>.</em></p> <blockquote> <h2>DomTrip 1.8.0</h2> <p>feat: add profile-scoped support to Plugins (forProfile)</p> <p>Mirror the profile-scoping pattern from <code>Dependencies</code> into <code>Plugins</code>:</p> <ul> <li>Add <code>contextElement</code> field + local <code>root()</code> shadow so all path-resolution calls (<code>findOrCreatePlugins</code>, <code>findOrCreateManagedPlugins</code>) automatically scope to the profile element when set</li> <li>Add <code>forProfile(String)</code> and <code>forProfile(Element)</code> factory methods</li> <li>Add local <code>updateVersionElement()</code> to resolve property references against the profile's own <code><properties></code> section rather than the project root</li> <li>Promote <code>isPropertyReference()</code> to outer <code>PomEditor</code> and add compound-property reference guard (expressions like <code>${revision}${changelist}</code> follow the literal-version branch instead of extracting a malformed key)</li> <li>Fix <code>@since</code> tags on <code>Plugins.forProfile()</code> methods: 1.2.0 → 1.8.0</li> <li>Update <code>Profiles</code> class Javadoc to reference <code>Plugins.forProfile</code></li> <li>Add class-level Javadoc to <code>Plugins</code></li> </ul> <p>Tests: 11 new tests in <code>PomEditorTest</code> covering <code>updatePlugin</code>, <code>updateManagedPlugin</code>, upsert, delete, error cases, <code>forProfile(Element)</code>, and the compound-property version guard.</p> <p>Fixes toolbox plugin-versions (and similar mojos) failing to update plugins declared inside <code><profiles>/<profile>/<build>/<plugins></code> when <code>apply=true</code>, because <code>PomEditor.plugins().updatePlugin()</code> was always targeting <code>project/build/plugins</code> regardless of where the plugin was declared.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/maveniverse/domtrip/commit/16355257b1a481d60db81050a360871ba53ee618"><code>1635525</code></a> feat: add profile-scoped support to Plugins (forProfile)</li> <li>See full diff in <a href="https://github.com/maveniverse/domtrip/compare/1.7.0...1.8.0">compare view</a></li> </ul> </details> <br /> Updates `eu.maveniverse.maven.domtrip:domtrip-maven` from 1.7.0 to 1.8.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/maveniverse/domtrip/releases">eu.maveniverse.maven.domtrip:domtrip-maven's releases</a>.</em></p> <blockquote> <h2>DomTrip 1.8.0</h2> <p>feat: add profile-scoped support to Plugins (forProfile)</p> <p>Mirror the profile-scoping pattern from <code>Dependencies</code> into <code>Plugins</code>:</p> <ul> <li>Add <code>contextElement</code> field + local <code>root()</code> shadow so all path-resolution calls (<code>findOrCreatePlugins</code>, <code>findOrCreateManagedPlugins</code>) automatically scope to the profile element when set</li> <li>Add <code>forProfile(String)</code> and <code>forProfile(Element)</code> factory methods</li> <li>Add local <code>updateVersionElement()</code> to resolve property references against the profile's own <code><properties></code> section rather than the project root</li> <li>Promote <code>isPropertyReference()</code> to outer <code>PomEditor</code> and add compound-property reference guard (expressions like <code>${revision}${changelist}</code> follow the literal-version branch instead of extracting a malformed key)</li> <li>Fix <code>@since</code> tags on <code>Plugins.forProfile()</code> methods: 1.2.0 → 1.8.0</li> <li>Update <code>Profiles</code> class Javadoc to reference <code>Plugins.forProfile</code></li> <li>Add class-level Javadoc to <code>Plugins</code></li> </ul> <p>Tests: 11 new tests in <code>PomEditorTest</code> covering <code>updatePlugin</code>, <code>updateManagedPlugin</code>, upsert, delete, error cases, <code>forProfile(Element)</code>, and the compound-property version guard.</p> <p>Fixes toolbox plugin-versions (and similar mojos) failing to update plugins declared inside <code><profiles>/<profile>/<build>/<plugins></code> when <code>apply=true</code>, because <code>PomEditor.plugins().updatePlugin()</code> was always targeting <code>project/build/plugins</code> regardless of where the plugin was declared.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/maveniverse/domtrip/commit/16355257b1a481d60db81050a360871ba53ee618"><code>1635525</code></a> feat: add profile-scoped support to Plugins (forProfile)</li> <li>See full diff in <a href="https://github.com/maveniverse/domtrip/compare/1.7.0...1.8.0">compare view</a></li> </ul> </details> <br /> 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]
