should repository-client-impl depend on repository-spi? (was Re: [daisy] Daisy Detachment - dependencies)

[Marc Portier]

Andreas Deininger wrote:
> 2006/7/4, tim_cranfield at goldenboat.net <tim_cranfield at goldenboat.net>:
>>
>> Another NoClassDefFoundError comes for ExtensionRegistrar.
>> Where can this be found?
> 
> In: daisy-repository-spi-1.x.jar
> 

hm, but that looks like a jar this detachment-client shouldn't be
dependent on, no?

I'm seeing the same error, and the stacktrace points me here:

> [java]      at org.outerj.daisy.detachment.DetachmentRepositoryTalker.<init>(DetachmentRepositoryTalker.java:24)

At the mentioned line there is:

> 
> 24	RepositoryManager repositoryManager = 
> 25		new RemoteRepositoryManager(connection.getUrl(), connection.getCredentials());


Digging into this
org.outerj.daisy.repository.clientimpl.RemoteRepositoryManager I noticed
it implements org.outerj.daisy.repository.ExtensionRegistrar which in
fact sits in the repository-spi.

Also the project.xml of repository-client-impl clearly states the
dependency on repository-spi.

Is that what we really want?
Should these extension-interfaces maybe move up to repository-api
(looking at their package names?)


-marc=
-- 
Marc Portier                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at                http://blogs.cocoondev.org/mpo/
mpo at outerthought.org                              mpo at apache.org