gnodet opened a new pull request, #24466:
URL: https://github.com/apache/camel/pull/24466

   ## Summary
   
   - Commit cdaf5a8b8b4 (CAMEL-19807) introduced Javadoc line wrapping and 
string concatenation alignment in `BeansDefinition.java` and 
`XmlRoutesBuilderLoader.java` that don't match what `mvn formatter:format` 
produces.
   - The CI step **"Fail if there are uncommitted changes"** detects these 
differences after the build runs the formatter, causing **all PR builds to 
fail** regardless of what the PR changes.
   - This PR runs `mvn formatter:format impsort:sort` on the two affected 
modules to align the committed code with the project's formatting rules.
   
   ## Changes
   
   **`BeansDefinition.java`** — Javadoc `@deprecated` tag line wrapping (2 
occurrences):
   ```diff
   -     * @deprecated use standard Camel XML DSL (camel-xml-io) instead of 
legacy Spring/Blueprint XML.
   -     *             This feature will be removed in a future release.
   +     * @deprecated use standard Camel XML DSL (camel-xml-io) instead of 
legacy Spring/Blueprint XML. This feature will
   +     *             be removed in a future release.
   ```
   
   **`XmlRoutesBuilderLoader.java`** — String concatenation `+` alignment:
   ```diff
   -                                + " Migrate to standard Camel XML DSL 
(camel-xml-io).");
   +                         + " Migrate to standard Camel XML DSL 
(camel-xml-io).");
   ```
   
   ## Test plan
   
   - [x] Verified the exact same diff appears in CI logs of failing PRs (e.g. 
[PR #24462 build 
log](https://github.com/apache/camel/actions/runs/28792084146/job/85373071265))
   - [x] Ran `mvn formatter:format impsort:sort` locally and confirmed `git 
status` is clean after
   - [ ] CI build on this PR should pass the "Fail if there are uncommitted 
changes" step
   
   _Claude Code on behalf of [@aldettinger](https://github.com/aldettinger)_
   
   🤖 Generated with [Claude Code](https://claude.ai/code)


-- 
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