-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Fix POM #623
Fix POM #623
Conversation
Update two dependencies (logback, schematron)
What are the changes (the diff shows only red and green) and we had one POM change request which unfortunately consistently failed on that -- will the maven publish still work afterwards? |
Update some versions (logback, assertj-core)
Find patch attached. POM.patch With regards to motivation for modifying the Maven config: Find log files attached, resulting from a compilation run against the current master. mustangproject-master-logs.zip With regards to build issues: As far as I see there are two reasons why the build fails:
This one has been fixed with PR#626. The issue has nothing to do with PR#623.
For me it works:
Find log files attached. Mustang-CLI-2.15.3-SNAPSHOT-logs.zip So, this issue has nothing to do with PR#623 as well. |
Update certain dependencies (core-jakarta)
Update certain dependencies (logback)
Update project.parent.version
Update project.parent.version
Update project.parent.version
Please do not change the tab-size. This makes it nearly impossible to find all changes. |
Probably something like spotless should be added to the code to ensure consistent formatting.
Edit: In GitHub you can suppress whitespace changes when viewing the diff (at the top of the page, where you can select inlined of sid-by-side view). |
I did not change the tab size. What you're claiming about is the missing normalization of the original Maven configuration. |
Yes, I agree. I have added the openrewrite plugin to my pull request:
This way, the Java sources and the Maven configuration would be normalized. |
The tab-size has been changed from 4 to 8 characters. Please use 4 characters. |
I do not want to discuss about white space. I would like to focus on the real issues. Find inspection results attached: (I attach the XML version only because the other versions HTML and JSON are too big.) I have filed another pull request #644. Therefore, I am going to close this one. |
See above. |
Modernize and standardize POM, concentrate version management into top-level POM