Re: is 3.5.1 open for business?

Will do. Thank you. -- Regards, Igor On April 13, 2017 3:55:43 PM Stephen Connolly wrote: Just be sure to delete the branch after merging so that the job will get cleaned up (in 3 days time - retention strategy) On Thu 13 Apr 2017 at 23:53, Stephen

Re: is 3.5.1 open for business?

Just be sure to delete the branch after merging so that the job will get cleaned up (in 3 days time - retention strategy) On Thu 13 Apr 2017 at 23:53, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > None here! > > On Thu 13 Apr 2017 at 23:30, Igor Fedorenko

Re: is 3.5.1 open for business?

None here! On Thu 13 Apr 2017 at 23:30, Igor Fedorenko wrote: > Thank you for the explanation, didn't find this job. > > Now that both branch builds are happy, any objections I merge then to > master? > > -- > Regards, > Igor > > > > On April 13, 2017 1:20:24 PM Karl Heinz

Re: is 3.5.1 open for business?

Thank you for the explanation, didn't find this job. Now that both branch builds are happy, any objections I merge then to master? -- Regards, Igor On April 13, 2017 1:20:24 PM Karl Heinz Marbaise wrote: Hi Igor, On 13/04/17 22:09, Igor Fedorenko wrote: I pushed my

Re: is 3.5.1 open for business?

Hi Igor, On 13/04/17 22:09, Igor Fedorenko wrote: I pushed my changes to feature branches. How do I trigger CI builds now? They are already running your builds... Take a look here: https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-jenkinsfile/ Kind regards Karl Heinz Marbaise

Re: is 3.5.1 open for business?

Are your branch jobs here: https://builds.apache.org/job/maven-3.x-jenkinsfile/ On Thu 13 Apr 2017 at 21:17, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Should trigger automatically > > On Thu 13 Apr 2017 at 21:09, Igor Fedorenko wrote: > >> I pushed my

Re: is 3.5.1 open for business?

Should trigger automatically On Thu 13 Apr 2017 at 21:09, Igor Fedorenko wrote: > I pushed my changes to feature branches. How do I trigger CI builds now? > > -- > Regards, > Igor > > > > On April 7, 2017 9:24:06 AM Igor Fedorenko wrote: > > > I

Re: is 3.5.1 open for business?

I pushed my changes to feature branches. How do I trigger CI builds now? -- Regards, Igor On April 7, 2017 9:24:06 AM Igor Fedorenko wrote: I completely agree we need to prove each code change does not break existing integration tests (and I did run the tests locally

[GitHub] maven-surefire issue #110: SUREFIRE-1216: TEST-*.xml files generated by Sure...

Github user jonenst commented on the issue: https://github.com/apache/maven-surefire/pull/110 Thanks for the hard work, congratz on the 2.20 release ! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

Re: Check if parameter is explicitly set

Hey, Sure, let me give you more context. The parameter has a default value that users can override. But if they don't set it and another condition is true (some file exists in the project), then we want to use a different value, a different default. Maybe the best is to remove the default value,

Re: Building a Java9 project just using JDK9

> > >> I don't see any activity either, so my idea is to replace XStream, see > MWAR-397[1] > Just for the record, Jörg is working through the Java9 issues for XStream presently - https://github.com/x-stream/xstream/commits/master - Paul

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

Is it you want the profiles activated during the release:perform fork? If that is the case you need to modify the "arguments" parameter of the release goal. Depending on how your pom is set up this could be as simple as "-Darguments=-P+viennacl -P+..." or you may have to modify the pom (though

Re: Check if parameter is explicitly set

Hi, On 13/04/17 02:05, András Kerekes wrote: Hi, I'm working on a Maven plugin and I'd like to check whether a parameter for a Mojo has been explicitly set by the user (via POM), or it contains the default value. Is there a way to do this? Maybe I misunderstand a thing but why do you need to