You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Bhoomin Pandya <bh...@gmail.com> on 2014/07/23 10:50:49 UTC
Stanbol Build with Java 8
Hi Stanbol Team,
Recently I got an update for Java 8.
i.e.
c:\.....\stanbol> java -version
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
The Maven was built with Java 7
Maven home: C:\apache-maven-3.2.1
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_25\jre
Default locale: en_IN, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
I could build Stanbol a couple of times after java update to 1.8.0_05
but now build fails with Mojo..exception error and
"-XX:MaxPermSize=256M" support removed in java version "1.8.0_05".
Is Java version the cause of Build Failure ? or its the recent changes
made to Stanbol Repository at your end?
Kindly, advise.
Best Regards,
Bhoomin Pandya
Re: Stanbol Build with Java 8
Posted by Bhoomin Pandya <bh...@gmail.com>.
Thanks Alessandro,
I shall try to build without tha "-XX:MaxPermSize" and let you know.
Best Regards,
Bhoomin
On Wed, Jul 23, 2014 at 2:30 PM, Alessandro Adamou
<al...@studio.unibo.it> wrote:
> Hi,
>
> It appears since Java 8, the Permanent Generation memory space is gone in Hotspot.
>
> I'm curious to try the build without setting "-XX:MaxPermSize" at all. If an OutOfMemoryError still occurs, we should suggest a value for the new "-XX:MaxMetaspaceSize"
>
> best
>
> Alessandro
>
> ________________________________________
> Da: Bhoomin Pandya <bh...@gmail.com>
> Inviato: mercoledì 23 luglio 2014 09:50
> A: dev@stanbol.apache.org
> Oggetto: Stanbol Build with Java 8
>
> Hi Stanbol Team,
>
> Recently I got an update for Java 8.
> i.e.
> c:\.....\stanbol> java -version
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
>
> The Maven was built with Java 7
> Maven home: C:\apache-maven-3.2.1
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_25\jre
> Default locale: en_IN, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>
> I could build Stanbol a couple of times after java update to 1.8.0_05
> but now build fails with Mojo..exception error and
> "-XX:MaxPermSize=256M" support removed in java version "1.8.0_05".
>
> Is Java version the cause of Build Failure ? or its the recent changes
> made to Stanbol Repository at your end?
>
> Kindly, advise.
>
> Best Regards,
>
> Bhoomin Pandya
RE: Stanbol Build with Java 8
Posted by Alessandro Adamou <al...@studio.unibo.it>.
Hi,
It appears since Java 8, the Permanent Generation memory space is gone in Hotspot.
I'm curious to try the build without setting "-XX:MaxPermSize" at all. If an OutOfMemoryError still occurs, we should suggest a value for the new "-XX:MaxMetaspaceSize"
best
Alessandro
________________________________________
Da: Bhoomin Pandya <bh...@gmail.com>
Inviato: mercoledì 23 luglio 2014 09:50
A: dev@stanbol.apache.org
Oggetto: Stanbol Build with Java 8
Hi Stanbol Team,
Recently I got an update for Java 8.
i.e.
c:\.....\stanbol> java -version
java version "1.8.0_05"
Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
The Maven was built with Java 7
Maven home: C:\apache-maven-3.2.1
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_25\jre
Default locale: en_IN, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
I could build Stanbol a couple of times after java update to 1.8.0_05
but now build fails with Mojo..exception error and
"-XX:MaxPermSize=256M" support removed in java version "1.8.0_05".
Is Java version the cause of Build Failure ? or its the recent changes
made to Stanbol Repository at your end?
Kindly, advise.
Best Regards,
Bhoomin Pandya