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

   The `route-parser` plugin (`camel route-parser`, since 4.17) parses Java 
routes with camel-route-parser (Roaster/JDT) and prints the route structure. 
`camel cmd route-structure MyRoute.java` prints the same tree, read with the 
Java DSL parser of camel-java-io once #27715 (CAMEL-25565) is in, and it works 
for YAML and XML too. So this PR removes the plugin:
   
   - the `camel-jbang-plugin-route-parser` module, and its entries in 
`dsl/camel-jbang/pom.xml`, `parent/pom.xml`, `bom/camel-bom/pom.xml` and 
`coverage/pom.xml`;
   - `PluginType.ROUTE_PARSER`;
   - the `camel route-parser` command page, its row in the commands index, and 
its row in the plugin table of `camel-jbang-projects.adoc`;
   - the comment about it in the launcher pom.
   
   camel-route-parser itself stays, since camel-report-maven-plugin and IDE 
tooling use it.
   
   A user who installed the plugin keeps it as an entry in their plugin config, 
which the CLI then treats like any other non-Camel plugin. The new 4.24 
upgrade-guide entry says to use `camel cmd route-structure` and to remove the 
plugin with `camel plugin delete route-parser`. 
(`camel-4x-upgrade-guide-4_24.adoc` is new here, as in #27679, #27681, #27714, 
#27715 and #27717; whichever is merged later keeps the header once and all 
sections.)
   
   Please merge this after #27715, so `route-structure` reads Java sources 
without compiling them when the plugin is gone. The camel-sbom files still list 
the artifact; the SBOM regen job updates them.
   
   Checked: camel-jbang-core and camel-launcher build, the plugin and 
CamelJBangMain tests pass (28), and nothing else in `dsl/` or the docs refers 
to the plugin.
   
   Fixes [CAMEL-25587](https://issues.apache.org/jira/browse/CAMEL-25587)
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-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