You will have to excuse my java ignorance. I only make forays into Java land when I really have to, so my knowledge of build tools and dependency management is trivial.
I am beginning to see where I am going wrong. I pulled down the sdb source distribution and fuseki binary distribution. I am doing "mvn clean install" in the jena-sdb-1.3.5 for example, and it does create jars in target, but there is no lib dir etc. So in my setup, there are no distinct jars for arq, core, etc. Pulling down the jena-2.10.0 source distro, I see jena-sdb under it, but it is commented out in the pom. Uncommenting it and building throws an immediate error: [ERROR] The project org.apache.jena:jena-sdb:1.3.6-SNAPSHOT (/Users/***/Source/GraphIDS/jena-2.10.0/jena-sdb/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not find artifact org.apache.jena:jena-parent:pom:5-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 29, column 11 -> [Help 2] Before I go trying to fix things that aren't broken, let me tell you what I want to do. Working is a rather backwards manner, I jumped into the code and created a patch to support a new database type, Redshift. It is modeled off the postgresql stuff, but with the necessary changes to work on Redshift. I can apply the patch cleanly to jena-sdb-1.3.5 and 1.3.6. I built 1.3.6-SNAPSHOT to generate a jar, and I was able to load it up with Fuseki and connect to my Redshift instance. However, I need to have the SDB command line tools working as well, so I can create the schema etc. What approach should I be taking to achieve my goal. I appreciate the support, and hopefully I will have Redshift support to contribute back as a result. Dom On Mon, Feb 25, 2013 at 1:55 PM, Andy Seaborne <[email protected]> wrote: > On 25/02/13 21:39, Dominique Brezinski wrote: > >> Hello all. I started working with SDB in order to add support for AWS >> Redshift. However, I am running into a problem that implies I missing >> something basic. >> >> I followed the instructions to setup the command line tools, but they bomb >> on an unmet dependency: arq.cmdline.CmdMain. >> >> bin/sdbconfig --sdb=sdb-redshift.ttl --create >> Exception in thread "main" java.lang.**NoClassDefFoundError: >> arq/cmdline/CmdGeneral >> at java.lang.ClassLoader.**defineClass1(Native Method) >> at java.lang.ClassLoader.**defineClassCond(ClassLoader.**java:631) >> at java.lang.ClassLoader.**defineClass(ClassLoader.java:**615) >> at java.security.**SecureClassLoader.defineClass(** >> SecureClassLoader.java:141) >> at java.net.URLClassLoader.**defineClass(URLClassLoader.**java:283) >> blah blah ;) >> >> I have been working with jena-sdb-1.3.5 and the SVN head of 1.3.6. Now >> looking in the source tree, I don't see the arq namespace. >> > > "arq.*" are the command line bits and pieces that come with ARQ jena-arq. > It looks like your runtime classpath is incomplete. > > The maven artifact will pull in all the dependencies. They are all > includes in the distribution zip file as well in lib/ (it's a mystery to be > why sometimes the jar has SNAPSHOT and sometimes the snapshot timestamp). > > alternatively run with > > java -cp 'lib/*' sdb.sdbconfig .... > > Andy > > > >> What the am missing? >> >> Thanks, >> Dom >> >> >
