• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • Integration Modules
  • hhuynh
  • Reporter: hhuynh
  • January 15, 2008
  • 0
  • Watchers: 0
  • January 30, 2008
  • January 28, 2008

Description

Follow the instruction from this page http://forge.terracotta.org/projects/tim-archetype/docs/quickstart.html and create the “baztim” module. Upon running the “sample” in that project, you’ll get a bunch of warnings like below:

tc-config.xml

<modules>
  <repository>file://%(user.home)/.m2/repository</repository>
  <module name="baztim" version="1.0.0" group-id="org.foo.bar"/>
</modules>

Error:

[INFO] [node0] 2008-01-15 16:45:41,875 WARN - Unable to resolve repository location, verify that it exists and that it is a valid repository: ‘d:\Users\hhuynh.m2\repository\org\terracotta\modules’ [INFO] [node1] 2008-01-15 16:45:41,925 WARN - Unable to resolve repository location, verify that it exists and that it is a valid repository: ‘d:\work\forge\baztim\target\org\terracotta\modules’

Comments

Alex Miller 2008-01-15

A windows file path like this is not a valid url - it may be that this is only a problem on Windows. Due to the jira (DEV-1176) which I just worked on in 2.5.1, you will likely get a different error message that is a bit more precise.

Hung Huynh 2008-01-15

It has something to do with the module resolver assuming/scanning /org/terracotta/modules.

I tried this in linux:

<modules>
  <!-- <repository>file://%(user.home)/.m2/repository</repository> -->
  <repository>file:///export1/cruise/forge/baztim/target</repository>                                                                  
  <module name="baztim" version="1.0.0" group-id="org.foo.bar"/>                                                                       
</modules>  

and got this error:

[INFO] [node0] 2008-01-15 18:41:00,808 WARN - Unable to resolve repository location, verify that it exists and that it is a valid repository: ‘/export1/cruise/forge/baztim/target/org/terracotta/modules’

and I have the TIM jar in “target”

[[email protected]: target]$ pwd /export1/cruise/forge/baztim/target [[email protected]: target]$ ls total 8 -rw-r–r– 1 cruise cruise 497 Jan 15 18:35 MANIFEST.MF -rw-r–r– 1 cruise cruise 2720 Jan 15 18:35 baztim-1.0.0.jar drwxr-xr-x 2 cruise cruise 80 Jan 15 18:35 classes

Juris Galang 2008-01-28

This is just a warning. We should just log this and not print it out.

When a module is not found, the modules loader will complain and print out a list of repository locations where it attempted to find the offending module.

Juris Galang 2008-01-28

This was misfiled under FORGE; the fix is on the main product line. Fixed in rev 6846 (2.5 branch), merged in trunk (rev 6847)