[MENFORCER-427] New rule to ban dynamic versions by kwin · Pull Request #187 · apache/maven-enforcer (original) (raw)

• [1.0.0,1.0.0] is currently invalid and leads to org.apache.maven.artifact.versioning.InvalidVersionSpecificationException: Range cannot have identical boundaries: [1.0,1.0].

This is strange because 1.0 is resolved to this...I wonder why this range is logically invalid.

• [1.0] leads to version resolving (although redundant) when used in a dependency and therefore always means overhead during build and dependency on metadata. I would rather ban this as well. This should be replaced by soft requirement 1.0 to speed up the build! Is there already an issue related to this? According to https://maven.apache.org/pom.html#Dependency_Version_Requirement_Specification the fixed hard requirement may make sense for some edge cases, but as long as this leads to version resolving I would recommend not to rely on it.

Well, [1.0] exists for a reason. I think it is parsed to [1.0,1.0] then of course it incurs resolution. Hard for me to tell whether this should be blocked or not. If you want to block this, fine. Add a comment about the situation.