Which branch/tag are you building it from?
Eh? I'm not building it.
I'm looking the downloaded EAP6.0.1 repo and that from 6.1.0 beta (https://www.jboss.org/download-manager/content/origin/files/sha256/0a/0a75b4e1028a48c45b2181a4bdee874ac3c854b166b3e719a40b8aeec32a264a/jboss-eap-6.1.0.Beta-maven-repository.zip).
Both only have guave in com/google/.
Well, what I meant was, who (or which branch) requires that com.google.code.cookcc#cookcc;0.3.3-redhat-1? In other words, how did you run into some error related to that artifact?
Ah, my bad. I don't know the proper Maven lingo, it seems
I was pulling org.jboss.as#jboss-as-controller-client;7.1.3.Final-redhat-4 out into a Ivy repository (using Ivy's install task).
The dependency is in org.jboss#jboss-dmr;1.1.1.Final-redhat-2, which is referenced by org.jboss.as#jboss-as-controller-client;7.1.3.Final-redhat-4.
jboss-as-controller-client is the one I was trying to import.
According to http://ant.apache.org/ivy/history/latest-milestone/use/install.html it appears that I'm using the 'default branch'.
I try to import transitive dependencies, and that may be the cause of the problem.
The problem is, however, if I don't import transitive dependencies, IVY will complain about referenced but not existing dependencies later on. *sigh*
The solution was to upgrade to Ivy 2.3.0 which allows the configuration to be specified.
Then I could specify 'default' instead of the default '*' which fixes the problem.