Closed ncordon closed 8 months ago
Uses the maven-metadata file to generate the versions.json instead of parsing the html.
maven-metadata
html
I've tried (with JVM 8) doing:
mkdir -p build ./gradlew versions
and it correctly generates a build/versions.json file that contains the 5.15.0 entry:
build/versions.json
{ "neo4j": "5.15.0", "neo4jVersion": "5.15.0", "apoc": "5.15.0", "version": "5.15.0", "url": "https://github.com/neo4j/apoc/releases/5.15.0", "homepageUrl": "https://github.com/neo4j/apoc/releases/5.15.0", "jar": "https://github.com/neo4j/apoc/releases/download/5.15.0/apoc-5.15.0-core.jar", "downloadUrl": "https://github.com/neo4j/apoc/releases/download/5.15.0/apoc-5.15.0-core.jar", "sha1": "f76b53599c9d0ca80a3643f489a0f662de9563c2", "sha256": "0c7a834d74948121666164b8f0db484e328219ec9522ae3fb5d07e05fe9ac755", "md5": "10e577a9cd887982b88d68003f8bb079", "config": { "+:dbms.security.procedures.unrestricted": [ "apoc.*" ] } }
Because that's a better source of truth. Right now https://repo1.maven.org/maven2/org/neo4j/neo4j-kernel/maven-metadata.xml is showing 5.15.0 but there's no 5.15.0 listed under https://repo1.maven.org/maven2/org/neo4j/neo4j-kernel/
What
Uses the
maven-metadata
file to generate the versions.json instead of parsing thehtml
.I've tried (with JVM 8) doing:
and it correctly generates a
build/versions.json
file that contains the 5.15.0 entry:Why
Because that's a better source of truth. Right now https://repo1.maven.org/maven2/org/neo4j/neo4j-kernel/maven-metadata.xml is showing 5.15.0 but there's no 5.15.0 listed under https://repo1.maven.org/maven2/org/neo4j/neo4j-kernel/