On Nov 19, 2012, at 1:49 PM, Stadelmann Josef <[email protected]> wrote:
> Colm, > > just updated the cxf/trunk and rerun the cxf/trunk build. > this time with a fresh built wss4j-1.6.7 in .m2\repository > (including surefire testing) and strong encryption policy files on-site > (under Vista / JDK1.7.0_03 / maven 3.0.5 ) > > The build of cxf just completed successfully after 2 restarts due to "out of > memory" > > it takes time on my little machine, and I need a bigger one, or a better > tuning of > the memory parameters for the JVM running maven. We have some information at: http://cxf.apache.org/building.html In general, we use: set MAVEN_OPTS=-Xmx768M -XX:MaxPermSize=192M On that page lists some of the additional targets (like -Pfastinstall) that you can use if you just want to get the jars installed as quick as possible without all the tests. Note that CXF also uses dynamic ports for all the tests. Thus, on a multi-core machine, you can use the Maven parallel builds. For example, on my (admitted very high end) MacBook Pro, I usually run "mvn -Pnochecks -T 8" which will build and run everything, but using 8 threads. That completes in just over 6 minutes or so. Dan > (BTW: what are your recommendations for a 4 GB Vista machine ?) > > BUT most important: > > cxf/trunk build has passed to successful completion. > > so your cxf/trunk commitments show effect. > > Josef > > > > > > -----Ursprüngliche Nachricht----- > Von: Colm O hEigeartaigh [mailto:[email protected]] > Gesendet: Montag, 19. November 2012 17:39 > An: [email protected] > Betreff: Re: [cxf] trunk and tags/2.7.0 > > I've just committed a potential fix. Could you try building trunk again? > > Colm. > > On Mon, Nov 19, 2012 at 1:51 PM, Stadelmann Josef < > [email protected]> wrote: > >> Sorry my fault, I was looking somehow skew to the version output. >> in fact what I described below was attempted with mvn 3.0.5 on Vista, >> (would be 2.2.1 on OpenVMS but that is not the point yet). >> So the version of maven might not be the problem. I would also update >> to maven-3.1 but that bootstrap-build of maven fails at my site. >> >> So I hope that the version of maven given below should make it? >> >> E:\asf\cxf\tags\cxf-2.7.0>mvn -version Apache Maven 3.0.5-SNAPSHOT >> (r1297401; 2012-03-06 12:23:19+0100) Maven home: >> E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5 >> Java version: 1.6.0_30, vendor: Sun Microsystems Inc. >> Java home: E:\Users\C770817\SW-UMGEBUNG\Java\jdk1.6.0_30\jre >> Default locale: de_CH, platform encoding: Cp1252 OS name: "windows >> vista", version: "6.0", arch: "x86", family: "windows" >> 'cmd' is not recognized as an internal or external command, operable >> program or batch file. >> E:\asf\cxf\tags\cxf-2.7.0> >> >> >> -----Ursprüngliche Nachricht----- >> Von: Colm O hEigeartaigh [mailto:[email protected]] >> Gesendet: Montag, 19. November 2012 14:43 >> An: [email protected] >> Betreff: Re: [cxf] trunk and tags/2.7.0 >> >> You must build with at least Maven 3.0. >> >> Colm. >> >> On Mon, Nov 19, 2012 at 1:25 PM, Stadelmann Josef < >> [email protected]> wrote: >> >>> Hy developers >>> >>> I just tried to build cxf from the trunk and as it failed from the >>> tags/cxf-2.7.0 using maven-2.2.1 && JDK_1.6.0_30 and it failed twice >>> at the same place on a Windows Vista System. >>> >>> Running org.apache.cxf.ws.security.wss4j.WSS4JFaultCodeTest >>> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >>> 1.035 sec <<< FAILURE! >>> testInvalidTimestamp(org.apache.cxf.ws.security.wss4j.WSS4JFaultCode >>> Te >>> st >>> ) Time elapsed: 1.02 sec <<< FAILURE! >>> java.lang.AssertionError: Expected failure on an invalid Timestamp >>> at org.junit.Assert.fail(Assert.java:93) >>> at >>> org.apache.cxf.ws.security.wss4j.WSS4JFaultCodeTest.testInvalidTimes >>> ta >>> mp >>> (WSS4JFaultCodeTest.java:171) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl >>> .j >>> av >>> a:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce >>> ss >>> or >>> Impl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:597) >>> at >>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framewor >>> kM >>> et >>> hod.java:45) >>> at >>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCa >>> ll >>> ab >>> le.java:15) >>> at >>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkM >>> et >>> ho >>> d.java:42) >>> at >>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMe >>> th >>> od >>> .java:20) >>> at >>> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores >>> .j >>> av >>> a:28) >>> at >>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java: >>> 30) >>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) >>> at >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRu >>> nn >>> er >>> .java:68) >>> at >>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRu >>> nn >>> er >>> .java:47) >>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) >>> at >>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) >>> at >>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) >>> at >>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) >>> at >>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) >>> at >>> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java: >>> 30) >>> at org.junit.runners.ParentRunner.run(ParentRunner.java:300) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provid >>> er >>> .j >>> ava:252) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit >>> 4P >>> ro >>> vider.java:141) >>> at >>> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider. >>> ja >>> va:112) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl >>> .j >>> av >>> a:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce >>> ss >>> or >>> Impl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:597) >>> at >>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray >>> (R >>> ef >>> lectionUtils.java:189) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invok >>> e( >>> Pr >>> oviderFactory.java:165) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(Prov >>> id >>> er >>> Factory.java:85) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(For >>> ke >>> dB >>> ooter.java:113) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java >>> :7 >>> 5) Running org.apache.cxf.ws.security.wss4j.WSS4JInOutTest >>> Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: >>> 0.297 sec >>> >>> >>> [INFO] Apache CXF Runtime UDP Transport .................. SUCCESS >>> [5.819s] [INFO] Apache CXF Runtime WS Reliable Messaging .......... >>> SUCCESS [52.329s] [INFO] Apache CXF Runtime WS MetadataExchange >>> ............ SUCCESS [5.772s] [INFO] Apache CXF Runtime WS Security >>> .................... FAILURE [57.194s] [INFO] Apache CXF JAX-RS >>> Extensions: Providers ........... SKIPPED [INFO] Apache CXF JAX-RS >>> Extensions: Search .............. SKIPPED [INFO] Apache CXF RS XML >>> Security ........................ SKIPPED >>> >>> Any special attentions preparations key-stores required or to be >>> consider/setup for WSS4J before it can be used in a cxf/trunk build. >>> >>> Josef - thanks full for any hint >>> >>> >>> >>> >>> >>> >> >> >> -- >> Colm O hEigeartaigh >> >> Talend Community Coder >> http://coders.talend.com >> > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
