Le 03/06/2017 à 02:41, Brian Burch a écrit : > On 02/06/17 20:46, Emmanuel Lécharny wrote: >> >> >> Le 02/06/2017 à 12:27, Brian Burch a écrit : >>> On 02/06/17 20:13, Emmanuel Lécharny wrote: >>>> >>>> >>>> Le 02/06/2017 à 12:07, Brian Burch a écrit : >>>>> On 02/06/17 18:33, Emmanuel Lécharny wrote: please retry with the >>>>> correct tag, you should get better result ! >>>>> >>>>> Yes, much better! >>>>> >>>>> I ran "mvn install", but it still comes up with two "failures":- >>>>> >>>>> [INFO] Apache Directory API OSGi Integration Tests 2 ...... SKIPPED >>>>> [INFO] Apache Directory LDAP API Distribution ............. SKIPPED >>>>> >>>>> Is that as expected? >>>>> >>>>> If yes, then I'll vote with +1 >>>>> >>>>> under:- >>>>> >>>>> openjdk version "1.8.0_131" >>>>> >>>>> Ubuntu 17.04 zesty >>>>> >>>>> GNU/Linux 4.10.0-21-generic #23-Ubuntu SMP x86_64 >>>>> >>>>> I hope that is helpful. I don't have time at the moment to do any >>>>> additional tests, but I'll do more with the server release when it is >>>>> available. >>>> >>>> Can you paste (or pastebin) the complete trace ? >>>> >>>> thanks ! >>> >>> Not sure what you mean by "trace". I searched around the subdirs but >>> didn't find anything obviously relevant. Here is the maven error log >>> at the end:- >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test >>> (default-test) on project api-integ-osgi: Execution default-test of >>> goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test >>> failed: The forked VM terminated without properly saying goodbye. VM >>> crash or System.exit called? >>> [ERROR] Command was /bin/sh -c cd >>> /home/brian/sandboxApache/ldap-api-1.0.0/integ-osgi && >>> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -Xmx1024m -jar >>> /home/brian/sandboxApache/ldap-api-1.0.0/integ-osgi/target/surefire/surefirebooter4909386868402849707.jar >>> >>> /home/brian/sandboxApache/ldap-api-1.0.0/integ-osgi/target/surefire/surefire4278794732828919115tmp >>> >>> /home/brian/sandboxApache/ldap-api-1.0.0/integ-osgi/target/surefire/surefire_157652920615491644248tmp >>> >>> >>> [ERROR] -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with >>> the -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException >>> >>> [ERROR] >>> [ERROR] After correcting the problems, you can resume the build with >>> the command >>> [ERROR] mvn <goals> -rf :api-integ-osgi >>> >>> Is that sufficient? >> Yes. This is a maven surefire random issue >> (https://issues.apache.org/jira/browse/SUREFIRE-1374 and also see >> https://issues.apache.org/jira/browse/SUREFIRE-1302). >> >> I was lucky yesterday not to be hit by it when I finally cut the >> release. It seems they have a fix for it, with a surefire SNAPSHOT >> available. One option for you would be to test the release with this >> SNAPSHOT > > It has been a long time since I last worked with maven, so it took me > a while to figure out that your request was very simple! Also, because > I am in Australia (GMT+10) we are usually a whole day out of synch. > > I added the following to the api pom.xml pluginManagement section for > the maven-surefire-report-plugin artifact: > > <version>2.19.1</version> > > Then I simply re-ran "mvn install":- > > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Directory LDAP API .......................... SUCCESS [ > 1.450 s] > [INFO] Apache Directory LDAP API I18n ..................... SUCCESS [ > 1.262 s] > [INFO] Apache Directory LDAP API Utilities ................ SUCCESS [ > 1.917 s] > [INFO] Apache Directory API ASN.1 Parent .................. SUCCESS [ > 0.059 s] > [INFO] Apache Directory API ASN.1 API ..................... SUCCESS [ > 1.020 s] > [INFO] Apache Directory API ASN.1 BER ..................... SUCCESS [ > 1.084 s] > [INFO] Apache Directory LDAP API Parent ................... SUCCESS [ > 0.072 s] > [INFO] Apache Directory LDAP API Model .................... SUCCESS [ > 11.240 s] > [INFO] Apache Directory LDAP API Codec Parent ............. SUCCESS [ > 0.046 s] > [INFO] Apache Directory LDAP API Codec Core ............... SUCCESS [ > 2.187 s] > [INFO] Apache Directory LDAP API Net Parent ............... SUCCESS [ > 0.058 s] > [INFO] Apache Directory LDAP API Network MINA ............. SUCCESS [ > 0.314 s] > [INFO] Apache Directory LDAP API Extras ................... SUCCESS [ > 0.038 s] > [INFO] Apache Directory LDAP API Extras Codec API ......... SUCCESS [ > 0.415 s] > [INFO] Apache Directory LDAP API Extras Codec ............. SUCCESS [ > 2.070 s] > [INFO] Apache Directory LDAP API Codec Standalone ......... SUCCESS [ > 0.932 s] > [INFO] Apache Directory LDAP API DSML Parent .............. SUCCESS [ > 0.034 s] > [INFO] Apache Directory LDAP API DSML Parser .............. SUCCESS [ > 2.181 s] > [INFO] Apache Directory LDAP API Extras ACI ............... SUCCESS [ > 1.187 s] > [INFO] Apache Directory LDAP API Schema Parent ............ SUCCESS [ > 0.037 s] > [INFO] Apache Directory LDAP API Schema Data .............. SUCCESS [ > 4.219 s] > [INFO] Apache Directory LDAP API Client Parent ............ SUCCESS [ > 0.035 s] > [INFO] Apache Directory LDAP API Client API ............... SUCCESS [ > 2.766 s] > [INFO] Apache Directory LDAP API DSML Engine .............. SUCCESS [ > 0.392 s] > [INFO] Apache Directory LDAP API Extras Util .............. SUCCESS [ > 0.872 s] > [INFO] Apache Directory LDAP API Extras Stored Procedures . SUCCESS [ > 0.294 s] > [INFO] Apache Directory LDAP API Extras Trigger ........... SUCCESS [ > 0.933 s] > [INFO] Apache Directory LDAP API Schema Converter ......... SUCCESS [ > 1.999 s] > [INFO] Apache Directory API All ........................... SUCCESS [ > 0.974 s] > [INFO] Apache Directory LDAP API Client All ............... SUCCESS [ > 3.082 s] > [INFO] Apache Directory API Integration Tests ............. SUCCESS [ > 4.918 s] > [INFO] Apache Directory API OSGi Integration Tests ........ SUCCESS [ > 11.006 s] > [INFO] Apache Directory API OSGi Integration Tests 2 ...... SUCCESS [ > 12.975 s] > [INFO] Apache Directory LDAP API Distribution ............. SUCCESS [ > 0.281 s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 01:13 min > [INFO] Finished at: 2017-06-03T10:07:41+10:00 > [INFO] Final Memory: 112M/1954M > > > I can see from the surefire JIRAs you've been onto this problem for a > while, so well done for chasing it down! > > The 2.19.1 version is dated December 2015, which makes it pretty old. > The SureFire project released a 2.20 version in April 2017. I updated > my pom.xml and re-ran the install with this version - not > surprisingly, the build was successful too. > > I'll leave it up to you to decide which version of surefire ought to > be used in our official API 1.0.0. release.
Actually, none of those versions are good to go. It's really a question of luck for the build to pass - or not -. The maven build depends on a side project, named 'project' , that fixes all the maven plugin version. If you look at http://svn.apache.org/repos/asf/directory/trunks, which pulls all the subprojects (API aka shared, apacheds, mavibot and a few others), you'll see that wealso pull 'project', which contains a POM file itself containing : <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.19.1</version> <configuration> <argLine>-Xmx1024m</argLine> </configuration> </plugin> I have ried with 2.18.1, same kind of (random) trouble. I do think we will have to wait for a 2.21 version to fix this random error. -- Emmanuel Lecharny Symas.com directory.apache.org
