Russel Winder wrote:
On Fri, 2009-08-14 at 15:36 -0400, Steve Appling wrote:
Do you actually have an empty build.gradle in the subproject? I think in our
similar cases we have not had any build.gradle in the subproject and used the
Project.subprojects method to configure it.
Yes the modules have no build.gradle -- Gradle, unlike Maven has the
ability to have the whole of the build specification in the top-level
specification file -- at least that is what the documentation says.
However I am getting the following. So there is recognition that there
is no build file in the project directory, but then it is failing for
exactly that reason :-(
It may be that someone who knows what they are doing could read the Gant
build.gradle and spot the problem instantly.
|> gradle -i :groovy1.5
Starting Build
Settings evaluated using settings file
'/home/users/russel/Repositories/Bazaar/Masters/Gant/Trunk_Development/settings.gradle'.
Projects loaded. Root project using build file
'/home/users/russel/Repositories/Bazaar/Masters/Gant/Trunk_Development/build.gradle'.
Included projects: [root project 'Trunk_Development', project
':groovy1.5', project ':groovy1.6', project ':groovy1.7']
Evaluating project : using build file
'/home/users/russel/Repositories/Bazaar/Masters/Gant/Trunk_Development/build.gradle'.
:: loading settings :: url =
jar:file:/home/users/russel/lib/Java/gradle/lib/ivy-2.1.0-rc2.jar!/org/apache/ivy/core/settings/ivysettings.xml
:: resolving dependencies :: unspecified#Trunk_Development;unspecified
confs: [classpath]
:: resolution report :: resolve 376ms :: artifacts dl 0ms
---------------------------------------------------------------------
| | modules ||
artifacts |
| conf | number| search|dwnlded|evicted||
number|dwnlded|
---------------------------------------------------------------------
| classpath | 0 | 0 | 0 | 0 || 0 |
0 |
---------------------------------------------------------------------
Evaluating project :groovy1.5 using empty build file.
Build failed with an exception.
Run with -s or -d option to get more details. Run with -f option to get
the full (very verbose) stacktrace.
Empty build file
A problem occurred evaluating project ':groovy1.5'.
Cause: java.lang.NullPointerException (no error message)
BUILD FAILED
Total time: 8.164 secs
I don't think that "Empty build file" is your error here.
I think the NPE is caused by something else.
Try running it with -s, -d, or -f to get the full stack trace so we can see
where the problem is.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
