Hi all,
I have a plugin I have been using for some time for docbook processing.
In the past I've just built it using Intellij and dropped the jars and
dependencies into the gradle lib directory and added the class to the
plugin.properties file. This was working find with the current 0.8 distro.
I decided (using the latest codebase) to try actually using gradle to
build it and install it in my local repository (~/.m2/repository). That
works OK, but when I try and add it as a dependency to the build script
I want to use it from, things go awry:
buildscript {
repositories {
mavenRepo urls: 'file:///Users/luke/.m2/repository'
mavenCentral();
}
dependencies {
classpath 'monkeymachine.gradle:gradle-docbook:0.1-SNAPSHOT'
}
}
usePlugin monkeymachine.gradle.DocbookPlugin
There seems to be a problem with resolving one the transient
dependencies of 'org.apache.xmlgraphics:fop:0...@jar' and gradle ends up
in a recursive call to
DefaultIvyReportConverter.getResolvedDependenciesForNode:
java.lang.StackOverflowError: null
at
org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor.getConfiguration(DefaultModuleDescriptor.java:404)
[ivy-2.1.0-rc2.jar:2.1.0-rc2]
at
org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor.getArtifacts(DefaultModuleDescriptor.java:442)
[ivy-2.1.0-rc2.jar:2.1.0-rc2]
at org.apache.ivy.core.resolve.IvyNode.getArtifacts(IvyNode.java:789)
[ivy-2.1.0-rc2.jar:2.1.0-rc2]
at
org.apache.ivy.core.resolve.IvyNode.getSelectedArtifacts(IvyNode.java:740)
[ivy-2.1.0-rc2.jar:2.1.0-rc2]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.getArtifacts(DefaultIvyReportConverter.java:279)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.createResolvedDependency(DefaultIvyReportConverter.java:265)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.getResolvedDependenciesForNode(DefaultIvyReportConverter.java:120)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.getResolvedDependenciesForNode(DefaultIvyReportConverter.java:135)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.getResolvedDependenciesForNode(DefaultIvyReportConverter.java:135)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
at
org.gradle.api.internal.artifacts.ivyservice.DefaultIvyReportConverter.getResolvedDependenciesForNode(DefaultIvyReportConverter.java:135)
[gradle-core-0.9-20091203145759+0000.jar:0.9-20091203145759+0000]
Leaving aside this issue (which I haven't had time to track down the
cause of), I was wondering if there is an alternative recommended
approach for configuring plugins.
I noticed that the concept of "init scripts" has been introduced. Is it
possible to use one of these to setup a plugin and add its dependency
jars without having to tinker with the gradle distro if I rebuild it or
switch to another version?
Cheers,
Luke.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
