On 10 Sep 2014, Ryan Baxter wrote: > Martin are you having issues building shindig because the dependency > cannot be found?
We had issues after an upgrade of our local repository manager (nexus 1.x to 2.9) which I solved by deploying a relocation POM for caja in our local repository manager. So no, I do not (no longer) have any problems building shindig or our project that uses shinding. Still, shinding depends on an artifact that (according to POM coordinates) does not exist, which feels just broken. > I just built shindig and maven was able to download > the dependency into my local repo and build. Background information: when building WITHOUT our local repository manager everthing worked and works fine. But when I use our local repository-manager maven said it cannot find the artifact caja: [...] [ERROR] Failed to execute goal on project emcs-shindig-integration: Could not resolve dependencies for project at.co.xss.myProject:jar:5.1-SNAPSHOT: The following artifacts could not be resolved: caja:caja:jar:r5054: Could not find artifact caja:caja:jar:r5054 in nexus-repo The thing is, the artifact caja:caja:jar:r5054 really does NOT exist! So the error message is correct. As I wrote earlier, according to caja's POM, it has a groupId of com.google.caja. However, in the repository http://google-caja.googlecode.com/svn/maven/ it's in the directory caja/caja which should correspond to the groupId (but does not). So the actual problem seems to be, that caja's maven repo is kind of broken. I already fixed the problem with a relocation POM for caja in our local repository manager. So there is no problem for me building our project. But I still think shinding's dependency to caja is incorrect. IMHO the whole thing only works because caja's repository serves an artifact that actually is not available according to POM coordinates. Did I make myself clear? hth, - martin
signature.asc
Description: PGP signature
