On Thu, Apr 10, 2008 at 3:59 PM, Brown, Carlton <
> I'd like to bump this topic one more time. After more testing using
> static revision numbers, I am still not able to use Ivy namespaces to
> map revision numbers between repositories. There's no problem with
> organisations or modules.
> This time I used static revision numbers instead of expressions, in
> order to guarantee an 1:1 relationship. For example, trying to map
> rev=126.96.36.199 to rev=1.0.0-final. It kept failing with an error similar
> to below, "inconsistent module descriptor". It claims it "found" a
> revision of 1.0.0-final inside ivy-1.0.01.xml (which is NOT contained in
> the file), although it expected a revision of 188.8.131.52 (which truly IS in
> the ivy-184.108.40.206.xml file).
> So does namespace mapping actually work for revisions? Is there a test
> case for this?
I doubt we have a test case for this, and I've never heard people using
namespaces for this, so I wouldn't be surprised if it's buggy. Just to be
sure, in your last test (with static revision) did you provide the
conversion rules in both ways (from and to system). Because I haven't
checked the code, but I think currently Ivy relies on both rules to handle
> > -----Original Message-----
> > From: Brown, Carlton [mailto:Carlton.Brown@compucredit.com]
> > Sent: Friday, April 04, 2008 1:52 PM
> > To: email@example.com
> > Subject: Namespace problems
> > I'm getting errors I don't understand while using install
> > with namespace
> > and I'd appreciate any insight.
> > Briefly, my intention is to copy foo-module-220.127.116.11 from an
> > RC repository into a final repository with the version
> > changed to 1.0.0 (truncating the final number).
> > My rename rule looks like this:
> > ==================================================== > > This message contains PRIVILEGED and CONFIDENTIAL information > > that is intended only for use by the named recipient. If you > > are not the named recipient, any disclosure, dissemination, > > or action based on the contents of this message is > > prohibited. In such case please notify us and destroy and > > delete all copies of this transmission. Thank you. > > ==================================================== > >> > > > ----------------------------------------- > ==================================================== > This message contains PRIVILEGED and CONFIDENTIAL > information that is intended only for use by the > named recipient. If you are not the named recipient, > any disclosure, dissemination, or action based on > the contents of this message is prohibited. In such > case please notify us and destroy and delete all > copies of this transmission. Thank you. > ==================================================== > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/