Snapshot deployments by CI
I personally think there are a lot of issues with CI automatically deploying snapshots... Some of these issues a social, and some are not. Hervé, Olivier, I suggest we start by writing down the policy you think you want... i’ll poke holes, you fix or ack until we get a good compromise... then we can implement. Policy should cover: * what to do on different branches * who is responsible for snapshots and non snapshots Eg CI will auto deploy snapshots only on the master branch. Other branches manually with the version changed to include branch name as a qualifier. Releases will be deployed manually, ideally from the master branch only. -- Sent from my phone
Re: seconder on other fixes for Maven 3.5.3
+1 on all of those On Thu 8 Feb 2018 at 23:30, Hervé BOUTEMY wrote: > Hi, > > Here is a new list of fixes I'd like to merge: > > - update parent pom to version 31 > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/upgrade_parent_pom/ > > - MNG-6255 Maven script cannot parse jvm.config with CRLF > https://issues.apache.org/jira/browse/MNG-6255 > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6255/ > > - Jansi 1.17 upgrade, which fixes 3 Jira issues on encoding & MingW/GitBash > https://issues.apache.org/jira/browse/MNG-6320 > https://issues.apache.org/jira/browse/MNG-6282 > https://issues.apache.org/jira/browse/MNG-6218 > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6320_jansi-1.17/ > > - Mockito upgrade > https://issues.apache.org/jira/browse/MNG-6335 > > https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6335_Mockito_upgrade/ > > > Regards, > > Hervé > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
Re: Old Style Build Jobs
On 9 February 2018 at 06:54, Hervé BOUTEMY wrote: > Le vendredi 9 février 2018, 02:16:10 CET Olivier Lamy a écrit : > > Thanks! > > I will have a look for Wagon. > thank you > > > > > Do we deploy automatically SNAPSHOT or not? > currently not: I'd like to do it, I think it's natural > but Stephen, who masters the new Jenkins build configuration, is not > positive > on the idea > OMG it might be really complicated... :P > and nobody really started a clean discussion on that > > > because of jdk10 issue for surefire, I currently have external projects > > depending on those snapshot. > to be concrete, currently, when I want to consume a SNAPSHOT after a > release > has been done, I have to do manually the "mvn deploy" from my computer > and each time I did this, I can confirm that it was the first SNAPSHOT > that was > deployed (even if the release has been done a few weeks ago) > I'd like to have auto build of downstream projects as well... changes of a shared lib should rebuild plugins depending on it etc... > > > IMHO might be good to have auto deploy so quick feedback from early > > testers/adopters > +1 > > let's start the discussion: I'm convinced this is natural for a CI job to > deploy SNAPSHOTs automatically to SNAPSHOT repository > and after thinking at it seriously, I think the fear Stephen has is valid > only > on *triggering a build based on a new SNAPSHOT availability*, but not > really > on *deploying SNAPSHOTs as part of continuous build* > the only question to me is how to code it precisely, to be sure the deploy > happens only once (and not on each OS+JDK configuration), and as much as > possible only if the build is fully successful (here, IIUC, the detection > of > "successful build" is currently not reliable) > Regards, > > Hervé > > > > > On 8 February 2018 at 22:25, Hervé BOUTEMY > wrote: > > > ok, I did the cleanup > > > > > > Tibor, I think there is cleanup to do on Surefire jobs: don't hesitate > to > > > do it > > > > > > I don't know for Wagon jobs > > > > > > > > > The cleanup I didn't do is the cleanup on maven-master-release-* > > > https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ > > > > > > I just disabled the jobs: if nobody objects, I'll delete the jobs and > even > > > the > > > view in 1 week > > > > > > Regards, > > > > > > Hervé > > > > > > Le mercredi 24 janvier 2018, 07:41:32 CET Hervé BOUTEMY a écrit : > > > > Le mardi 23 janvier 2018, 20:57:42 CET Karl Heinz Marbaise a écrit : > > > > > >> 3. > > > > > >> https://builds.apache.org/view/M-R/view/Maven/job/core-> > > > > integration-test > > > > > > > > >> in > > > > > >> g-m aven-3-embedded/ > > > > > > > > > > > > I'd like to keep this one, since it's a reference in embedded > mode > > > > > > (faster > > > > > > execution) > > > > > > > > > > Our default Job for Maven Core [1] is running with embedded mode.. > > > > > > > > > > > > > > > [1]: https://builds.apache.org/job/maven-wip/job/maven/ > > > > > > > > ok, thanks for the info (I could have found myself...) > > > > > > > > then +1 to drop this job also > > > > > > > > and while at it > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven- > 3.x-jenkinsfile/ > > > > > > > > > > > > Regards, > > > > > > > > Hervé > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Old Style Build Jobs
Le vendredi 9 février 2018, 02:16:10 CET Olivier Lamy a écrit : > Thanks! > I will have a look for Wagon. thank you > > Do we deploy automatically SNAPSHOT or not? currently not: I'd like to do it, I think it's natural but Stephen, who masters the new Jenkins build configuration, is not positive on the idea and nobody really started a clean discussion on that > because of jdk10 issue for surefire, I currently have external projects > depending on those snapshot. to be concrete, currently, when I want to consume a SNAPSHOT after a release has been done, I have to do manually the "mvn deploy" from my computer and each time I did this, I can confirm that it was the first SNAPSHOT that was deployed (even if the release has been done a few weeks ago) > IMHO might be good to have auto deploy so quick feedback from early > testers/adopters +1 let's start the discussion: I'm convinced this is natural for a CI job to deploy SNAPSHOTs automatically to SNAPSHOT repository and after thinking at it seriously, I think the fear Stephen has is valid only on *triggering a build based on a new SNAPSHOT availability*, but not really on *deploying SNAPSHOTs as part of continuous build* the only question to me is how to code it precisely, to be sure the deploy happens only once (and not on each OS+JDK configuration), and as much as possible only if the build is fully successful (here, IIUC, the detection of "successful build" is currently not reliable) Regards, Hervé > > On 8 February 2018 at 22:25, Hervé BOUTEMY wrote: > > ok, I did the cleanup > > > > Tibor, I think there is cleanup to do on Surefire jobs: don't hesitate to > > do it > > > > I don't know for Wagon jobs > > > > > > The cleanup I didn't do is the cleanup on maven-master-release-* > > https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ > > > > I just disabled the jobs: if nobody objects, I'll delete the jobs and even > > the > > view in 1 week > > > > Regards, > > > > Hervé > > > > Le mercredi 24 janvier 2018, 07:41:32 CET Hervé BOUTEMY a écrit : > > > Le mardi 23 janvier 2018, 20:57:42 CET Karl Heinz Marbaise a écrit : > > > > >> 3. > > > > >> https://builds.apache.org/view/M-R/view/Maven/job/core-> > > > integration-test > > > > > > >> in > > > > >> g-m aven-3-embedded/ > > > > > > > > > > I'd like to keep this one, since it's a reference in embedded mode > > > > > (faster > > > > > execution) > > > > > > > > Our default Job for Maven Core [1] is running with embedded mode.. > > > > > > > > > > > > [1]: https://builds.apache.org/job/maven-wip/job/maven/ > > > > > > ok, thanks for the info (I could have found myself...) > > > > > > then +1 to drop this job also > > > > > > and while at it > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/ > > > > > > > > > Regards, > > > > > > Hervé > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Old Style Build Jobs
Thanks! I will have a look for Wagon. Do we deploy automatically SNAPSHOT or not? because of jdk10 issue for surefire, I currently have external projects depending on those snapshot. IMHO might be good to have auto deploy so quick feedback from early testers/adopters On 8 February 2018 at 22:25, Hervé BOUTEMY wrote: > ok, I did the cleanup > > Tibor, I think there is cleanup to do on Surefire jobs: don't hesitate to > do it > > I don't know for Wagon jobs > > > The cleanup I didn't do is the cleanup on maven-master-release-* > https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ > > I just disabled the jobs: if nobody objects, I'll delete the jobs and even > the > view in 1 week > > Regards, > > Hervé > > Le mercredi 24 janvier 2018, 07:41:32 CET Hervé BOUTEMY a écrit : > > Le mardi 23 janvier 2018, 20:57:42 CET Karl Heinz Marbaise a écrit : > > > >> 3. > > > >> https://builds.apache.org/view/M-R/view/Maven/job/core- > integration-test > > > >> in > > > >> g-m aven-3-embedded/ > > > > > > > > I'd like to keep this one, since it's a reference in embedded mode > > > > (faster > > > > execution) > > > > > > Our default Job for Maven Core [1] is running with embedded mode.. > > > > > > > > > [1]: https://builds.apache.org/job/maven-wip/job/maven/ > > > > ok, thanks for the info (I could have found myself...) > > > > then +1 to drop this job also > > > > and while at it > > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/ > > > > > > Regards, > > > > Hervé > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Surefire 2.21 release date ?
On 8 February 2018 at 07:00, Hervé BOUTEMY wrote:
> Le jeudi 8 février 2018, 06:45:24 CET Olivier Lamy a écrit :
> > Hi,
> > I'm looking now at having surefire/failsafe working with jdk10 (yup first
> > RC is expected really soon :-)
> > I can't get failsafe working with jdk10 because of a commons-lang3 bug
> (see
> > https://issues.apache.org/jira/browse/SUREFIRE-1473 due to
> > https://issues.apache.org/jira/browse/LANG-1365)
> > So I simply upgraded to commons-lang3 but now it looks enforcer is
> > configured to enforce 1.6.
> > Well as I was thinking: 1.6 really in 2018?
> > So I created SUREFIRE-1474 and push it.
> > Let me know if you have any issues with that?
> no issue with that: if people want old JDK, they need old Maven Surefire
> Plugin
> version, that's quite natural
> Please just add a table in the plugin doc about which is the latest
> Surefire
> version that support which JDK
>
where is the page?
>
> Regards,
>
> Hervé
>
> > As jdk10 is very soon. I'm happy to release surefire ASAP now.
> >
> > WDYT?
> >
> > Cheers
> > Olivier
> >
> > On 4 February 2018 at 19:11, Enrico Olivelli
> wrote:
> > > Il dom 4 feb 2018, 19:38 Tibor Digana ha
> scritto:
> > > > Hi Enrico,
> > > >
> > > > I have got working build script and got some issues on integration
> tests
> > >
> > > in
> > >
> > > > TestNG & Java 10.
> > > > See this CLI. I think the JaCoCo Agent property is the issue because
> it
> > >
> > > is
> > >
> > > > not resolved. I will try to put an empty string in there. Maybe the
> > > > build
> > > > would pass.
> > >
> > > Thank you Tibor for the update. Unfortunately I don't have a Windows
> box
> > > to
> > > reproduce the issue.
> > >
> > > From the error I guess you are right
> > >
> > > Enrico
> > >
> > > > [windows-jdk10-maven3.5.x] [ERROR] Command was cmd.exe /X /C
> > > > "F:\jenkins\tools\java\jdk10-ea+37\bin\java ${jacoco.agent} -jar
> > > >
> > > > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698\
> > >
> > > surefirebooter6458194328264691762.jar
> > >
> > > > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698
> > > > 2018-02-04T17-23-23_801-jvmRun1 surefire15708374661287747855tmp
> > > > surefire_015474024382399849038tmp"
> > > >
> > > >
> > > >
> > > > On Fri, Feb 2, 2018 at 12:23 AM, Tibor Digana <
> tibordig...@apache.org>
> > > >
> > > > wrote:
> > > > > It's ok, not annoying.
> > > > > The issue SUREFIRE-1374 is quite easy to workaround and therefore
> I am
> > > > > working on more difficult issue - the build process.
> > > > > So regarding build process I contacted our INFRA team and found the
> > > > > problem. Now the build is running in [1] and the build script is in
> > >
> > > [2].
> > >
> > > > I
> > > >
> > > > > should get this working first. We are testing JDK 7, 8, 9, 10 on
> Linux
> > > >
> > > > and
> > > >
> > > > > Windows and Maven 3.2 - 3.5.
> > > > >
> > > > > [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-> >
> > > surefire-pipeline/job/SUREFIRE-1463/
> > > > > [2]: https://github.com/apache/maven-surefire/blob/SUREFIRE-> > >
> > 1463/Jenkinsfile
> > > > >
> > > > >
> > > > > On Thu, Feb 1, 2018 at 1:55 PM, Enrico Olivelli <
> eolive...@gmail.com>
> > > > >
> > > > > wrote:
> > > > >> Sorry, I don't want to annoy.
> > > > >> I see that SUREFIRE-1374 needs feedback from users.
> > > > >> I took a look but I don't know how to move forward that issue
> > > > >>
> > > > >> Is it a blocker for 2.21 release ? o can it be post-poned to 2.2 ?
> > > > >>
> > > > >> 2.21 is a great milestone to move people to Java 9
> > > > >>
> > > > >> -- Enrico
> > > > >>
> > > > >> 2018-01-23 17:49 GMT+01:00 Enrico Olivelli :
> > > > >> > 2018-01-16 21:26 GMT+01:00 Enrico Olivelli >:
> > > > >> >> Il gio 11 gen 2018, 22:26 Tibor Digana
> ha
> > > > >> >>
> > > > >> >> scritto:
> > > > >> >>> I was busy at work but now I am free.
> > > > >> >>> I need to have a help with investigating a bug
> > > > >> >>> https://issues.apache.org/jira/browse/SUREFIRE-1450
> > > > >>
> > > > >> >>> I should fix branches which are already in progress:
> > > > >> UnicodeTestNamesIT
> > > > >>
> > > > >> >>> and
> > > > >> >>> JaCoCO (SUREFIRE-1455).
> > > > >> >
> > > > >> > Tibor
> > > > >> >
> > > > >> > I see that now SUREFIRE-1455 (JaCoCo) is closed
> > > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1455
> > > > >> >
> > > > >> > And I see that SUREFIRE-1461 about UnicodeTestNamesIT is closed
> too
> > > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1461
> > > > >> >
> > > > >> >
> > > > >> > It seems that for 2.21 there is only one task open
> > > > >> >
> > > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1374?jql=
> > > > >> > project%20%3D%20SUREFIRE%20AND%20status%20in%20(Open%
> > > > >> > 2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%
> > > > >>
> > > > >> 20%3D%202.21.0.
> > > > >>
> > > > >> > Jigsaw
> > > > >> >
> > > > >> > Do you need some help ?
> > > > >> > I am looking forward a release of
seconder on other fixes for Maven 3.5.3
Hi, Here is a new list of fixes I'd like to merge: - update parent pom to version 31 https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/upgrade_parent_pom/ - MNG-6255 Maven script cannot parse jvm.config with CRLF https://issues.apache.org/jira/browse/MNG-6255 https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6255/ - Jansi 1.17 upgrade, which fixes 3 Jira issues on encoding & MingW/GitBash https://issues.apache.org/jira/browse/MNG-6320 https://issues.apache.org/jira/browse/MNG-6282 https://issues.apache.org/jira/browse/MNG-6218 https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6320_jansi-1.17/ - Mockito upgrade https://issues.apache.org/jira/browse/MNG-6335 https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/job/maven/job/MNG-6335_Mockito_upgrade/ Regards, Hervé - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Old Style Build Jobs
ok, I did the cleanup Tibor, I think there is cleanup to do on Surefire jobs: don't hesitate to do it I don't know for Wagon jobs The cleanup I didn't do is the cleanup on maven-master-release-* https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ I just disabled the jobs: if nobody objects, I'll delete the jobs and even the view in 1 week Regards, Hervé Le mercredi 24 janvier 2018, 07:41:32 CET Hervé BOUTEMY a écrit : > Le mardi 23 janvier 2018, 20:57:42 CET Karl Heinz Marbaise a écrit : > > >> 3. > > >> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-test > > >> in > > >> g-m aven-3-embedded/ > > > > > > I'd like to keep this one, since it's a reference in embedded mode > > > (faster > > > execution) > > > > Our default Job for Maven Core [1] is running with embedded mode.. > > > > > > [1]: https://builds.apache.org/job/maven-wip/job/maven/ > > ok, thanks for the info (I could have found myself...) > > then +1 to drop this job also > > and while at it > https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/ > > > Regards, > > Hervé > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Surefire 2.21 release date ?
I assume that library still uses an enum, which means an upgrade will be
required with every new Java release.
I'd prefer to switch to Plexus Java, which won't have such issue.
I can re-implement that now or after a release of surefire.
Robert
On Thu, 08 Feb 2018 17:15:53 +0100, Gary Gregory
wrote:
On Wed, Feb 7, 2018 at 10:45 PM, Olivier Lamy wrote:
Hi,
I'm looking now at having surefire/failsafe working with jdk10 (yup
first
RC is expected really soon :-)
I can't get failsafe working with jdk10 because of a commons-lang3 bug
(see
https://issues.apache.org/jira/browse/SUREFIRE-1473 due to
https://issues.apache.org/jira/browse/LANG-1365)
So I simply upgraded to commons-lang3 but now it looks enforcer is
configured to enforce 1.6.
Well as I was thinking: 1.6 really in 2018?
So I created SUREFIRE-1474 and push it.
Let me know if you have any issues with that?
As jdk10 is very soon. I'm happy to release surefire ASAP now.
WDYT?
Everytime I want to build with Java 10, I run into this problem. I am +1
(non-binding) for making Java 7 the minimum and updating to the latest
Apache Commons Lang.
Gary
Cheers
Olivier
On 4 February 2018 at 19:11, Enrico Olivelli
wrote:
> Il dom 4 feb 2018, 19:38 Tibor Digana ha
scritto:
>
> > Hi Enrico,
> >
> > I have got working build script and got some issues on integration
tests
> in
> > TestNG & Java 10.
> > See this CLI. I think the JaCoCo Agent property is the issue
because it
> is
> > not resolved. I will try to put an empty string in there. Maybe the
build
> > would pass.
> >
>
>
> Thank you Tibor for the update. Unfortunately I don't have a Windows
box
to
> reproduce the issue.
>
> From the error I guess you are right
>
> Enrico
>
> >
> > [windows-jdk10-maven3.5.x] [ERROR] Command was cmd.exe /X /C
> > "F:\jenkins\tools\java\jdk10-ea+37\bin\java ${jacoco.agent} -jar
> >
> > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698\
> surefirebooter6458194328264691762.jar
> > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698
> > 2018-02-04T17-23-23_801-jvmRun1 surefire15708374661287747855tmp
> > surefire_015474024382399849038tmp"
> >
> >
> >
> > On Fri, Feb 2, 2018 at 12:23 AM, Tibor Digana
> > wrote:
> >
> > > It's ok, not annoying.
> > > The issue SUREFIRE-1374 is quite easy to workaround and therefore
I
am
> > > working on more difficult issue - the build process.
> > > So regarding build process I contacted our INFRA team and found
the
> > > problem. Now the build is running in [1] and the build script is
in
> [2].
> > I
> > > should get this working first. We are testing JDK 7, 8, 9, 10 on
Linux
> > and
> > > Windows and Maven 3.2 - 3.5.
> > >
> > > [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-
> > > surefire-pipeline/job/SUREFIRE-1463/
> > > [2]: https://github.com/apache/maven-surefire/blob/SUREFIRE-
> > > 1463/Jenkinsfile
> > >
> > >
> > > On Thu, Feb 1, 2018 at 1:55 PM, Enrico Olivelli
>
> > > wrote:
> > >
> > >> Sorry, I don't want to annoy.
> > >> I see that SUREFIRE-1374 needs feedback from users.
> > >> I took a look but I don't know how to move forward that issue
> > >>
> > >> Is it a blocker for 2.21 release ? o can it be post-poned to 2.2
?
> > >>
> > >> 2.21 is a great milestone to move people to Java 9
> > >>
> > >> -- Enrico
> > >>
> > >>
> > >> 2018-01-23 17:49 GMT+01:00 Enrico Olivelli :
> > >>
> > >> >
> > >> >
> > >> > 2018-01-16 21:26 GMT+01:00 Enrico Olivelli
:
> > >> >
> > >> >>
> > >> >>
> > >> >> Il gio 11 gen 2018, 22:26 Tibor Digana
ha
> > >> >> scritto:
> > >> >>
> > >> >>> I was busy at work but now I am free.
> > >> >>> I need to have a help with investigating a bug
> > >> >>> https://issues.apache.org/jira/browse/SUREFIRE-1450
> > >> >>> I should fix branches which are already in progress:
> > >> UnicodeTestNamesIT
> > >> >>> and
> > >> >>> JaCoCO (SUREFIRE-1455).
> > >> >>>
> > >> >>
> > >> > Tibor
> > >> >
> > >> > I see that now SUREFIRE-1455 (JaCoCo) is closed
> > >> > https://issues.apache.org/jira/browse/SUREFIRE-1455
> > >> >
> > >> > And I see that SUREFIRE-1461 about UnicodeTestNamesIT is closed
too
> > >> > https://issues.apache.org/jira/browse/SUREFIRE-1461
> > >> >
> > >> >
> > >> > It seems that for 2.21 there is only one task open
> > >> >
> > >> > https://issues.apache.org/jira/browse/SUREFIRE-1374?jql=
> > >> > project%20%3D%20SUREFIRE%20AND%20status%20in%20(Open%
> > >> > 2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%
> > >> 20%3D%202.21.0.
> > >> > Jigsaw
> > >> >
> > >> > Do you need some help ?
> > >> > I am looking forward a release of 2.21
> > >> >
> > >> > Thank you
> > >> > Enrico
> > >> >
> > >> >
> > >> >>
> > >> >> I can pick one on these, just tell me which is the best
> > >> >>
> > >> >> Then all ITs setup with JDK 9.
> > >> >>>
> > >> >>> On Wed, Jan 10, 2018 at 11:17 AM, Enrico Olivelli <
> > >> eolive...@gmail.com>
> > >> >>> wrote:
> > >> >>>
> > >> >>> > (resending)
> > >> >>> >
> > >> >
Re: Surefire 2.21 release date ?
On Wed, Feb 7, 2018 at 10:45 PM, Olivier Lamy wrote:
> Hi,
> I'm looking now at having surefire/failsafe working with jdk10 (yup first
> RC is expected really soon :-)
> I can't get failsafe working with jdk10 because of a commons-lang3 bug (see
> https://issues.apache.org/jira/browse/SUREFIRE-1473 due to
> https://issues.apache.org/jira/browse/LANG-1365)
> So I simply upgraded to commons-lang3 but now it looks enforcer is
> configured to enforce 1.6.
> Well as I was thinking: 1.6 really in 2018?
> So I created SUREFIRE-1474 and push it.
> Let me know if you have any issues with that?
> As jdk10 is very soon. I'm happy to release surefire ASAP now.
>
> WDYT?
>
Everytime I want to build with Java 10, I run into this problem. I am +1
(non-binding) for making Java 7 the minimum and updating to the latest
Apache Commons Lang.
Gary
>
> Cheers
> Olivier
>
>
>
>
>
> On 4 February 2018 at 19:11, Enrico Olivelli wrote:
>
> > Il dom 4 feb 2018, 19:38 Tibor Digana ha
> scritto:
> >
> > > Hi Enrico,
> > >
> > > I have got working build script and got some issues on integration
> tests
> > in
> > > TestNG & Java 10.
> > > See this CLI. I think the JaCoCo Agent property is the issue because it
> > is
> > > not resolved. I will try to put an empty string in there. Maybe the
> build
> > > would pass.
> > >
> >
> >
> > Thank you Tibor for the update. Unfortunately I don't have a Windows box
> to
> > reproduce the issue.
> >
> > From the error I guess you are right
> >
> > Enrico
> >
> > >
> > > [windows-jdk10-maven3.5.x] [ERROR] Command was cmd.exe /X /C
> > > "F:\jenkins\tools\java\jdk10-ea+37\bin\java ${jacoco.agent} -jar
> > >
> > > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698\
> > surefirebooter6458194328264691762.jar
> > > C:\Users\jenkins\AppData\Local\Temp\1\surefire3375403847264435698
> > > 2018-02-04T17-23-23_801-jvmRun1 surefire15708374661287747855tmp
> > > surefire_015474024382399849038tmp"
> > >
> > >
> > >
> > > On Fri, Feb 2, 2018 at 12:23 AM, Tibor Digana
> > > wrote:
> > >
> > > > It's ok, not annoying.
> > > > The issue SUREFIRE-1374 is quite easy to workaround and therefore I
> am
> > > > working on more difficult issue - the build process.
> > > > So regarding build process I contacted our INFRA team and found the
> > > > problem. Now the build is running in [1] and the build script is in
> > [2].
> > > I
> > > > should get this working first. We are testing JDK 7, 8, 9, 10 on
> Linux
> > > and
> > > > Windows and Maven 3.2 - 3.5.
> > > >
> > > > [1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-
> > > > surefire-pipeline/job/SUREFIRE-1463/
> > > > [2]: https://github.com/apache/maven-surefire/blob/SUREFIRE-
> > > > 1463/Jenkinsfile
> > > >
> > > >
> > > > On Thu, Feb 1, 2018 at 1:55 PM, Enrico Olivelli >
> > > > wrote:
> > > >
> > > >> Sorry, I don't want to annoy.
> > > >> I see that SUREFIRE-1374 needs feedback from users.
> > > >> I took a look but I don't know how to move forward that issue
> > > >>
> > > >> Is it a blocker for 2.21 release ? o can it be post-poned to 2.2 ?
> > > >>
> > > >> 2.21 is a great milestone to move people to Java 9
> > > >>
> > > >> -- Enrico
> > > >>
> > > >>
> > > >> 2018-01-23 17:49 GMT+01:00 Enrico Olivelli :
> > > >>
> > > >> >
> > > >> >
> > > >> > 2018-01-16 21:26 GMT+01:00 Enrico Olivelli :
> > > >> >
> > > >> >>
> > > >> >>
> > > >> >> Il gio 11 gen 2018, 22:26 Tibor Digana
> ha
> > > >> >> scritto:
> > > >> >>
> > > >> >>> I was busy at work but now I am free.
> > > >> >>> I need to have a help with investigating a bug
> > > >> >>> https://issues.apache.org/jira/browse/SUREFIRE-1450
> > > >> >>> I should fix branches which are already in progress:
> > > >> UnicodeTestNamesIT
> > > >> >>> and
> > > >> >>> JaCoCO (SUREFIRE-1455).
> > > >> >>>
> > > >> >>
> > > >> > Tibor
> > > >> >
> > > >> > I see that now SUREFIRE-1455 (JaCoCo) is closed
> > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1455
> > > >> >
> > > >> > And I see that SUREFIRE-1461 about UnicodeTestNamesIT is closed
> too
> > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1461
> > > >> >
> > > >> >
> > > >> > It seems that for 2.21 there is only one task open
> > > >> >
> > > >> > https://issues.apache.org/jira/browse/SUREFIRE-1374?jql=
> > > >> > project%20%3D%20SUREFIRE%20AND%20status%20in%20(Open%
> > > >> > 2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%
> > > >> 20%3D%202.21.0.
> > > >> > Jigsaw
> > > >> >
> > > >> > Do you need some help ?
> > > >> > I am looking forward a release of 2.21
> > > >> >
> > > >> > Thank you
> > > >> > Enrico
> > > >> >
> > > >> >
> > > >> >>
> > > >> >> I can pick one on these, just tell me which is the best
> > > >> >>
> > > >> >> Then all ITs setup with JDK 9.
> > > >> >>>
> > > >> >>> On Wed, Jan 10, 2018 at 11:17 AM, Enrico Olivelli <
> > > >> eolive...@gmail.com>
> > > >> >>> wrote:
> > > >> >>>
> > > >> >>> > (resending)
> > > >> >>> >
> > > >> >>> > Hi Tibor,
> > > >> >>> > Do you have any pl
Re: seconders for Maven 3.5.x
+1000 On Thu 8 Feb 2018 at 03:12, Manfred Moser wrote: > Seconding with > > +2 > > ;-) > > > Olivier Lamy wrote on 2018-02-07 17:18: > > > +1 > > > > On 8 February 2018 at 00:09, Hervé BOUTEMY > wrote: > > > >> Hi, > >> > >> I need seconders for: > >> > >> http://git-wip-us.apache.org/repos/asf/maven/commit/7fed4792 > >> [MNG-5992] Upgrade default version of maven-release-plugin to 2.5.3 > >> avoids exposing Git password during release > >> https://issues.apache.org/jira/browse/MNG-5992 > >> > >> Anybody? > >> > >> Regards, > >> > >> Hervé > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > > > > -- > > Olivier Lamy > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sent from my phone
