buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hok Shun Poon (JIRA)" <>
Subject [jira] [Created] (BUILDR-644) 'buildr eclipse' or 'buildr idea' tasks downloads artefacts multiple times.
Date Thu, 07 Jun 2012 18:42:23 GMT
Hok Shun Poon created BUILDR-644:

             Summary: 'buildr eclipse' or 'buildr idea' tasks downloads artefacts multiple
                 Key: BUILDR-644
             Project: Buildr
          Issue Type: Bug
          Components: Dependency management
    Affects Versions: 1.4.7
         Environment: Ruby Version: ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin10.0]

Java Version: java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-10M3635)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
            Reporter: Hok Shun Poon
            Priority: Minor

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 (
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 = "com.badlogic.gdx:gdx:jar:0.9.4"
LIBGDX_OPENAL = "com.badlogic.gdx:gdx-openal:jar:0.9.4"
... (7 more)
download artifact(LIBGDX) => ""
download artifact(LIBGDX_OPENAL) => ""
... (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

`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!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message