On 6/02/10 6:00 AM, barrymac wrote:
No worries, I'm afraid I can't remember exactly but it was something to do
with ant-1.6 being on the classpath. I didn't always get a stack trace
though. Sometimes it only said it couldn't resolve all dependencies. even
though they were available in artifactory.
I added the dependency in the normal way.
As in, you did something like:
dependencies {
compile 'esapi:esapi:1.4.4'
}
I had uploaded all the jars into
our maven repo from the esapi distribution which included poms for them all.
So the esapi pom had a long list of dependencies which caused a clash with
gradle.
Adam Murdoch-2 wrote:
Hi,
I completely missed your original post. Sorry about that.
Regarding the original problem, how were you adding the dependency on
esapi? And what was the stack trace that was being reported?
On 28/01/10 10:05 PM, barrymac wrote:
I fixed this by simply reducing the pom for esapi that is stored in
artifactory down to a minimal set of jars. The transient flag on the
dependencies in gradle did not seem to effect anything, but removing them
from the pom did!
I should add that when I add the correct dependency for xml-apis as
gradle
suggests then it makes no difference to the behaviour at all.
Hi folks,
My problem does not appear with version 0.8. I've been having this
trouble
for a while with version 0.9.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
