On 09/09/16 11:16, otheus uibk wrote:
Thanks Andy,
An RPM for Fuseki is the goal.
If Fuseki, consider using one of the docker containers.
I hoped you were joking with this. I had given it some thought, and for our
immediate purposes, this would suffice. Then again, so would a jar file run
out of a personal directory. For enterprise deployment in a productive
environment, this isn't helpful.
The container people would beg to differ!
For Fuseki/RPM, what you are trying to install is a directory hierarchy +
maybe some setting in other files. So don't treat as a Java thing but pull
the prebuilt zip and work with files from there.
Yeah, it's the "setting in other files" bit which is pretty critical. The
main thing is a set of service startup/stop scripts (or service files, if
systemd), and identifying package dependencies (java 1.7 OK? java 1.8 OK?).
Fuseki - and the rest of jena - is Java8.
There's a maven plugin at http://www.mojohaus.org/rpm-maven-plugin/ but I
don't really understand how to use it.
I don't think you need to use maven. Start with the prebuilt distribution.
Fuseki self-initializes - if you run it in a directory (and that can be
moved away from where the jar is with environment variables - e.g.
/etc/default/fuseki), it creates it's own run area. c.f. CATALINA_HOME
and CATALINA_BASE. Try it and see.
Andy
