Open galtm opened 4 months ago
Do we need to request a particular Maven version in appveyor.yml
, such as by adding a MAVEN_VERSION
line as below?
environment:
MAVEN_VERSION: 3.8.7
matrix:
# Non-mainstream jobs are not included in favor of GitHub Actions and Azure Pipelines
- XSPEC_TEST_ENV: saxon-12
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...
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.
To enable #1833 to avoid this failure, I disabled the Maven operations in AppVeyor (ee4ba74e879ba2a5cf5466a7373ce0d0e84971c7) as part of that PR. This issue can remind us to re-enable it after we find a solution.
Creating this issue to continue from my comment, https://github.com/xspec/xspec/pull/1875#issuecomment-2010407662
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