Hi Rupert,

The Build Resulted in Failure again with increased memory, I am not sure
but I had read somewhere that Windows can use only max of 1.4 GB RAM.

I believe its my system probably. I will reduce the load on the desktop and
run it again.

Many Thanks,

Bhoomin




On Tue, Apr 8, 2014 at 6:17 PM, Bhoomin Pandya <bhoominpan...@gmail.com>wrote:

> Hi Rupert,
>
> Many Thanks I will run it with increased memory.
>
>
> I just tried to reach you. I wish to be more involved with the Stanbol
> once it is up running.
>
> Best Regards
> Bhoomin
>
>
>
> On Tue, Apr 8, 2014 at 5:06 PM, Rupert Westenthaler <
> rupert.westentha...@gmail.com> wrote:
>
>> Hi Bhoomin,
>>
>>
>> > java.lang.OutOfMemoryError: PermGen space
>>
>> this indicates that you do not have enough PermGen memory available
>> during the build.
>>
>> Please try to increase the memory settings in your MAVEN_OPTS
>>
>>     MAVEN_OPTS=-Xmx2g -XX:MaxPermSize=512M
>>
>> For windows user: There are some known issues when compiling/running
>> Stanbol on windows. [1] provides a good overview about such issues
>>
>> best
>> Rupert
>>
>> [1] http://markmail.org/message/fnm6xhasrw5zq6r7
>>
>> On Tue, Apr 8, 2014 at 1:29 PM, Bhoomin Pandya <bhoominpan...@gmail.com>
>> wrote:
>> > Hi Furkan:
>> >
>> > I would like to correct my earlier email - Rupert did not suggest SVN -
>> but
>> > I believe that is the only way to go about. I have Tortoise SVN.
>> >
>> > I have already set enviroment variable
>> >
>> > MAVEN_OPTS=-Xmx1024M -XX:MaxPermSize=256M
>> >
>> >
>> > Thanks for your help
>> > Best Regards
>> >
>> > Bhoomin
>> >
>> > On Tue, Apr 8, 2014 at 4:48 PM, Bhoomin Pandya <bhoominpan...@gmail.com
>> >wrote:
>> >
>> >> Hi Furkan:
>> >>
>> >> In the beginning of the installation I am getting some error message
>> about
>> >> No Source to Compile
>> >> Then almost all SNAPSHOTs get downloaded
>> >> Test Show no Failures
>> >> But Afterwards
>> >>
>> >> following Failure Message Appear
>> >>
>> >>  BUILD FAILURE
>> >>
>>  ------------------------------------------------------------------------
>> >>  Total time: 09:14 min
>> >>  Finished at: 2014-04-08T16:44:47+05:30
>> >>  Final Memory: 119M/949M
>> >>
>>  ------------------------------------------------------------------------
>> >> ] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.
>> >> mpile (default-compile) on project
>> org.apache.stanbol.commons.web.resource
>> >> pilation failure
>> >> ] Failure executing javac, but could not parse the error:
>> >> ]
>> >> ]
>> >> ] The system is out of resources.
>> >> ] Consult the following stack trace for details.
>> >> ] java.lang.OutOfMemoryError: PermGen space
>> >> ] at java.lang.ClassLoader.defineClass1(Native Method)
>> >> ] at java.lang.ClassLoader.defineClass(ClassLoader.java:792)
>> >> ] at
>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14
>> >>
>> >> ] at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
>> >> ] at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
>> >> ] at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
>> >> ] at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
>> >> ] at java.security.AccessController.doPrivileged(Native Method)
>> >> ] at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
>> >> ] at
>> org.codehaus.plexus.compiler.javac.IsolatedClassLoader.loadClass(Isol
>> >> assLoader.java:56)
>> >> ] at
>> com.sun.tools.javac.file.JavacFileManager.setContext(JavacFileManager
>> >> 158)
>> >> ] at
>> com.sun.tools.javac.file.JavacFileManager.<init>(JavacFileManager.jav
>> >>
>> >> ] at
>> com.sun.tools.javac.file.JavacFileManager$1.make(JavacFileManager.jav
>> >>
>> >> ] at
>> com.sun.tools.javac.file.JavacFileManager$1.make(JavacFileManager.jav
>> >>
>> >> ] at com.sun.tools.javac.util.Context.get(Context.java:147)
>> >> ] at com.sun.tools.javac.util.Context.get(Context.java:190)
>> >> ] at com.sun.tools.javac.main.Main.compile(Main.java:422)
>> >> ] at com.sun.tools.javac.main.Main.compile(Main.java:353)
>> >> ] at com.sun.tools.javac.main.Main.compile(Main.java:342)
>> >> ] at com.sun.tools.javac.main.Main.compile(Main.java:333)
>> >> ] at com.sun.tools.javac.Main.compile(Main.java:94)
>> >> ] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> ] at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >> 7)
>> >> ] at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> >> l.java:43)
>> >> ] at java.lang.reflect.Method.invoke(Method.java:606)
>> >> ] at
>> org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(Jav
>> >> iler.java:549)
>> >> ] at
>> org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompile
>> >> :156)
>> >> ] at
>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompiler
>> >> ava:605)
>> >> ] at
>> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
>> >> ] at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
>> >> luginManager.java:133)
>> >> ] at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
>> >> 208)
>> >> ] at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
>> >> 153)
>> >> ] -> [Help 1]
>> >> ]
>> >>
>> >> ] To see the full stack trace of the errors, re-run Maven with the -e
>> swit
>> >>
>> >> ] Re-run Maven using the -X switch to enable full debug logging.
>> >> ]
>> >>
>> >> ] For more information about the errors and possible solutions, please
>> rea
>> >> following articles:
>> >> ] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>> >>
>> >> ]
>> >>
>> >> ] After correcting the problems, you can resume the build with the
>> command
>> >>
>> >> ]   mvn <goals> -rf :org.apache.stanbol.commons.web.resources
>> >>
>> >>
>> >>
>> >> On Tue, Apr 8, 2014 at 4:22 PM, Bhoomin Pandya <
>> bhoominpan...@gmail.com>wrote:
>> >>
>> >>> Earlier ones were MojoExecutionException, etc
>> >>>
>> >>> This time I didn't copy the output.
>> >>>
>> >>> When I run it again I will keep the error message copy.
>> >>>
>> >>> currently one installation is going on for eclipse mvn
>> eclipse:eclipse. I
>> >>> am trying if I need a project to start a server instance 8080. I
>> already
>> >>> tried with an svn project in the stanbol directory.
>> >>>
>> >>> I know I am lost but I am trying to figure out.
>> >>>
>> >>> Bhoomin
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Apr 8, 2014 at 4:06 PM, Furkan KAMACI <furkankam...@gmail.com
>> >wrote:
>> >>>
>> >>>> Hi;
>> >>>>
>> >>>> What error do you get?
>> >>>>
>> >>>> Thanks;
>> >>>> Furkan KAMACI
>> >>>>
>> >>>>
>> >>>> 2014-04-08 13:31 GMT+03:00 Bhoomin Pandya <bhoominpan...@gmail.com>:
>> >>>>
>> >>>> > Hi Rupert:
>> >>>> >
>> >>>> > Your clues are helpful in clearing some issues like SVN etc.But
>> still
>> >>>> need
>> >>>> > some more guidelines.
>> >>>> >
>> >>>> > I have Window 7 64bit Home Premium. Java and Maven installed with
>> >>>> > environment variables set as per instruction on Stanbol and IKS
>> >>>> > Installation tutorial:
>> >>>> >
>> >>>> > 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
>> >>>> >
>> >>>> > My Java Version is
>> >>>> > java version "1.7.0_51"
>> >>>> > Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
>> >>>> > Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
>> >>>> >
>> >>>> > I tried using the 4 tags suggested by you. I have downloaded the
>> tags,
>> >>>> > trunk and enhancer using SVN. I face difficulty downloading the [4]
>> >>>> > http://dev.iks-project.eu/downloads/stanbol-launchers/
>> >>>> >
>> >>>> > c\......\stanbol> mvn clean install
>> >>>> > gives build failure.
>> >>>> >
>> >>>> > Kindly help.
>> >>>> > Many Thanks,
>> >>>> >
>> >>>> > Best Regards,
>> >>>> > Bhoomin Pandya
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > On Mon, Apr 7, 2014 at 9:54 PM, Bhoomin Pandya <
>> >>>> bhoominpan...@gmail.com
>> >>>> > >wrote:
>> >>>> >
>> >>>> > > Many Thanks Rupert. I appreciate your help.
>> >>>> > >
>> >>>> > > I shall try and let yo know.
>> >>>> > >
>> >>>> > > Best Regards,
>> >>>> > > Bhoomin
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > > On Mon, Apr 7, 2014 at 6:14 PM, Rupert Westenthaler <
>> >>>> > > rupert.westentha...@gmail.com> wrote:
>> >>>> > >
>> >>>> > >> Hi Bhoomin,
>> >>>> > >>
>> >>>> > >> Just to be sure I updated my maven version to 3.2.1 (from
>> 3.0.3).
>> >>>> > >> After the update the builds for 0.12.0 (release - i used the
>> tag [1]
>> >>>> > >> and not the download), the 0.12 branch (r1585465) as well as the
>> >>>> trunk
>> >>>> > >> [3] (also r1585465) where all fine.
>> >>>> > >>
>> >>>> > >> mvn -version
>> >>>> > >>   Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>> >>>> > >>   Java version: 1.7.0_45, vendor: Oracle Corporation
>> >>>> > >>   Java home:
>> >>>> > >>
>> /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre
>> >>>> > >>   Default locale: en_US, platform encoding: UTF-8
>> >>>> > >>   OS name: "mac os x", version: "10.9.2", arch: "x86_64",
>> family:
>> >>>> "unix"
>> >>>> > >>
>> >>>> > >>
>> >>>> > >> For the first error you reported
>> >>>> > >>
>> >>>> > >> > [ERROR] java.lang.NoClassDefFoundError:
>> >>>> > >> com/sun/jersey/server/impl/provider/RuntimeDelegateImpl
>> >>>> > >>
>> >>>> > >> a google search suggested that this is related to the set
>> context
>> >>>> > >> class loader in the unit test environment. As I do not see this
>> it
>> >>>> > >> might be dependent to your platform and JVM version.
>> >>>> > >>
>> >>>> > >> On Mon, Apr 7, 2014 at 6:41 AM, Bhoomin Pandya <
>> >>>> bhoominpan...@gmail.com
>> >>>> > >
>> >>>> > >> wrote:
>> >>>> > >> > Dear Mr. Furkan Kamaci
>> >>>> > >> >
>> >>>> > >> > I have Stanbol (apache-stanbol-0.12.0-source-release) which
>> when
>> >>>> > >> installed
>> >>>> > >> > using "mvn clean install" from the directory specified, shows
>> >>>> > >> > MojoExecutionException error with instructions to run
>> installation
>> >>>> > with
>> >>>> > >> -e
>> >>>> > >> > and -X switch. With this also I am facing the life cycle goal
>> >>>> error.
>> >>>> > >> >
>> >>>> > >>
>> >>>> > >> can you provide more information about the
>> MojoExecutionException
>> >>>> > >> (module, stack trace ...)
>> >>>> > >>
>> >>>> > >> >
>> >>>> > >> > Please enlighten how should I go about.
>> >>>> > >> >
>> >>>> > >>
>> >>>> > >> While resolving those issues you can use one of the binary
>> launcher
>> >>>> > >> downloads provided at [4]
>> >>>> > >>
>> >>>> > >> best
>> >>>> > >> Rupert
>> >>>> > >>
>> >>>> > >> [1]
>> >>>> https://svn.apache.org/repos/asf/stanbol/tags/apache-stanbol-0.12
>> >>>> > >> [2]
>> https://svn.apache.org/repos/asf/stanbol/branches/release-0.12
>> >>>> > >> [3] https://svn.apache.org/repos/asf/stanbol/trunk
>> >>>> > >> [4] http://dev.iks-project.eu/downloads/stanbol-launchers/
>> >>>> > >>
>> >>>> > >> --
>> >>>> > >> | Rupert Westenthaler             rupert.westentha...@gmail.com
>> >>>> > >> | Bodenlehenstraße 11                              +
>> >>>> +43-699-11108907+43-699-11108907
>> >>>> > >> | A-5500 Bischofshofen
>> >>>> > >> |
>> >>>> >
>> >>>>
>> REDLINK.CO..........................................................................
>> >>>> > >> | http://redlink.co/
>> >>>> > >>
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>
>> >>>
>> >>
>> > Call
>> > Send SMS
>> > Add to Skype
>> > You'll need Skype CreditFree via Skype
>>
>>
>>
>> --
>> | Rupert Westenthaler             rupert.westentha...@gmail.com
>> | Bodenlehenstraße 11                              ++43-699-11108907
>> | A-5500 Bischofshofen
>> | 
>> REDLINK.CO..........................................................................
>> | http://redlink.co/
>>
>
>

Reply via email to