Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move off direct SecDispatcher use #1848

Merged
merged 1 commit into from
Jan 2, 2025

Conversation

cstamas
Copy link
Contributor

@cstamas cstamas commented Jan 1, 2025

Use the "official" way instead, and it solves Maven 4 support as well.

Changes:

  • align Maven deps (maven-compat was 3.0 while maven-core 3.8.1)
  • since Maven 3.9 plexus util is NOT provided
  • do not use directly SecDispatcher, use Maven APIs instead
  • fix UTs

Use the "official" way instead, and it does
provide backward compatibility support as well.
@cstamas
Copy link
Contributor Author

cstamas commented Jan 1, 2025

An alt fix could be to detect is Mojo running in Maven 4, and if so, simply "do nothing" (make decrypt method no-op), as Maven 4 on boot decrypts everything in effective settings, and there is no need to decrypt anything (as long as thing comes from effective settings).

As explained on Maven ML https://lists.apache.org/thread/4fywo93s80fhmcj58cg9lvj5s61497tc

@rohanKanojia rohanKanojia merged commit 1b28e22 into fabric8io:master Jan 2, 2025
18 of 23 checks passed
@rohanKanojia
Copy link
Member

@cstamas : Thanks a lot!

@cstamas cstamas deleted the move-off-sec-dispatcher branch January 2, 2025 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants