Closed jdmarques closed 4 months ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
There have been some conda-forge specific issues here in the past. What we really need here are better tests.
My bandwidth as a maintainer is limited until mid-July. I would be willing to do a trial in late July.
If you would like to see proceed before then, please add additional tests across multiple platforms, including Windows.
There have been some conda-forge specific issues here in the past. What we really need here are better tests.
My bandwidth as a maintainer is limited until mid-July. I would be willing to do a trial then
If you would like to see proceed before then, please add additional tests across multiple platforms.
See https://github.com/conda-forge/maven-feedstock/pull/24#issuecomment-1588465291
hello @mkitti, from what I see in https://github.com/conda-forge/maven-feedstock/pull/24#issuecomment-1588465291 what fixed the issue was the flag to ignore the cleanup errors "-Dmaven.clean.failOnError=false" and not the version limit. Am I missing something?
From the CI logs the build from this PR run with "openjdk: 22.0.1-h57928b3_0 conda-forge" just fine. I can try to add a test but I need more information about the actual issue.
I have some bandwidth to try this now, and plan to merge in a few hours.
Pinging @ctrueden and @hinerm
@conda-forge-admin, please rerender
thanks @mkitti
Hello, I think you should remove this upper limit on the OpenJDK. From the Maven documentation, the limit is only on JDK 8, " Maven 3.9+ requires JDK 8 or above to execute" source: https://maven.apache.org/download.cgi
why set this upper bound limit?
Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)