-
Notifications
You must be signed in to change notification settings - Fork 55
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
Adapt to Jakarta Mail migration #1280
Conversation
…execute (default) on project sample: Managed plugin dependency io.jenkins.plugins:jakarta-activation-api not listed in test classpath of sample plugin -> [Help 1]
…execute (default) on project sample: Managed plugin dependency io.jenkins.plugins:jakarta-mail-api not listed in test classpath of sample plugin -> [Help 1]
I am not exactly sure what you are force-pushing here—that breaks the incremental review function of PRs. It should not be necessary if the PR will be squash-merged anyway, right? (Except in weird cases like when you accidentally merged in the wrong base branch and filled the commit list with junk.) |
You do not need to be
Already aware of that |
Should we do a release of this before dropping for 2.289.x and 2.303.x? |
No strong preference, but if we do, then I'd like to get #1288 in first because that builds on top of this PR. |
Adapting to: