-
Notifications
You must be signed in to change notification settings - Fork 33
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
Improve resource resolution #161
Comments
@basil If you are willing and able to:
|
How is the byte size of |
It is a way to see if that jar was deployed without asking if that jar was deployed :) The idea is force examination of the system instead of examination of ones memory of what was deployed. I trust you did it correctly but want to verify it. We already have 2 tickets of users falling in to this trap (which I need to fix) and I want to rule this out as a problem. If that jar is missing there are some silent failures that are only shown with debugging on. As an example:
|
I support users in an open-source project, so I can understand this perspective. This also means we can skip the indirection and I can explain to you how to reproduce the problem from scratch. Download the latest Jenkins weekly release, then start it with Java 11, 17, or 21 with Once Jenkins is up and running, go to Manage Jenkins, System. Under "System Admin e-mail address", set an address like Once Jenkins is configured, create a new Freestyle project. As an example, I often create a test project that clones https://github.com/basil/simple-maven-project-with-tests.git and runs Now run the job in Jenkins, and at the end it should send you an email. This should work before proceeding to the next step, so if it fails, do whatever it takes to get it to work, or contact me for help. Now, once it is working, you can break it by removing my workaround as follows. Clone https://github.com/jenkinsci/jakarta-mail-api-plugin and remove the workaround with
|
@basil Thanks for the reproducer! This will save me a ton of time. You are a gentleman and a scholar. For my own notes this is the project console output of the basic test to get a weekly build working with no changes.
Here is the launch console output for jenkins.war running with activation debugging for the above console log:
TODO notes for myself:
|
Notes to myself:
|
Jenkins Dependencies and Class Loading shows a classloader tree where for example JAF-API is not able to locate JakartaMail (plug-in C) mailcap.file resolved from JAF-API (plugin A) because the context classloader is
Jenkins core
. See: #145 (comment)Mail uses JAF but Mail jar contains the mailcap resource file.
More thought needs to be put in to this but there are some options:
The text was updated successfully, but these errors were encountered: