asciidoctor / asciidoctor-gradle-examples

A collection of example projects that demonstrates how to use the Asciidoctor Gradle plugin
http://asciidoctor.github.io/asciidoctor-gradle-examples
Other
147 stars 136 forks source link

asciidoc-diagram-to-html-example failing to build #38

Closed GregDThomas closed 5 years ago

GregDThomas commented 7 years ago

If you simply download the examples as a ZIP, and try the asciidoc-diagram-to-html-example the following occurs:

C:\Greg\asciidoc-diagram-to-html-example>gradlew asciidoctor
:jrubyPrepare FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jrubyPrepare'.
> Could not resolve all dependencies for configuration ':gems'.
   > Could not resolve rubygems:asciidoctor-diagram:[1.5.4,1.5.4].
     Required by:
         :asciidoc-diagram-to-html-example:1.0.0-SNAPSHOT
      > Could not resolve rubygems:asciidoctor-diagram:[1.5.4,1.5.4].
         > Failed to list versions for rubygems:asciidoctor-diagram.
            > Could not list versions using M2 pattern 'http://rubygems.lasagna.io/proxy/maven/releases/[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]'.
               > Could not GET 'http://rubygems.lasagna.io/proxy/maven/releases/rubygems/asciidoctor-diagram/'.
                  > rubygems.lasagna.io:80 failed to respond

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.587 secs

From the looks of it, there's something more fundamental going wrong with the setup, but I don't know enough to be able to analyse any further, so any ideas?

Thanks

GregDThomas commented 7 years ago

Whatever the problem was, it's resolved itself. It seems http://rubygems.lasagna.io/ went AWOL for while ...

lenalebt commented 7 years ago

It is away again, can we re-open this? Away since at least yesterday.

GregDThomas commented 6 years ago

Still happening this morning, so re-opening

GregDThomas commented 6 years ago

OK - it's back again. I'll leave this issue open though - clearly it's not a one-off issue, so some sort of long-term solution should probably be put in place.

GregDThomas commented 6 years ago

(started happening again sometime over this weekend)

DennisRippinger commented 6 years ago

My temporary fix was to download the gem file directly and link the gem via a files directive:

dependencies {
    gems files('libs/asciidoctor-diagram-1.5.4.gem')
}
GregDThomas commented 6 years ago

Thanks; that temporary work-around was good for me, too.

[Sadly, I'm all too aware that "Nothing is so permanent as a temporary ...." - Milton Friedman, IIRC]

marhan commented 6 years ago

The server is offline again: http://rubygems.lasagna.io/proxy/maven/prereleases/rubygems.

regevbr commented 6 years ago

Offline again...

nibin commented 6 years ago

offline again

mojavelinux commented 6 years ago

I really don't understand why this is relying on a prereleases repository. That's part of the problem. It should be using http://rubygems-proxy.torquebox.org/. That's the most stable endpoint.

piersf commented 6 years ago

Seems like http://rubygems.lasagna.io/proxy/maven/releases/rubygems/rspec/maven-metadata.xml is offline again. It's been offline for the past 3 days.

Anybody knows if it has moved somewhere else or what is going on?

piersf commented 6 years ago

For anyone encountering the same issue with rubygems.lasagna.io being down, i was able to find a solution which i posted here: https://github.com/jruby-gradle/jruby-gradle-plugin/issues/329

gavenkoa commented 6 years ago

http://rubygems.lasagna.io/ is down? Add to you build.gradle:

repositories {
    maven { url "http://rubygems-proxy.torquebox.org/releases" }
}
mojavelinux commented 5 years ago

It looks like the JRuby plugin is going to switch back to using the Torquebox repository, which is maintained by Red Hat. That should put an end to this thrashing.

rwinch commented 5 years ago

Fixed via #48

GregDThomas commented 5 years ago

Closing this issue now it's been resolved,