Remove the maven.version.range
declaration in pom.xml
to avoid contributors compiling with Maven 4.0.0-beta3
?
#32568
Labels
Feature Request
For English only, other languages will not be accepted.
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Is your feature request related to a problem?
Describe the feature you would like.
pom.xml
currently has a declaration formaven.version.range
, seeshardingsphere/pom.xml
Line 54 in cf9e6a9
This is strange, because it implies that the project can be compiled by
apache/maven 4.0.0-beta3
, but this is not possible. Tested usingSDKMAN!
under Ubuntu WSL 22.04.4.sdk install java 22.0.2-graalce sdk install maven 4.0.0-beta-3 git clone git@github.com:apache/shardingsphere.git cd ./shardingsphere/ sdk use java 22.0.2-graalce sdk use maven 4.0.0-beta-3 mvn clean install -Prelease -T1C -DskipTests -Djacoco.skip=true -Dcheckstyle.skip=true -Drat.skip=true -Dmaven.javadoc.skip=true
maven.version.range
declaration inpom.xml
to avoid contributors compiling with Maven4.0.0-beta3
? After all ShardingSphere is using the Maven Wrapper which declares a specific Maven version3.8.7
.shardingsphere/.mvn/wrapper/maven-wrapper.properties
Line 18 in 74cfb23
4.0.0-beta3
. This is a bit abstract, after all, Maven4.0.0-beta3
requires the minimum JDK runtime to be JDK17.The text was updated successfully, but these errors were encountered: