RE: Can't build wicket from updated trunk
Dumping the environment variables shows only these maven related variables are set: M2 M2_HOME I can't see any other places where MAVEN_OPTS is being set. Nothing in maven's settings.xml that refers to any JVM heap size options. I noticed my version of maven is 2.2.1 dated 2009-08-07 so maybe I should update to the latest maven release and see if it establishes a larger default JVM heap size. -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Monday, 2 January 2012 6:44 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk I don't set any JVM settings to be able to build Wicket... @Chris: do you have some globally exported MAVEN_OPTS which may interfere ? On Mon, Jan 2, 2012 at 6:52 AM, Matthias Gasser matthias.gas...@gmail.com wrote: You need to increase the heap space for maven. Just run the following line prior building: snip set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m snap That should bring you through. -matthias Am 02.01.2012 um 05:43 schrieb Chris Colman: I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] - --- [ERROR] BUILD FAILURE [INFO] - --- [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacComp iler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java :161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.j ava:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag er.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif ecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl e(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife cycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai lures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def aultLifecycleExecutor.java:348) -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:50 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk already moved. -igor On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2
RE: Can't build wicket from updated trunk
Well it certainly works a lot better with Maven 3.0.3! ;) It still can't build core because of some test failures: Running org.apache.wicket.protocol.http.StoredResponsesMapTest Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 19.351 sec FAILURE! Running org.apache.wicket.VisitorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.wicket.ajax.AjaxBehaviorAndMetaDataTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec Running org.apache.wicket.page.PageAccessSynchronizerTest Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.488 sec FAILURE! Results : Failed tests: getExpiredValue(org.apache.wicket.protocol.http.StoredResponsesMapTest) testBlocking(org.apache.wicket.page.PageAccessSynchronizerTest) Tests run: 1264, Failures: 2, Errors: 0, Skipped: 2 -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Monday, 2 January 2012 6:44 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk I don't set any JVM settings to be able to build Wicket... @Chris: do you have some globally exported MAVEN_OPTS which may interfere ? On Mon, Jan 2, 2012 at 6:52 AM, Matthias Gasser matthias.gas...@gmail.com wrote: You need to increase the heap space for maven. Just run the following line prior building: snip set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m snap That should bring you through. -matthias Am 02.01.2012 um 05:43 schrieb Chris Colman: I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] - --- [ERROR] BUILD FAILURE [INFO] - --- [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacComp iler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java :161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.j ava:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag er.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif ecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl e(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife cycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai lures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def aultLifecycleExecutor.java
Re: Can't build wicket from updated trunk
skip the tests with -Dmaven.test.skip=true -igor On Mon, Jan 2, 2012 at 10:11 AM, Chris Colman chr...@stepaheadsoftware.com wrote: Well it certainly works a lot better with Maven 3.0.3! ;) It still can't build core because of some test failures: Running org.apache.wicket.protocol.http.StoredResponsesMapTest Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 19.351 sec FAILURE! Running org.apache.wicket.VisitorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec Running org.apache.wicket.ajax.AjaxBehaviorAndMetaDataTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec Running org.apache.wicket.page.PageAccessSynchronizerTest Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.488 sec FAILURE! Results : Failed tests: getExpiredValue(org.apache.wicket.protocol.http.StoredResponsesMapTest) testBlocking(org.apache.wicket.page.PageAccessSynchronizerTest) Tests run: 1264, Failures: 2, Errors: 0, Skipped: 2 -Original Message- From: Martin Grigorov [mailto:mgrigo...@apache.org] Sent: Monday, 2 January 2012 6:44 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk I don't set any JVM settings to be able to build Wicket... @Chris: do you have some globally exported MAVEN_OPTS which may interfere ? On Mon, Jan 2, 2012 at 6:52 AM, Matthias Gasser matthias.gas...@gmail.com wrote: You need to increase the heap space for maven. Just run the following line prior building: snip set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m snap That should bring you through. -matthias Am 02.01.2012 um 05:43 schrieb Chris Colman: I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] - --- [ERROR] BUILD FAILURE [INFO] - --- [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacComp iler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java :161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.j ava:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag er.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif ecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl e(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife cycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai lures
Can't build wicket from updated trunk
I have done a recent update on my working copy of the trunk and mvn clean install yields: Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? Yours sincerely, Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together Sydney: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au mailto://chr...@stepahead.com.au Website: http://www.pagebloom.com blocked::http://www.pagebloom.com/ http://develop.stepaheadsoftware.com blocked::http://develop.stepaheadsoftware.com/
Re: Can't build wicket from updated trunk
clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar ** ** ** ** Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? ** ** Yours sincerely, ** ** Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together ** ** **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au //chr...@stepahead.com.au Website: http://www.pagebloom.com http://develop.stepaheadsoftware.com ** **
RE: Can't build wicket from updated trunk
Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:24 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar ** ** ** ** Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? ** ** Yours sincerely, ** ** Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together ** ** **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au //chr...@stepahead.com.au Website: http://www.pagebloom.com http://develop.stepaheadsoftware.com ** ** - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Can't build wicket from updated trunk
already moved. -igor On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:24 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar ** ** ** ** Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? ** ** Yours sincerely, ** ** Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together ** ** **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au //chr...@stepahead.com.au Website: http://www.pagebloom.com http://develop.stepaheadsoftware.com ** ** - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Can't build wicket from updated trunk
I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:50 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk already moved. -igor On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:24 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar ** ** ** ** Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? ** ** Yours sincerely, ** ** Chris Colman Pagebloom Team Leader, Step Ahead Software pagebloom - your business your website growing together ** ** **Sydney**: (+61 2) 9656 1278 Canberra: (+61 2) 6100 2120 Email: chr...@stepahead.com.au //chr...@stepahead.com.au Website: http://www.pagebloom.com
Re: Can't build wicket from updated trunk
You need to increase the heap space for maven. Just run the following line prior building: snip set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m snap That should bring you through. -matthias Am 02.01.2012 um 05:43 schrieb Chris Colman: I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:50 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk already moved. -igor On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:24 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version' is missing for javax.inject:javax.inject:jar ** ** ** ** Have I done something wrong or do I need to upgrade to a later JDK (currently 1.6.0_29-b11)? ** ** Yours sincerely
Re: Can't build wicket from updated trunk
I don't set any JVM settings to be able to build Wicket... @Chris: do you have some globally exported MAVEN_OPTS which may interfere ? On Mon, Jan 2, 2012 at 6:52 AM, Matthias Gasser matthias.gas...@gmail.com wrote: You need to increase the heap space for maven. Just run the following line prior building: snip set MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=128m snap That should bring you through. -matthias Am 02.01.2012 um 05:43 schrieb Chris Colman: I cloned the wicket git repos and then checked out branch wicket-1.5.x branch and the build broke in a different place (it got a bit further this time :) ) The build was done on a Windows XP box with 4GB RAM so I wouldn't have thought it would have run out of memory. [INFO] 1 error [INFO] - [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation 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: Java heap space at com.sun.tools.javac.code.Scope$ImportScope.makeEntry(Scope.java:385) at com.sun.tools.javac.code.Scope.enter(Scope.java:196) at com.sun.tools.javac.code.Scope.enter(Scope.java:183) at com.sun.tools.javac.comp.MemberEnter.importAll(MemberEnter.java:132) at com.sun.tools.javac.comp.MemberEnter.visitTopLevel(MemberEnter.java:509) at com.sun.tools.javac.tree.JCTree$JCCompilationUnit.accept(JCTree.java:446) at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:387) at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:819) at com.sun.tools.javac.code.Symbol.complete(Symbol.java:386) at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:758) at com.sun.tools.javac.comp.Enter.complete(Enter.java:451) at com.sun.tools.javac.comp.Enter.main(Enter.java:429) at com.sun.tools.javac.main.JavaCompiler.enterTrees(JavaCompiler.java:819) at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:727) at com.sun.tools.javac.main.Main.compile(Main.java:353) at com.sun.tools.javac.main.Main.compile(Main.java:279) at com.sun.tools.javac.main.Main.compile(Main.java:270) at com.sun.tools.javac.Main.compile(Main.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:554) at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:161) at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:605) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:50 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk already moved. -igor On Sun, Jan 1, 2012 at 7:31 PM, Chris Colman chr...@stepaheadsoftware.com wrote: Is Wicket moving to git? Chris -Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Monday, 2 January 2012 2:24 PM To: users@wicket.apache.org Subject: Re: Can't build wicket from updated trunk clone the project from here: http://git-wip-us.apache.org/repos/asf/wicket -igor On Sun, Jan 1, 2012 at 6:09 PM, Chris Colman chr...@stepaheadsoftware.comwrote: ** ** I have done a recent update on my working copy of the trunk and mvn clean install yields: ** ** Project ID: org.apache.wicket:wicket-ioc POM Location: C:\dev\libs\wicket\trunk\wicket-ioc\pom.xml Validation Messages: ** ** [0] 'dependencies.dependency.version
