-
Notifications
You must be signed in to change notification settings - Fork 31
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
AppVeyor Maven packaging fails because Maven 3.6.0 is too old #1893
Comments
Do we need to request a particular Maven version in
|
Yes, probably. ut we could also go to the latest Maven version : 3.9.6 https://repo1.maven.org/maven2/org/apache/maven/maven/3.9.6/ |
This has no consequence on what we build / deliver. It's just on how it's built... |
Good clarification. I changed the title of this issue to convey that it's not the package that fails but rather the packaging process (attempting to build the package) that fails. |
Creating this issue to continue from my comment, #1875 (comment)
Cc: @cmarchand
Maven versions in different testing environments
That same AppVeyor log linked from my last comment lists the Maven version as 3.6.0.
Meanwhile, our other test runs use Maven 3.8.7. The GitHub Actions windows-latest/java8/saxon12 session lists
while the windows-latest/java17/saxon12 session lists
and the Azure Pipelines Win_Java8 Saxon-12 log lists
History of Maven testing on AppVeyor
#664 : Introduced but disabled because Maven image wasn't available on AppVeyor
#678 : Enabled when AppVeyor had Maven image
The text was updated successfully, but these errors were encountered: