Re: apache-jena not building properly and possibly bad paths

[Sarven Capadisli]

On 02/04/2013 09:34 PM, Andy Seaborne wrote:

On 04/02/13 18:13, Sarven Capadisli wrote:

Hello!

I have svn co https://svn.apache.org/repos/asf/jena/trunk

JENA_HOME="/usr/lib/jena/trunk/apache-jena"

and I'm trying to build apache-jena from

/usr/lib/jena/trunk/apache-jena$

I do:

mvn install

I get the following:

[INFO] Reading assembly descriptor: assembly-jena-zip.xml
[WARNING] Cannot include project artifact:
org.apache.jena:apache-jena:pom:2.10.0-SNAPSHOT; it doesn't have an
associated file or directory.

I suspect you have not the snapshot repo setup:

In your Maven settings.xml ==>

         <repository>
           <id>apache.snapshots</id>
           <name>Apache Snapshot Repository</name>
           <url>https://repository.apache.org/snapshots</url>
           <releases>
             <enabled>false</enabled>
           </releases>
           <snapshots>
             <enabled>true</enabled>
           </snapshots>
         </repository>

Do I have to setup a <profile> for this? I've tried just placing that within <settings>, from a copy that I grabbed under /etc/maven/settings.xml (in Ubuntu) to ~/.m2/settings.xml. Didn't work out.

Even though build is successful. Full output at [1].

When I run:

/usr/lib/jena/trunk/apache-jena/bin/tdbloader

I get:

Error: Could not find or load main class tdb.tdbloader

apache-jena creates the zip file for the download.  It does not create
the lib/ locally.

Adding the ASF snapshot repo and "mvn clean package" should be enough,
then unpack the zip.

Or use an overnight build: the build runs every day.

https://repository.apache.org/content/repositories/snapshots/org/apache/jena/apache-jena/


You probably want the latter unless you want to edit the code or pick up
a fix that is only a few hours done.

So, when I look at /usr/lib/jena/trunk/apache-jena, I noticed that the
lib directory is not created and missing the jars.

What did I miss? I have apache-jena on my local machine and I suppose it
created the libs at some point in the past. I can't remember if I did
this differently.


And.. so I tried the old fashion way with jena-tdb where TDBROOT is
set to:

/usr/lib/jena/trunk/jena-tdb

Then I ran

$ bin/tdbloader
Can't open /usr/lib/jena/trunk/jena-tdb/.classpath: No such file or
directory.
Exception in thread "main" java.lang.NoClassDefFoundError:
arq/cmdline/CmdARQ

Here, you are running the script that is used developing TDB.  It's
looking for the dependencies and assumes an Eclipse setup.  You need to
have all of Jena/trunk setup for Eclipse and compiled.

Woah, okay, I guess I was completely off mark there. Thanks.

...

That'd be my preferred way (as opposed to apache-jena), however:

It appears to be that I always run into path issues when I upgrade stuff.

I still find the most reliable way to set up TDB/Fuseki is co
jena-fuseki. However, I'd like to move away from that in order to give
more memory to TDB and just use it for Fuseki.

You can run TDB commands using the Fuseki jar (!!!)

java -cp DIR/fuseki-server.jar tdb/tdbloader ....

I missed this too. I was using java tdb.tdbloader in the past where my Fuseki target/ is in $CLASSPATH but never was able to change the memory availability. This is very handy and I think I'll just resort to this option as it pretty much gives me all I needed i.e., ability to change the memory for TDB loading as well as Fuseki. Seems obvious but I've overlooked :)

As always, any direction is much appreciated

[1] https://gist.github.com/4708357

-Sarven
http://csarven.ca/#i

     Andy

Andy for Prime Minister!

-Sarven

smime.p7s
Description: S/MIME Cryptographic Signature