Andy Seaborne wrote: > It does not disturb anything else (does it?) and makes it more > accessible to users to try out.
tdbloader3 is using Hex from commons-codec which is a dependency in ARQ. This is not in the TDB's .classpath (which is edited manually). So, I added (manually, :-() these: + <classpathentry excluding="**/*.java|**/.svn/" kind="src" + <classpathentry kind="var" path="M2_REPO/commons-codec/commons-codec/1.4/commons-codec-1.4.jar" sourcepath="M2_REPO/commons-codec/commons-codec/1.4/commons-codec-1.4-sources.jar"/> mvn eclispe:eclipse for TDB does not work: [INFO] Resource directory's path matches an existing source directory. Resources will be merged with the source directory src/main/resources [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ I usually go with mvn eclipse:eclipse and my advice would be to do that not to lose the big advantage of managing direct and transitive dependencies with a dependency engine (in this case Maven). Manually editing the .classpath file is bound to human mistakes, for example, in this case TDB's .classpath is missing transitive dependencies coming from ARQ. However, I am going on and edit the .classpath manually as shown above and forget mvn eclipse:eclipse for TDB. Paolo
