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


Reply via email to