Getting UNRESOLVED DEPENDENCIES, FAILURE: Build failed with an exception

Hi all ,

i’m trying to dynamically generate the manifest for a jar file, in a multi-project build.

I am using an example that I found here: http://www.prait.ch/wordpress/?p=640 which uses the afterEvaluate context to grab dependencies, and add them to the manifest.

I have several projects in the build, one of the simplest works fine (it has inter-project dependencies, only dependencies on external jar files). However, when I try the same with another project which itself depends on other projects, I get errors:

here in manifest making
here in afterEvaluate
:: problems summary ::
:::: WARNINGS
  ::::::::::::::::::::::::::::::::::::::::::::::
    ::
        UNRESOLVED DEPENDENCIES
       ::
    ::::::::::::::::::::::::::::::::::::::::::::::
    :: major#external;unspecified: configuration not found in major#external;unspecified: 'default'. It was required from major#api;unspecified compile
    ::::::::::::::::::::::::::::::::::::::::::::::
      FAILURE: Build failed with an exception.
  * Where:
Build file '/mnt/data/dev/testbuild/major/MyProj/build.gradle' line: 112
  * What went wrong:
Could not resolve all dependencies for configuration ':MyProj:compile':
    - unresolved dependency: major#external;unspecified: configuration not found in major#external;unspecified: 'default'. It was required from major#api;unspecified compile

The error output does not make much sense to me, with its hashes and semi-colons, … “unspecified” and the like…

What is going on?

thanks for any hints.

sean

This is a very old version of Gradle.

Is there any chance you can try with a recent version?