Use of 'compile' property is unclear

[dchambers]

According to the documentation, the 'compile' property can be used to configure the path to the 'retrolambda.jar' that will be used, but it's unclear what this actually means. I'd like to test a fix in retrolambda 1.1.4 (which fixes issue luontola/retrolambda#13), but I ran into these issues:

1. Maven central doesn't have either retrolambda 1.1.3 or retrolambda 1.1.4.
2. Setting the property to compile "net.orfjackal.retrolambda:retrolambda:1.1.1" (which is available in maven), didn't actually cause that version to be used.
3. Compiling retrolambda myself and setting the property to the absolute path of the 'retrolambda.jar' I'd built also had no effect, as retrolambda 1.1.2 was still used.

I assume this issue can probably be fixed by having some more explicit examples in the documentation, though I'm not sure who's responsible for deploying the retrolambda artifact to Maven Central?

[luontola]

Regarding point 1., they are in Maven Central: http://central.maven.org/maven2/net/orfjackal/retrolambda/retrolambda/

(Version 1.1.4 might not have been there when you first tried it, because there is a couple of hour delay for artifacts to show up in Central, but 1.1.3 has been there for some days already.)

[dchambers]

Ah, that much is my fault. I just always end up Googling through to this site when I'm searching for a dependency:

• http://mvnrepository.com/artifact/net.orfjackal.retrolambda/retrolambda

and I hadn't realized it was such a stale view of the world.

[luontola]

It's quite surprising how stale that site is - I didn't know it either. I search artifacts normally using http://search.maven.org/ and it's updated quite quickly.

[evant]

The compile property is supposed to work exactly like any dependency, i.e. you should be able to give it 'net.orfjackal.retrolambda:retrolambda:1.1.4' to fetch from maven central or files('path/to/retrolambda.jar') to pull it in locally. However, I can confirm that it is actually ignored and only the hardcoded path is used.

As a workaround, you can use the retrolambda configuration directly by

dependencies {
    retrolambdaConfig 'net.orfjackal.retrolambda:retrolambda:1.1.4'
}

I'm considering just making this the default way of setting it, and taking out the compile property completely.

[luontola]

Thanks. That workaround worked.

[dchambers]

Yes, that worked for me too. Our build is now passing on my machine, which is really excellent news!