Hi, On 29.07.2010 16:45, Carsten Ziegeler wrote: > Justin Edelson wrote >> On 7/29/10 8:02 AM, Carsten Ziegeler wrote: >>> Ian Boston wrote >>>> Hi, >>>> >>>> I am seeing failures with things that implement the Resource api from the >>>> 2.0.8 bundle that are used by ResourceUtil.getName(resource) in the >>>> 2.0.9-SNAPSHOT bundle. >>>> >>>> IIUC the Resource API from 2.0.9-SNAPSHOT has getName(). >>>> ResourceUtil.getName() in 2.0.9-SNAPSHOT calls resource.getName() which >>>> doesnt exist in 2.0.8 and earlier. AbstractMethodException follows. >>>> >>>> I think one solution would be a try catch in the deprecated methods to >>>> work with pre 2.0.8 implementations of Resource >>>> WDYT? >>>> >>> I think this is a temporary problem - the new API will export version >>> 2.1, therefore old implementations are not expected to work anymore. >>> This is the version contract we have - compatibility for clients, but >>> not necessary for implementations when the minor version changes. >>> >>> Regards >>> Carsten >> Then we should change the imports on the resource implementation bundles >> so that they're now [2.1,2.2) ? >> > Yes, I think so.
I will care for this. Myabe we should just keep the old ResourceUtil implementations so as to not trigger such exceptions. I just adapted the actual maven dependencies. Thanks for noting. Regards Felix > > Carsten
