Thanks for your suggestion Luciano. I have fixed this issue by modifying the deployer to add dependencies based on the namespace location attribute.
Committed at revision 834397. On Mon, Nov 9, 2009 at 9:51 PM, Luciano Resende <[email protected]>wrote: > On Mon, Nov 9, 2009 at 3:01 AM, Simon Laws <[email protected]> > wrote: > > Hi Ram > > > > I thought the location specific to the import processing. Why would we > > want it on the resolveModel interface generally? > > > > Regards > > > > Yes, I think the idea is, if you find a specific contribution URI on > the import, then you delegate to the resolver of the specific > contribution, otherwise, you delegate to the special resolver that > goes over a broad set of contributions. This filter could probably be > done either with the "match" algorithm available in the import/export > models or when the Deployer process the dependencies (see > DeployerImpl.addContributionDependencies) > > -- > Luciano Resende > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ > -- Thanks & Regards, Ramkumar Ramalingam
