-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Tomcat10 support latest master #4342
Conversation
52127f5
to
e64463e
Compare
487eddf
to
b7b7328
Compare
b7b7328
to
75af30a
Compare
c42c696
to
fd7a58b
Compare
Java dependency diffOmitted due to character limit. See workflow artifacts for full diff file. Module detailsOmitted due to character limit. See workflow artifacts for full diff file. ChecklistUnique changesUnique additions
Developer commentsGlossaryLimitations
Emojies
|
Dependencies license checkUpgrades
Additions
|
Notes for the ReviewerThe ee pipeline build failure looks unrelated to the changes. Assigning for the review. |
fd7a58b
to
fcc6c0c
Compare
<include>jakarta.xml.bind:jakarta.xml.bind-api:jar</include> | ||
|
||
<!-- Resteasy --> | ||
<include>org.jboss.resteasy:resteasy-*</include> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line could potentially include more artifacts than neccessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After keeping only reasteasy-core from all the resteasy artifacts, no issue could be identified at the moment.
References:
Keep only resteasy-core
UpdateContext: Removed all resteasy depencencies except
|
The inclusion contains also the transitive dependencies
Assigning for a second review round |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good. Nice work!
❓Is the CI error related?
I believe we can ignore it since the respective EE-PR build passed which used the No. 48 build (latest) as a basis |
Next stepsRedo License check after the updated artifacts, collect them and send the list for license approval. |
Java dependency diffOmitted due to character limit. See workflow artifacts for full diff file. Module detailsjna:5.8.0Declared licenses:
Links: jakarta.el-api:4.0.0Declared licenses:
Links: geronimo-jta_1.1_spec:1.1.1Declared licenses:
Links:
jboss-annotations-api_1.1_spec:1.0.1.FinalDeclared licenses:
Links: jboss-ejb-api_3.1_spec:1.0.2.FinalDeclared licenses:
Links: jboss-el-api_2.2_spec:1.0.2.FinalDeclared licenses:
Links: jboss-jsf-api_2.1_spec:2.0.9.FinalDeclared licenses:
Links: jboss-interceptors-api_1.1_spec:1.0.1.FinalDeclared licenses:
Links: jboss-connector-api_1.6_spec:1.0.1.FinalDeclared licenses:
Links: jboss-servlet-api_3.0_spec:1.0.2.FinalDeclared licenses:
Links: jboss-jstl-api_1.2_spec:1.0.3.FinalDeclared licenses:
Links: serializer:2.7.1.jbossorg-2Declared licenses:
Links:
jboss-transaction-api_1.1_spec:1.0.1.FinalDeclared licenses:
Links: jboss-jaxb-api_2.2_spec:1.0.4.FinalDeclared licenses:
Links: jakarta.transaction-api:2.0.1Declared licenses:
Links: jakarta.interceptor-api:2.1.0Declared licenses:
Links: jakarta.enterprise.concurrent-api:3.0.1Declared licenses:
Links: jakarta.el-api:5.0.1Declared licenses:
Links: ChecklistUnique changesUnique additions
Developer commentsGlossaryLimitations
Emojies
|
License CheckHere is the final table with the dependencies that need approval Dependencies used for Testing
APIs
|
License Check UpdateOpened a License check ticket to request approval |
License Check UpdateThere are two dependencies that use GPL and are not allowed:
Reference: Approval Request Thread Update
Both dependencies above in their respective github repositories use GPL. It's questionable why. Verdict: These licenses are not added by the Next Steps: Find out more about the licenses of the two dependencies, figure out when they were introduced and see if they can be excluded. References: Root-cause Analysis of the Dependency Diff |
jboss-jsp-api_2.2_spec & jboss-jaxb-api_2.2_specModule: |
License Check
|
Next StepProceed with Merging. |
Root Cause Analysis of the Java Dependency DiffProblem: Root-cause
Solution: Ignore the false additions. |
Temporarily postponing the merge until all review points are covered and clarity for the version diff is restored. |
UpdateLicense check has been completed. Proceeding to merging. |
Related-to: #4387
Parent-issue: #2471