• Bug
  • Status: Closed
  • 2 Major
  • Resolution: As Designed
  • drb
  • Reporter: tgautier
  • August 26, 2008
  • 0
  • Watchers: 0
  • July 27, 2012
  • August 26, 2008


  • tgautier (1.00 k) application/xml pom.xml


I should be able to specify commons collections as a dependency and our repo and it should download, but I am getting an error:

[INFO] Preparing tc:manifest [WARNING] Removing: manifest from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping Downloading: http://snapshots.repository.codehaus.org/org/terracotta/modules/tim-collections/2.2.2/tim-collections-2.2.2.jar Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/terracotta/modules/tim-collections/2.2.2/tim-collections-2.2.2.jar Downloading: http://www.terracotta.org/download/reflector/maven2/org/terracotta/modules/tim-collections/2.2.2/tim-collections-2.2.2.jar Downloading: http://repo1.maven.org/maven2/org/terracotta/modules/tim-collections/2.2.2/tim-collections-2.2.2.jar [INFO] ———————————————————————— [ERROR] BUILD ERROR [INFO] ———————————————————————— [INFO] Failed to resolve artifact.

Attached is my pom.xml


Tim Eck 2008-08-26

I might not know how things are supposed to work, but I’m confused by two things. First I don’t think is a TIM called tim-collections. There is container type project called tim-collections that has bunch of TIMs within it (tim-hashtable, tim-sycnrhonizedset, etc). The other thing that is confusing is that I wasn’t under the impression that tim-collections has any thing to do with apache commons collections. There is a clustered-commons-collections TIM that comes with the core kit (although it very incomplete)

Alex Miller 2008-08-26

Tim, you are 100% correct. At the moment, clustered-commons-collections is still in the kit, not on the forge.