Grails Geb plugin versions 1.0.0 and 1.0.1 JARs are broken in official artifactory

[hendrikstill]

While attempting to build a legacy Grails application, I discovered that the JAR files for versions 1.0.0 and 1.0.1 of the Grails Geb plugin in the official Grails artifactory are broken.
Instead of containing the expected plugin code, these JAR files only contain an error message.

curl https://repo.grails.org/artifactory/plugins/org/grails/plugins/geb/1.0.0/geb-1.0.0.jar 
The requested path was not found.% 

curl https://repo.grails.org/artifactory/plugins/org/grails/plugins/geb/1.0.1/geb-1.0.1.jar 
The requested path was not found.%

I understand that these dependencies are very old and shouldn't be used anymore in new projects,
but I thought it was worth mentioning this issue as it affects legacy applications that still rely on these specific versions of the Geb plugin.

[jamesfredley]

Those URLs are working. Can you check again?

[hendrikstill]

@jamesfredley

The URLs still return the plaintext The requested path was not found. and not the acutal jar file.
Artifactory UI also report the size of only 33 bytes

https://repo.grails.org/ui/repos/tree/General/plugins/org/grails/plugins/geb/1.0.1/geb-1.0.1.jar

[jamesfredley]

Ok, they did download for me, but upon opening them, they are invalid jar files. It might be the user-agent from curl that is causing JFrog Artifactory to give you the path not found message.

Can you use version 1.0.2 (it has a valid jar) or another higher version from: https://repo.grails.org/ui/native/plugins/org/grails/plugins/geb

This is likely from the bintray retirement, although I was not part of that.

The other option would be to build those old versions using the tags on https://github.com/grails/geb/tags?after=v1.1.1 and put the jar in your app.

[hendrikstill]

I believe the bintray retirement could be the reason for the broken artifacts.
If you don't plan to re-upload the broken versions, that's perfectly fine with me, as we are planning to migrate to newer versions.