Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

On Thu 10 May 2018 at 23:51, Hervé BOUTEMY wrote: > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > > ob/master/1/console looks good. @Hervé can you delete > >

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

On Thu 10 May 2018 at 23:51, Hervé BOUTEMY wrote: > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > > ob/master/1/console looks good. @Hervé can you delete > >

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > ob/master/1/console looks good. @Hervé can you delete > https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are > happy with it? great

Re: [VOTE] Release Apache Maven EAR Plugin version 3.0.1

Hi, +1 from me... Kind regards Karl Heinz Marbaise On 09/05/18 20:05, Karl Heinz Marbaise wrote: Hi, We solved 3 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12342882 There are still a couple of issues left in JIRA:

Re: JDK 11 Early Access build 12 available

On 09.05.2018 23:35, Tibor Digana wrote: > I still do not have the answer regarding language features. Apologies for that - your email about language features didn't contain any question marks, so it seemed to be just a statement of your opinions. Since opinions are not questions, I didn't

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.1

+1 On Wed, 09 May 2018 20:17:24 +0200, Karl Heinz Marbaise wrote: Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12341729 There are still a couple of issues left in JIRA:

Re: [VOTE] Release Apache Maven WAR Plugin version 3.2.1

I've marked MWAR-303 for 3.2.2 to reduce the chance of forgetting it. Robert On Thu, 10 May 2018 03:21:41 +0200, Gabriel Belingueres wrote: any chance of adding MWAR-303 to the release? fix is already submitted. El mié., 9 de may. de 2018 20:14, Olivier Lamy

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

Ahh no, https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-site/ is about publishing the maven core test results... we should see about folding that into the core Jenkinsfile with a condition on being master branch only On 10 May 2018 at 09:55, Stephen Connolly

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-site/ seems like a dead job too On 10 May 2018 at 09:52, Stephen Connolly wrote: > https://builds.apache.org/view/M-R/view/Maven/job/maven- > box/job/maven-site/job/master/1/console looks good. @Hervé

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/job/master/1/console looks good. @Hervé can you delete https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are happy with it? On 10 May 2018 at 09:37, Stephen Connolly

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

On 10 May 2018 at 07:25, Hervé BOUTEMY wrote: > Le mercredi 9 mai 2018, 19:40:54 CEST Karl Heinz Marbaise a écrit : > > Hi, > > > > > > This means if you do a commit in the gitbox repository[1] the job[2] on > > our build server will start and deploy directly to production

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

Le mercredi 9 mai 2018, 19:40:54 CEST Karl Heinz Marbaise a écrit : > Hi, > > > This means if you do a commit in the gitbox repository[1] the job[2] on > our build server will start and deploy directly to production site[3] > without the need to public via cms[4]. yes, you get it > > > Great