Hi Martin, Did you have a look in Archiva around RedbackRuntimeConfigurationAdmin (how to define which redback impl is used). Spring configuration files are loaded META-INF/spring-context.xml
Note the idea is to get rid of all jdo implementations. HTH On 3 October 2016 at 05:13, Martin <[email protected]> wrote: > Oh, wrong, I put the jpa module dependencies into > redback-common-integrations/pom.xml > But the questions remain the same ;-) > > > Am Sonntag, 2. Oktober 2016, 19:57:26 CEST schrieb Martin Stockhammer: > > Ok, I got it. It was hidden in pom dependencies. > > The dependencies for the redback-users provider implementations are > hidden > > deeper in the dependency tree (e.g. redback-users-jdo is a dependency in > > redback-rbac-cached). > > > > I put the jpa modules into the redback-core pom as dependency, but not > sure > > if this is the right place. > > > > So two questions: > > - I think the dependency of redback-users-jdo in the pom of redback-rbac- > > cached is wrong and should be moved into the test scope. Am I right? > > - Wouldn't it make sense to set the users and rbac provider > implementations > > that archiva uses/knows explicitly as maven dependency in the web > > application pom? > > > > > > Martin > > > > Am Sonntag, 2. Oktober 2016, 12:56:50 CEST schrieb Martin: > > > So, as I can see it seems to be more a packaging / dependency problem. > > > The new modules are not copied to WEB-INF/lib of the created > application. > > > > > > So I think I have to mention the modules somewhere in the pom.xml as > > > dependency. But currently I do not know where. They are added as > modules > > > to > > > the parent module (e.g. redback-users-provider), but I think they must > be > > > added somewhere else. redback-users-ldap and redback-users-jdo seems > to be > > > loaded by some magic, or deeper dependencies that I currently do not > see. > > > > > > Greetings > > > > > > Martin > > > > > > Am Samstag, 1. Oktober 2016, 22:27:18 CEST schrieb Martin: > > > > Hi, > > > > > > > > I currently try to load the new redback jpa modules into the archiva > > > > application. But I'm a bit lost. The spring-context.xml seems not to > be > > > > loaded from these files. So how does the spring starter know which > > > > context > > > > files to load? Is there anywhere a master file or something, or does > it > > > > only work by classpath scanning? If so, do I have to add additionally > > > > somewhere the dependencies to these modules? > > > > > > > > Greetings > > > > > > > > Martin > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
