-
Notifications
You must be signed in to change notification settings - Fork 69
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
jQAssistant dependency analysis results #687
Comments
Contains:
|
Contains:
|
Contains:
|
@edburns and @arjantijms: As requested, here are the results of the jQA runs. The current results are all from Maven Central and using the new jQA 2.0.1 Maven plugin. |
Contains:
Note: Were parts missing, the following issue results are limited, because it is a single element with no dependencies, but the Specification Dependency Diagram still shows this. |
Contains:
|
Contains:
|
Contains:
|
Contains:
|
Contains:
|
@edburns, @arjantijms: I started to create a report that covers the CN4J umbrella specs results and planning, which can help to check the waves for releasing and showing some of the current issues regrading depedencies. Updates for a potential Jakarta Platform 10.0.1 Patch Release that shows the additional TCK dependencies besides the API dependencies will follow soon. |
@edburns, @arjantijms: Here is the updated report, where the waves can be derived from: |
Contains:
|
Here is an updated report: |
Now that #729 has been merged, this particular issue can be closed. We do need continual analysis such as @JanWesterkamp-iJUG has been doing here as part of the maintenance lead role, but that role is still being discussed on the platform-dev mailing list. I will leave it to the person filling that role to decide how and where to manage this. |
@edburns, I will need to reopen this issue, as I do the jQA runs here and adding the summaries in the CN4J Report. Creating allways new issues for additional jQA results creates a lot of overhead on my side, as these issues need a new introduction and updates on all referenced issues then. I hope this reopening does not confuse the DevOps board. |
@JanWesterkamp-iJUG this is a great resource! Is there any way to provide the graphs in a way that they are more readable? The colored graph, figure 6, is still unreadable at 1000x magnification (the highest zoom ratio I could apply in my browser). |
May be another PDF viewer (from the OS or another Browser) allows higher zoom ratios? I think I did not published the manually editied (colored) graphs yet, but I can fix that - at the end I want to publish the hole project somewhere, so you get all the source and it's possible to contribute there then. The jQA results can be generated with the jQA demo project (linked at the beginning of the report). Of course, the final solution might be to have the jQA analysis been done with every change, staged release for the reviewers and using it to check some contraints automatically. |
20230802 01.zip
20230804 01.zip
20230809 01.zip
20230827 02.zip
20230828 01.zip
|
Updated version with filtered views for umbrella specs (@edbratt, I hope his helps to show some details without the need to zoom to much) and typos fixed. |
Updated version: |
Contains (manually edited):
@edbratt, as announced here is the PlantUML and SVG version of the originally planed Patch Release, which contains also TCK dependencies from the report. |
This issue contains (manually) generated dependency analysis results from jQA.
This is a follow up from the jakartaee/jakartaee-api#125 and #681 created to support the Jakarta EE 10 Release.
The project to analyse Jakata EE is maintained here and was updated recently to use the new maven plugin versions.
The reports can be found in the jqassistant/report folder subdirectories, interesing might be especially:
Unfortunately I can not upload the SVGs here to show them directly, because GitHub modifies them then (!).
AB#6
The text was updated successfully, but these errors were encountered: