On Tue, Nov 16, 2010 at 2:08 PM, Stefan Seelmann <firstname.lastname@example.org>
I'm trying to get Studio's UI tests working again. I updated ApacheDS
and Shared dependencies to current trunk. I had problems when using
the FrameworkRunner (which starts an embedded ApacheDS). The schema
extractor uses the java.class.path to scan the JARs for schema LDIF
files. However in the Eclipse RCP (OSGi) environment the
java.class.path only contains the bootstrap JAR. Similar issues were
already reported in  and .
Owen Jacobson proposed in  to use an index file that lists all
schema LDIF files. I think that's a great idea. I tested the solution
in a branch  and it works fine for the UI tests. I think it should
also work for other cases. Unfortunately I can't run the full ApacheDS
test suite atm.
I created the index file with
find src/main/resources/schema -name "*.ldif" | sed
and added it to SVN
(src/main/resources/META-INF/apacheds-schema.index). A better solution
would be to generate the index file during the build, and to avoid its
addition to version control. One way would be to execute that (or a
similar) command using the exec-maven-plugin, but it only works on
Unix. A better way would be to create a new Maven plugin (I searched
but didn't find an existsing Maven plugin that scan the file system
and creates a file list).
This schema file will need to be updated I guess when users create a new schema in ApacheDS correct?
So I guess there would be more we would need to do with this. Also this reminds me sort of by the index file we used to have in the past for partition index files for the schema partition. I remember running into several build problems when we were using it. But this does not mean we will have the same problem here.
You volunteered to create a Maven Plugin :-) Do you still want to give
it a try and contribute it to the Directory project?