Tests fail if there are any connectivity problems about jruby-gradle-plugin

[rtyler]

I suppose a question for you @ysb33r would be, is there any reason not to always run the tests as if they are "offline"?

[ysb33r]

Some tests need to connect to the internet to download gems as part of the test. When you are testing in an environment that does not have network connectivity run with ./gradlew --offline. Try that to see if it works for now.

(Having said that one test in JRubyPluginTest will still fail - I need to fix that)

[rtyler]

@ysb33r the --offline flag definitely lets the tests run. Do you think tests passing with --offline is sufficient for a release

[ysb33r]

I would say no, but I would also wonder how you could build a released version without network connectivity?

[rtyler]

@ysb33r I'm getting the above test failure very consistently from my laptop (the one I'm typing these comments from) so I don't think it's an online/offline thing. I'm in the chatroom now if you want to discuss further there

[ysb33r]

I'll give this a bit of think. A good starting point is https://github.com/robfletcher/gradle-compass/blob/master/gradle/integration-tests.gradle.

What I want to avoid is someone building a release without running the integration tests, but I also want to give people to options to skip the integration tests in normal development.

Maybe just allowing something like ./gradlew -PinterTest=0 to skip integration tests can do the trick.

[I'm leaving the option that ./gradlew --offline will avoid integration tests, but that is for the reason that --offline means we are using Gradle without a network connection and as such no network related activities should occur, including looking for repositories].