Hi,
On 01/03/2013 07:51 AM, Fabian Christ wrote:
btw it's eating a lot more than before: 1.5g heap and 256m permgen was no
longer enough when I tried it on a virtualised Linux.
Yes, it is because of the new security components introduced by Reto. They
are activated in the full launcher by default. Maybe you need your own
launcher configuration if you do not want this.
Actually it is the _build_ that's eating that much, goes out of memory
long before reaching the launchers. I needed at least -Xmx2g and
-XX:MaxPermSize=384m to get it to compile.
At any rate, I've tried the OWL API 3.3 dependencies instead of 3.4.2,
like this:
<dependency>
<groupId>net.sourceforge.owlapi</groupId>
<artifactId>owlapi-api</artifactId>
<version>3.3</version>
</dependency>
<dependency>
<groupId>net.sourceforge.owlapi</groupId>
<artifactId>owlapi-apibinding</artifactId>
<version>3.3</version>
</dependency>
It managed to build and test fine on me under this environment:
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-i386/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-35-generic", arch: "i386", family: "unix"
BUT so far I've only tried commons.owl and the ontologymanager reactor.
Now I'm rebuilding the whole Stanbol. I'll keep you updated.
I expect some integration tests to fail, because we'll need to embed
many additional OWL API packages: those two artifacts are enough for
compiling, but I'm afraid we're going to need a lot more for the
ontologymanager to work in the launcher, unless there is some readily
available OSGi bundle for the OWL API and its bindings. If not, is it OK
if I use the commons.owl bundle for embedding them?
Best,
Alessandro
