devareddy05 opened a new pull request, #23439: URL: https://github.com/apache/camel/pull/23439
# Description Fixes https://issues.apache.org/jira/browse/CAMEL-22504. `org.apache.camel.component.jasypt.Main` — the command line entrypoint that lets the `camel-jasypt` jar be invoked directly (e.g. via JBang) to encrypt or decrypt property values — is a small but real maintenance burden because it duplicates functionality already provided by the upstream supported [Jasypt CLI](http://www.jasypt.org/cli.html). Per the Jira description, the goal is to deprecate **only** the CLI entrypoint (not the component itself — runtime property-source decryption is unaffected). ## Changes * `Main.java` — annotated `@Deprecated(since = "4.21")` with a class-level Javadoc explaining the replacement. * `MainTest.java` — added `@SuppressWarnings("deprecation")` so the existing unit tests for `Main` keep compiling cleanly without contributing new deprecation noise to the build. * `jasypt.adoc` — added an asciidoc `WARNING` admonition to the Tooling section pointing readers at the Jasypt CLI. * `camel-4x-upgrade-guide-4_21.adoc` — added a "Deprecation of camel-jasypt CLI entrypoint" entry alongside the other 4.21 deprecations, with a link to the Jasypt CLI replacement. ## Out of scope This PR does **not** remove the `<mainClass>` entry in `camel-jasypt/pom.xml`, the runnable-jar manifest, or the `Main` class itself. The Jira's "eventually drop" follow-up is intentionally left for a later release once the deprecation window has elapsed. ## Verification * `mvn -pl components/camel-jasypt formatter:format impsort:sort` — clean (`Already Sorted: 12`, `Formatted: 0`). * `mvn -pl components/camel-jasypt -am install -DskipTests` — BUILD SUCCESS. * `mvn -pl components/camel-jasypt test` — **Tests run: 25, Failures: 0, Errors: 0, Skipped: 0** (all 6 `MainTest` cases still pass under the `@SuppressWarnings`). # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL-22504) filed for the change. # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn formatter:format impsort:sort` locally on the affected module (no changes needed). -- 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]
