Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Abandoned
-
1.4.7
Description
I would like to use the Buildr auto-extract + cache into local repository functionality with a rather funny setup.
I'm using a library called libgdx, Android / HTML5 game library (http://libgdx.googlecode.com/files/libgdx-0.9.4.zip). This library is not on Maven Central, but is distributed as a zip containing 9 .jars on the top level of the zip hierarchy.
A selection of these JARs are required to build my project successfully. Thus, I ensure that I declare the JARs as constants and tell Buildr that they can be found in the libgdx-0.9.4.zip URL:
```
LIBGDX = "com.badlogic.gdx:gdx:jar:0.9.4"
LIBGDX_OPENAL = "com.badlogic.gdx:gdx-openal:jar:0.9.4"
... (7 more)
download artifact(LIBGDX) => "http://libgdx.googlecode.com/files/libgdx-0.9.4.zip"
download artifact(LIBGDX_OPENAL) => "http://libgdx.googlecode.com/files/libgdx-0.9.4.zip"
... (7 more)
```
Project declarations are as standard. For the sakes of illustration, try:
```
...
compile.with LIBGDX, LIBGDX_OPENAL
...
```
`buildr compile` succeeds in a short time, downloading the zip if it wasn't found, extracting, and publishing the named JARs into the local repository. The next time this is invoked, the local repository is inspected and are found, so no zip download is initiated. This is perfect behaviour.
`buildr eclipse` and `buildr idea` however seem to totally ignore the local repository and just goes to download the listed artefacts in the sequence specified. This is disastrous for the build especially when all of the 'download artefact' directives point to the exact same 26MB zip!
Please ensure commands that trigger a zip download inspects the local repository first!