Actually, if someone with a decent internet connection could try to checkout the current API trunk, and run mvn release:prepare (for 1.0.0) followed by mvn release:perform, just to check if it's not that I just have a slow connection, that would be cool !
Thanks ! On Thu, Jun 1, 2017 at 10:22 AM, Emmanuel Lecharny <[email protected]> wrote: > I'm still stuck :/ > > - when using project-39, with maven-surefire-plugin 2.19.1, it fails. > - when using project-40, whith maven-surefire-plugin 2.18.1, failure again > - the previous release (1.0.0-RC2) was using preoject-36, which was using > maven-surefire-plugin 2.19.1, and it worked... > > Now, here is what can be done : > - revert the version changes for the felix and pax dependencies, to have > them back to their version used in 1.0.0-RC2 > - or simply comment the integ-osgi module temporarily (or in package mode). > > The thing is that when I run the tests, or mvn:perform in dry test, or > mvn:prepare, everything goes well. The failure is really when I do the > perform, so there must be something else going on that impact various parts > of maven... > > Waiting for suggestions ... > > > On Wed, May 31, 2017 at 7:33 PM, Emmanuel Lecharny <[email protected]> > wrote: > >> Sorry, I made a mistake : the maven-checkstyle-plugin version to use is >> 2.17, not 3.0.1. >> >> On Wed, May 31, 2017 at 7:30 PM, Emmanuel Lecharny <[email protected]> >> wrote: >> >>> Ok, I've checked with Studio, and it was not as easy as expected. I had >>> to downgrade some of the versions : >>> - slf4j 1.8.0-alpha2 does not please Eclipse version scheme, so I used >>> 1.7.25 instead >>> - bcprov (used by apacheDS) *must* use version 1.56, as 1.57 is for Java >>> 9, which is not accepted by eclipse. >>> >>> Here are the plugins I have upgraded in 'project' 39-SNAPSHOT : >>> >>> o maven-assembly-plugin : 2.6 -> 3.0.0 >>> o maven-checkstyle-plugin : 2.17-> 3.0.1 >>> o checkstyle : 7.2 -> 7.8 >>> o maven-compiler-plugin : 3.6.0 -> 3.6.1 >>> o maven-dependency-plugin : 2.10 -> 3.0.1 >>> o maven-pmd-plugin : 3.7 -> 3.8 >>> o maven-resources-plugin : 3.0.1 -> 3.0.2 >>> o maven-shade-plugin : 2.4.3 -> 3.0.0 >>> o maven-site-plugin : 3.5.1 -> 3.6 >>> o maven-surefire-plugin : 2.18.1 -> 2.19.1 >>> o maven-war-plugin : 3.0.0 -> 3.1.0 >>> o maven-bundle-plugin : 3.2.0 -> 3.3.0 >>> o modello-maven-plugin : 1.8.3 -> 1.9.1 >>> o build-helper-maven-plugin : 1.12 -> 3.0.0 >>> >>> Changes in LDAP API : >>> >>> o logback : 1.1.8 -> 1.2.3 >>> o org.apache.felix : 5.6.1 -> 5.6.4 >>> o pax-exam : 4.9.2 -> 4.11.0 >>> o slf4j.api : 1.7.22 -> 1.7.25 >>> o slf4j.log4j12 : 1.7.22 -> 1.7.25 >>> >>> Changes in ApacheDS : >>> >>> o ant : 1.10.0 -> 1.10.1 >>> o commons.cli : 1.3.1 -> 1.4 >>> o commons.net : 3/5 -> 3.6 >>> o ehcache : 2.10.3 -> 2.10.4 >>> o jetty : 9.2.16.v20160414 -> 9.4.5.v20170502 >>> o logback : 1.1.8 -> 1.2.3 >>> o org.apache.felix : 5.6.1 -> 5.6.4 >>> o pax-exam : 4.9.2 -> 4.11.0 >>> o slf4j.api : 1.7.22 -> 1.7.25 >>> o slf4j.log4j12 : 1.7.22 -> 1.7.25 >>> >>> and finally changes in Studio : >>> >>> o net.sf.ehcache : 2.10.3 -> 2.10.4 >>> o org.slf4j : 1.7.22 -> 1.7.25 >>> >>> >>> I will release project-39 now. >>> >>> >>> On Wed, May 31, 2017 at 9:23 AM, Emmanuel Lécharny <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> >>>> I will try to run the release with a mre recent version of the surefire >>>> plugi (see the comment from Tibor on >>>> https://issues.apache.org/jira/browse/SUREFIRE-1302). >>>> >>>> >>>> At the same time, I have bumped up a few plugins in the 'project' >>>> project, so I may have to release it first. Probably this afternoon, or >>>> evening. Tests are passing with the changes I have made on the API and >>>> ApacheDS, I'll check with Studio and Fortress later on. >>>> >>>> >>>> >>>> >>>> Le 30/05/2017 à 11:31, Colm O hEigeartaigh a écrit : >>>> > Hi Emmanuel, >>>> > >>>> > We ran into that same error in the OSGi tests in CXF. We had to >>>> downgrade >>>> > to Surefire 2.18.1 to get it to work afaik. >>>> > >>>> > Colm. >>>> > >>>> > On Tue, May 30, 2017 at 10:25 AM, Emmanuel Lécharny < >>>> [email protected]> >>>> > wrote: >>>> > >>>> >> Hi guys, >>>> >> >>>> >> >>>> >> I'm facing some issue with the mvn release:perform : >>>> >> >>>> >> >>>> >> [INFO] ------------------------------------------------------- >>>> >> [INFO] T E S T S >>>> >> [INFO] ------------------------------------------------------- >>>> >> [INFO] Running org.apache.directory.api.osgi.ApiAsn1ApiOsgiTest >>>> >> [INFO] >>>> >> ... >>>> >> >>>> >> [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time >>>> elapsed: >>>> >> 1.119 sec - in org.apache.directory.api.osgi.ApiLdapNetMinaOsgiTest >>>> >> [INFO] Running org.apache.directory.api.osgi. >>>> >> ApiLdapSchemaConverterOsgiTest >>>> >> [INFO] >>>> >> [INFO] [SUREFIRE] std/in stream corrupted >>>> >> [INFO] java.io.IOException: Command NOOP unexpectedly read Void data >>>> >> with length 4. >>>> >> [INFO] at >>>> >> org.apache.maven.surefire.booter.MasterProcessCommand. >>>> >> decode(MasterProcessCommand.java:139) >>>> >> [INFO] at >>>> >> org.apache.maven.surefire.booter.CommandReader$CommandRunnable.run( >>>> >> CommandReader.java:360) >>>> >> [INFO] at java.lang.Thread.run(Thread.java:745) >>>> >> [INFO] >>>> >> [INFO] Results : >>>> >> [INFO] >>>> >> [INFO] Tests run: 50, Failures: 0, Errors: 0, Skipped: 0 >>>> >> ... >>>> >> >>>> >> [INFO] [INFO] Apache Directory API OSGi Integration Tests ........ >>>> >> FAILURE [ 21.710 s] >>>> >> [INFO] [INFO] Apache Directory LDAP API Distribution ............. >>>> SKIPPED >>>> >> [INFO] [INFO] >>>> >> ------------------------------------------------------------ >>>> ------------ >>>> >> [INFO] [INFO] BUILD FAILURE >>>> >> [INFO] [INFO] >>>> >> ------------------------------------------------------------ >>>> ------------ >>>> >> [INFO] [INFO] Total time: 15:35 min >>>> >> [INFO] [INFO] Finished at: 2017-05-30T11:10:32+02:00 >>>> >> [INFO] [INFO] Final Memory: 78M/304M >>>> >> [INFO] [INFO] >>>> >> ------------------------------------------------------------ >>>> ------------ >>>> >> [INFO] [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? >>>> >> harny/apacheds/trunks/shared/target/checkout/integ-osgi/ >>>> >> target/surefire/surefire_158862987326254246739tmp >>>> >> ... >>>> >> >>>> >> and of course, I just can't re-run from the last module :/ >>>> >> >>>> >> >>>> >> It might be related to https://issues.apache.org/jira >>>> /browse/SUREFIRE-1302 >>>> >> >>>> >> Anyone has an idea ? >>>> >> >>>> >> >>>> >> -- >>>> >> Emmanuel Lecharny >>>> >> >>>> >> Symas.com >>>> >> directory.apache.org >>>> >> >>>> >> >>>> > >>>> >>>> -- >>>> Emmanuel Lecharny >>>> >>>> Symas.com >>>> directory.apache.org >>>> >>>> >>> >>> >>> -- >>> Regards, >>> Cordialement, >>> Emmanuel Lécharny >>> www.iktek.com >>> >> >> >> >> -- >> Regards, >> Cordialement, >> Emmanuel Lécharny >> www.iktek.com >> > > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
