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

2018-05-10 Thread Stephen Connolly 
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
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are
> > happy with it?
> great job, even with multi-branch: I'll copy the Jenkinsfile to Doxia site
>
> How can we consult the local site build result? I don't see on master:
> would
> something appear in a branch?


Ok I am having a hard time parsing that request. Could you try to rephrase?


>
>
> >
> > On 10 May 2018 at 09:37, Stephen Connolly <
> stephen.alan.conno...@gmail.com>
> >
> > wrote:
> > > 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
> site[3]
> > >> > without the need to public via cms[4].
> > >>
> > >> yes, you get it
> > >>
> > >> > Great work...
> > >>
> > >> thank you
> > >>
> > >> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile
> to
> > >> > make a mvn site-deploy ?
> > >>
> > >> currently, the Jenkins job that builds and deploy the website is
> manually
> > >> configured
> > >> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins
> job
> > >> could
> > >> be replaced by the equivalent maven-box generated one
> > >> https://builds.apache.org/job/maven-box/
> > >>
> > >> My personal knowledge of Jenkinsfile and how to test it before
> committing
> > >> is
> > >> null, then we're staying for the moment with the handcrafted job
> > >>
> > >> Initially, I thought that only the Jenkinsfile would bring us the
> > >> immediate
> > >> rebuild on Git commit: but it seems the Git pubsub feature is
> available
> > >> also
> > >> on handcrafted job.
> > >
> > > Tsk Tsk did you think that little of me that I would implement pub-sub
> for
> > > multibranch and leave regular in the cold just to try and drive
> > > multibranch
> > > adoption :-(
> I don't know Jenkins sufficiently to know if Git pubsub is really a
> separate
> feature from Apache Hosted Git plugin: glad to see it works for any type
> of
> job
>
>
> > >
> > >> Then the only benefit we'll have is to remove the handmade
> > >> job: nice to have, but nothing critical...
> > >>
> > >> Regards,
> > >>
> > >> Hervé
> > >>
> > >> > Kind regards
> > >> > Karl Heinz Marbaise
> > >> >
> > >> >
> > >> >
> > >> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
> > >> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
> > >> > [3]: https://maven.apache.org/
> > >> > [4]: https://cms.apache.org/maven/
> > >> >
> > >> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
> > >> > > sites sources migration to Git at GitBox done: now you can edit
> Maven
> > >>
> > >> and
> > >>
> > >> > > Doxia sites directly from GitHub through the edit link
> > >>
> > >> > > The site build and publish Jenkins jobs are still the previous
> ones:
> > >> if
> > >>
> > >> > > someone creates a Jenkinsfile, we'll have immediate build in
> > >> > > maven-box
> > >> > > job.
> > >> > >
> > >> > > Next step will be the move of components svnpubsub location from
> > >> > > infra
> > >> > > location [1] to ASF [2] this will require a change in
> > >> > > distributionManagement/site/url in a new parent POM and every
> child
> > >>
> > >> POMs:
> > >> > > if you intend to do a release, please tell and we'll check what
> to do
> > >> > >
> > >> > > Regards,
> > >> > >
> > >> > > Hervé
> > >> > >
> > >> > > [1]
> > >> > > https://svn.apache.org/repos/infra/websites/production/maven
> > >>
> > >> /components/
> > >>
> > >> > > +
> > >> > > https://svn.apache.org/repos/infra/websites/production/maven
> > >>
> > >> -doxia/compon
> > >>
> > >> > > ents/
> > >> > >
> > >> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
> > >> > > +
> https://svn.apache.org/repos/asf/maven/doxia/website/components/
> > >> > >
> > >> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
> > >> > >> Jira issue for source migration to Git opened:
> > >> > >> https://issues.apache.org/jira/browse/INFRA-16361
> > >> > >>
> > >> > >> Regards,
> > >> > >>
> > >> > >> Hervé
> > >> > >>
> > >> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
> > >> > >>> here it is, now Maven site and Doxia sub-site are published by
> > >>
> > >> Jenkins
> > >>
> > >> > >>> CMS is not used any more
> > >> > >>> We'll just need to move components reference documentation out
> of
> > >>
> > >> the
> > >>
> > >> > >>> CMS
> > >> > >>> svn space: I'll do it later with infra
> > >> > >>>
> > >> > >>> now, I'll work on GitBox migration
> > >> > >>>
> > >> > >>> If someone can write a Jenkinsfile, this

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

2018-05-10 Thread Stephen Connolly 
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
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are
> > happy with it?
> great job, even with multi-branch: I'll copy the Jenkinsfile to Doxia site
>
> How can we consult the local site build result? I don't see on master:
> would
> something appear in a branch?
>
>
> >
> > On 10 May 2018 at 09:37, Stephen Connolly <
> stephen.alan.conno...@gmail.com>
> >
> > wrote:
> > > 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
> site[3]
> > >> > without the need to public via cms[4].
> > >>
> > >> yes, you get it
> > >>
> > >> > Great work...
> > >>
> > >> thank you
> > >>
> > >> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile
> to
> > >> > make a mvn site-deploy ?
> > >>
> > >> currently, the Jenkins job that builds and deploy the website is
> manually
> > >> configured
> > >> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins
> job
> > >> could
> > >> be replaced by the equivalent maven-box generated one
> > >> https://builds.apache.org/job/maven-box/
> > >>
> > >> My personal knowledge of Jenkinsfile and how to test it before
> committing
> > >> is
> > >> null, then we're staying for the moment with the handcrafted job
> > >>
> > >> Initially, I thought that only the Jenkinsfile would bring us the
> > >> immediate
> > >> rebuild on Git commit: but it seems the Git pubsub feature is
> available
> > >> also
> > >> on handcrafted job.
> > >
> > > Tsk Tsk did you think that little of me that I would implement pub-sub
> for
> > > multibranch and leave regular in the cold just to try and drive
> > > multibranch
> > > adoption :-(
> I don't know Jenkins sufficiently to know if Git pubsub is really a
> separate
> feature from Apache Hosted Git plugin: glad to see it works for any type
> of
> job


So the SCM API in Jenkins (which I wrote) has a code path that lets you
write a single event marcher to target old style and multibranch projects
at the same time... so in effect implementing the gitpubsub stuff gave me
old style support “for free”

(Of course I paid for that support when I wrote scm api... but incremental
cost is lower)

>
>
>
> > >
> > >> Then the only benefit we'll have is to remove the handmade
> > >> job: nice to have, but nothing critical...
> > >>
> > >> Regards,
> > >>
> > >> Hervé
> > >>
> > >> > Kind regards
> > >> > Karl Heinz Marbaise
> > >> >
> > >> >
> > >> >
> > >> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
> > >> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
> > >> > [3]: https://maven.apache.org/
> > >> > [4]: https://cms.apache.org/maven/
> > >> >
> > >> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
> > >> > > sites sources migration to Git at GitBox done: now you can edit
> Maven
> > >>
> > >> and
> > >>
> > >> > > Doxia sites directly from GitHub through the edit link
> > >>
> > >> > > The site build and publish Jenkins jobs are still the previous
> ones:
> > >> if
> > >>
> > >> > > someone creates a Jenkinsfile, we'll have immediate build in
> > >> > > maven-box
> > >> > > job.
> > >> > >
> > >> > > Next step will be the move of components svnpubsub location from
> > >> > > infra
> > >> > > location [1] to ASF [2] this will require a change in
> > >> > > distributionManagement/site/url in a new parent POM and every
> child
> > >>
> > >> POMs:
> > >> > > if you intend to do a release, please tell and we'll check what
> to do
> > >> > >
> > >> > > Regards,
> > >> > >
> > >> > > Hervé
> > >> > >
> > >> > > [1]
> > >> > > https://svn.apache.org/repos/infra/websites/production/maven
> > >>
> > >> /components/
> > >>
> > >> > > +
> > >> > > https://svn.apache.org/repos/infra/websites/production/maven
> > >>
> > >> -doxia/compon
> > >>
> > >> > > ents/
> > >> > >
> > >> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
> > >> > > +
> https://svn.apache.org/repos/asf/maven/doxia/website/components/
> > >> > >
> > >> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
> > >> > >> Jira issue for source migration to Git opened:
> > >> > >> https://issues.apache.org/jira/browse/INFRA-16361
> > >> > >>
> > >> > >> Regards,
> > >> > >>
> > >> > >> Hervé
> > >> > >>
> > >> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
> > >> > >>> here it is, now Maven site and Doxia sub-site are published by
> > >>
> > >> Jenkins
> > >>
> > >> > >>> CMS is not used any more
> > >> > >>> We'll just need to move

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

2018-05-10 Thread Hervé BOUTEMY 
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 job, even with multi-branch: I'll copy the Jenkinsfile to Doxia site

How can we consult the local site build result? I don't see on master: would 
something appear in a branch?


> 
> On 10 May 2018 at 09:37, Stephen Connolly 
> 
> wrote:
> > 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 site[3]
> >> > without the need to public via cms[4].
> >> 
> >> yes, you get it
> >> 
> >> > Great work...
> >> 
> >> thank you
> >> 
> >> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
> >> > make a mvn site-deploy ?
> >> 
> >> currently, the Jenkins job that builds and deploy the website is manually
> >> configured
> >> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job
> >> could
> >> be replaced by the equivalent maven-box generated one
> >> https://builds.apache.org/job/maven-box/
> >> 
> >> My personal knowledge of Jenkinsfile and how to test it before committing
> >> is
> >> null, then we're staying for the moment with the handcrafted job
> >> 
> >> Initially, I thought that only the Jenkinsfile would bring us the
> >> immediate
> >> rebuild on Git commit: but it seems the Git pubsub feature is available
> >> also
> >> on handcrafted job.
> > 
> > Tsk Tsk did you think that little of me that I would implement pub-sub for
> > multibranch and leave regular in the cold just to try and drive
> > multibranch
> > adoption :-(
I don't know Jenkins sufficiently to know if Git pubsub is really a separate 
feature from Apache Hosted Git plugin: glad to see it works for any type of 
job


> > 
> >> Then the only benefit we'll have is to remove the handmade
> >> job: nice to have, but nothing critical...
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> > Kind regards
> >> > Karl Heinz Marbaise
> >> > 
> >> > 
> >> > 
> >> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
> >> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
> >> > [3]: https://maven.apache.org/
> >> > [4]: https://cms.apache.org/maven/
> >> > 
> >> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
> >> > > sites sources migration to Git at GitBox done: now you can edit Maven
> >> 
> >> and
> >> 
> >> > > Doxia sites directly from GitHub through the edit link
> >> 
> >> > > The site build and publish Jenkins jobs are still the previous ones:
> >> if
> >> 
> >> > > someone creates a Jenkinsfile, we'll have immediate build in
> >> > > maven-box
> >> > > job.
> >> > > 
> >> > > Next step will be the move of components svnpubsub location from
> >> > > infra
> >> > > location [1] to ASF [2] this will require a change in
> >> > > distributionManagement/site/url in a new parent POM and every child
> >> 
> >> POMs:
> >> > > if you intend to do a release, please tell and we'll check what to do
> >> > > 
> >> > > Regards,
> >> > > 
> >> > > Hervé
> >> > > 
> >> > > [1]
> >> > > https://svn.apache.org/repos/infra/websites/production/maven
> >> 
> >> /components/
> >> 
> >> > > +
> >> > > https://svn.apache.org/repos/infra/websites/production/maven
> >> 
> >> -doxia/compon
> >> 
> >> > > ents/
> >> > > 
> >> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
> >> > > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
> >> > > 
> >> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
> >> > >> Jira issue for source migration to Git opened:
> >> > >> https://issues.apache.org/jira/browse/INFRA-16361
> >> > >> 
> >> > >> Regards,
> >> > >> 
> >> > >> Hervé
> >> > >> 
> >> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
> >> > >>> here it is, now Maven site and Doxia sub-site are published by
> >> 
> >> Jenkins
> >> 
> >> > >>> CMS is not used any more
> >> > >>> We'll just need to move components reference documentation out of
> >> 
> >> the
> >> 
> >> > >>> CMS
> >> > >>> svn space: I'll do it later with infra
> >> > >>> 
> >> > >>> now, I'll work on GitBox migration
> >> > >>> 
> >> > >>> If someone can write a Jenkinsfile, this would be great: the job
> >> 
> >> has to
> >> 
> >> > >>> be
> >> > >>> tied to websites1 node, and the command is simply "mvn site-deploy"
> >> > >>> 
> >> > >>> Regards,
> >> > >>> 
> >> > >>> Hervé
> >> > >>> 
> >> > >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
> >> >  FYI, switch is happening currently, I'm on HipChat with infra
> >> >  
> >> >  then CMS does not have any effect now:

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

2018-05-10 Thread Karl Heinz Marbaise 

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:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MEAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC 



Staging repo:
https://repository.apache.org/content/repositories/maven-1422/

https://repository.apache.org/content/repositories/maven-1422/org/apache/maven/plugins/maven-ear-plugin/3.0.1/maven-ear-plugin-3.0.1-source-release.zip 



Source release checksum(s):
maven-ear-plugin-3.0.1-source-release.zip sha1: 
e6fadc6916a2ece64fbc73e0c03086b96a8773c7


Staging site:
https://maven.apache.org/plugins-archives/maven-ear-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: JDK 11 Early Access build 12 available

2018-05-10 Thread dalibor topic 



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 consider that you 
were looking for a reply.


Why Oracle 
did not implement more language improvements after Java 1.8?


Firstly, there was the introduction of the module system, which was the 
major Java programming language improvement in Java SE 9. Please see 
https://docs.oracle.com/javase/specs/jls/se9/html/jls-7.html#jls-7.7 for 
details.  In addition, Java SE 9 contained some smaller language 
improvements, as described at 
https://docs.oracle.com/javase/9/language/toc.htm#JSLAN-GUID-B06D7006-D9F4-42F8-AD21-BF861747EDCF 
.


Secondly, Java SE 10 introduced local variable type inference, another 
language improvement as described at 
https://docs.oracle.com/javase/10/language/toc.htm#JSLAN-GUID-7D5FDD65-ACE4-4B3C-80F4-CC01CBD211A4 
.


For Java SE 11, it's planned to refine that feature further as discussed 
at http://openjdk.java.net/jeps/323 .


Further ideas for Java programming language improvements are being 
explored in Project Amber (see http://openjdk.java.net/projects/amber/ 
for details) for smaller changes, and Project Valhalla (see 
http://openjdk.java.net/projects/valhalla/ for details) for larger ones, 
like value types.



For instance value objects. Is this in 9, 10 or 11? I could not find it.


Assuming you mean value types, they are not targetted for any release 
yet, as they are still being explored in Project Valhalla.



What about descriptive language and features? Is it possible in Java?


Assuming you mean data classes, as in 
http://cr.openjdk.java.net/~briangoetz/amber/datum.html , they are being 
explored in Project Amber. They are not targetted for any release yet, 
either.


If you're interested in following (or contributing to) the development 
of Project Amber and Project Valhalla, details of the features being 
explores, code, etc. I would suggest subscribing to their mailing lists, 
as linked off the respective web pages above.


cheers,
dalibor topic




On Wed, May 9, 2018 at 8:28 PM, dalibor topic > wrote:




On 08.05.2018 11:36, Tibor Digana wrote:

Is there any JVM which "shrinks" at least shrinks the native
memory consumption so that the Java Heap is cca == Native
Consumption at most of the time?


I hope that the information in

https://docs.oracle.com/javase/10/gctuning/factors-affecting-garbage-collection-performance.htm#JSGCT-GUID-7FB2D1D5-D75F-4AA1-A3B1-4A17F8FF97D0


is helpful in that regard.

cheers,
dalibor topic


-- 
 Dalibor Topic | Principal Product Manager

Phone: +494089091214  | Mobile: +491737185961


ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 H

amburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D
-80992
München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

> Oracle is committed to developing
practices and products that help protect the environment




--
 Dalibor Topic | Principal Product Manager
Phone: +494089091214  | Mobile: +491737185961


ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

 Oracle is committed to developing
practices and products that help protect the environment

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

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

2018-05-10 Thread Robert Scholte 

+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:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MWAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1423/

https://repository.apache.org/content/repositories/maven-1423/org/apache/maven/plugins/maven-war-plugin/3.2.1/maven-war-plugin-3.2.1-source-release.zip

Source release checksum(s):
maven-war-plugin-3.2.1-source-release.zip sha1:  
94317def832e4b767808dbed6b9463c75a99227c


Staging site:
https://maven.apache.org/plugins-archives/maven-war-plugin-LATEST/

Guide to testing staged releases:
https://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for at least 72 hours.

[ ] +1
[ ] +0
[ ] -1


Kind regards
Karl Heinz Marbaise

-
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: [VOTE] Release Apache Maven WAR Plugin version 3.2.1

2018-05-10 Thread Robert Scholte 

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   
escribió:



+1

On Thu, 10 May 2018 at 04:17, 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:
>
>
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MWAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1423/
>
>
>
https://repository.apache.org/content/repositories/maven-1423/org/apache/maven/plugins/maven-war-plugin/3.2.1/maven-war-plugin-3.2.1-source-release.zip
>
> Source release checksum(s):
> maven-war-plugin-3.2.1-source-release.zip sha1:
> 94317def832e4b767808dbed6b9463c75a99227c
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-war-plugin-LATEST/
>
> Guide to testing staged releases:
>  
https://maven.apache.org/guides/development/guide-testing-releases.html

>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> 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

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

2018-05-10 Thread Stephen Connolly 
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 
wrote:

> 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é 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 > om> wrote:
>>
>>>
>>>
>>> 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 site[3]
 > without the need to public via cms[4].
 yes, you get it

 >
 >
 > Great work...
 thank you

 >
 > BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
 > make a mvn site-deploy ?
 currently, the Jenkins job that builds and deploy the website is
 manually
 configured
 If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job
 could
 be replaced by the equivalent maven-box generated one
 https://builds.apache.org/job/maven-box/

 My personal knowledge of Jenkinsfile and how to test it before
 committing is
 null, then we're staying for the moment with the handcrafted job

 Initially, I thought that only the Jenkinsfile would bring us the
 immediate
 rebuild on Git commit: but it seems the Git pubsub feature is available
 also
 on handcrafted job.
>>>
>>>
>>> Tsk Tsk did you think that little of me that I would implement pub-sub
>>> for multibranch and leave regular in the cold just to try and drive
>>> multibranch adoption :-(
>>>
>>>
 Then the only benefit we'll have is to remove the handmade
 job: nice to have, but nothing critical...

 Regards,

 Hervé

 >
 >
 > Kind regards
 > Karl Heinz Marbaise
 >
 >
 >
 > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
 > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
 > [3]: https://maven.apache.org/
 > [4]: https://cms.apache.org/maven/
 >
 > On 30/04/18 22:49, Hervé BOUTEMY wrote:
 > > sites sources migration to Git at GitBox done: now you can edit
 Maven and
 > > Doxia sites directly from GitHub through the edit link
 > >
 > > The site build and publish Jenkins jobs are still the previous
 ones: if
 > > someone creates a Jenkinsfile, we'll have immediate build in
 maven-box
 > > job.
 > >
 > > Next step will be the move of components svnpubsub location from
 infra
 > > location [1] to ASF [2] this will require a change in
 > > distributionManagement/site/url in a new parent POM and every
 child POMs:
 > > if you intend to do a release, please tell and we'll check what to
 do
 > >
 > > Regards,
 > >
 > > Hervé
 > >
 > > [1]
 > > https://svn.apache.org/repos/infra/websites/production/maven
 /components/
 > > +
 > > https://svn.apache.org/repos/infra/websites/production/maven
 -doxia/compon
 > > ents/
 > >
 > > [2] https://svn.apache.org/repos/asf/maven/website/components/
 > > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
 > >
 > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
 > >> Jira issue for source migration to Git opened:
 > >> https://issues.apache.org/jira/browse/INFRA-16361
 > >>
 > >> Regards,
 > >>
 > >> Hervé
 > >>
 > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
 > >>> here it is, now Maven site and Doxia sub-site are published by
 Jenkins
 > >>>
 > >>> CMS is not used any more
 > >>> We'll just need to move components reference documentation out of
 the
 > >>> CMS
 > >>> svn space: I'll do it later with infra
 > >>>
 > >>> now, I'll work on GitBox migration
 > >>>
 > >>> If someone can write a Jenkinsfile, this would be great: the job
 has to
 > >>> be
 > >>> tied to websites1 node, and the command is simply "mvn
 site-deploy"
 > >>>
 > >>> Regards,
 > >>>
 > >>> Hervé
 > >>>
 > >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
 >  FYI, switch is happening currently, I'm on HipChat with infra
 > 
 >

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

2018-05-10 Thread Stephen Connolly 
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é 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  > wrote:
>
>>
>>
>> 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 site[3]
>>> > without the need to public via cms[4].
>>> yes, you get it
>>>
>>> >
>>> >
>>> > Great work...
>>> thank you
>>>
>>> >
>>> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
>>> > make a mvn site-deploy ?
>>> currently, the Jenkins job that builds and deploy the website is
>>> manually
>>> configured
>>> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job
>>> could
>>> be replaced by the equivalent maven-box generated one
>>> https://builds.apache.org/job/maven-box/
>>>
>>> My personal knowledge of Jenkinsfile and how to test it before
>>> committing is
>>> null, then we're staying for the moment with the handcrafted job
>>>
>>> Initially, I thought that only the Jenkinsfile would bring us the
>>> immediate
>>> rebuild on Git commit: but it seems the Git pubsub feature is available
>>> also
>>> on handcrafted job.
>>
>>
>> Tsk Tsk did you think that little of me that I would implement pub-sub
>> for multibranch and leave regular in the cold just to try and drive
>> multibranch adoption :-(
>>
>>
>>> Then the only benefit we'll have is to remove the handmade
>>> job: nice to have, but nothing critical...
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> >
>>> >
>>> > Kind regards
>>> > Karl Heinz Marbaise
>>> >
>>> >
>>> >
>>> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
>>> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
>>> > [3]: https://maven.apache.org/
>>> > [4]: https://cms.apache.org/maven/
>>> >
>>> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
>>> > > sites sources migration to Git at GitBox done: now you can edit
>>> Maven and
>>> > > Doxia sites directly from GitHub through the edit link
>>> > >
>>> > > The site build and publish Jenkins jobs are still the previous ones:
>>> if
>>> > > someone creates a Jenkinsfile, we'll have immediate build in
>>> maven-box
>>> > > job.
>>> > >
>>> > > Next step will be the move of components svnpubsub location from
>>> infra
>>> > > location [1] to ASF [2] this will require a change in
>>> > > distributionManagement/site/url in a new parent POM and every child
>>> POMs:
>>> > > if you intend to do a release, please tell and we'll check what to do
>>> > >
>>> > > Regards,
>>> > >
>>> > > Hervé
>>> > >
>>> > > [1]
>>> > > https://svn.apache.org/repos/infra/websites/production/maven
>>> /components/
>>> > > +
>>> > > https://svn.apache.org/repos/infra/websites/production/maven
>>> -doxia/compon
>>> > > ents/
>>> > >
>>> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
>>> > > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
>>> > >
>>> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
>>> > >> Jira issue for source migration to Git opened:
>>> > >> https://issues.apache.org/jira/browse/INFRA-16361
>>> > >>
>>> > >> Regards,
>>> > >>
>>> > >> Hervé
>>> > >>
>>> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
>>> > >>> here it is, now Maven site and Doxia sub-site are published by
>>> Jenkins
>>> > >>>
>>> > >>> CMS is not used any more
>>> > >>> We'll just need to move components reference documentation out of
>>> the
>>> > >>> CMS
>>> > >>> svn space: I'll do it later with infra
>>> > >>>
>>> > >>> now, I'll work on GitBox migration
>>> > >>>
>>> > >>> If someone can write a Jenkinsfile, this would be great: the job
>>> has to
>>> > >>> be
>>> > >>> tied to websites1 node, and the command is simply "mvn site-deploy"
>>> > >>>
>>> > >>> Regards,
>>> > >>>
>>> > >>> Hervé
>>> > >>>
>>> > >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
>>> >  FYI, switch is happening currently, I'm on HipChat with infra
>>> > 
>>> >  then CMS does not have any effect now: this will be Jenkins job
>>> (or
>>> >  manual
>>> >  build)
>>> > 
>>> >  please don't try to publish anything for now: I'll tell once
>>> everything
>>> >  is
>>> >  stabilized
>>> > 
>>> >  Regards,
>>> > 
>>> >  Hervé
>>> > 
>>> >  Le vendredi 13 avril 2018, 18:15:21 CEST Karl Heinz Marbaise a
>>> écrit :
>>> > > Hi Hervé,
>>> > >
>>> > > On 12/04/18 08:17, Hervé

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

2018-05-10 Thread Stephen Connolly 
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 
wrote:

>
>
> 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 site[3]
>> > without the need to public via cms[4].
>> yes, you get it
>>
>> >
>> >
>> > Great work...
>> thank you
>>
>> >
>> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
>> > make a mvn site-deploy ?
>> currently, the Jenkins job that builds and deploy the website is manually
>> configured
>> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job
>> could
>> be replaced by the equivalent maven-box generated one
>> https://builds.apache.org/job/maven-box/
>>
>> My personal knowledge of Jenkinsfile and how to test it before committing
>> is
>> null, then we're staying for the moment with the handcrafted job
>>
>> Initially, I thought that only the Jenkinsfile would bring us the
>> immediate
>> rebuild on Git commit: but it seems the Git pubsub feature is available
>> also
>> on handcrafted job.
>
>
> Tsk Tsk did you think that little of me that I would implement pub-sub for
> multibranch and leave regular in the cold just to try and drive multibranch
> adoption :-(
>
>
>> Then the only benefit we'll have is to remove the handmade
>> job: nice to have, but nothing critical...
>>
>> Regards,
>>
>> Hervé
>>
>> >
>> >
>> > Kind regards
>> > Karl Heinz Marbaise
>> >
>> >
>> >
>> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
>> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
>> > [3]: https://maven.apache.org/
>> > [4]: https://cms.apache.org/maven/
>> >
>> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
>> > > sites sources migration to Git at GitBox done: now you can edit Maven
>> and
>> > > Doxia sites directly from GitHub through the edit link
>> > >
>> > > The site build and publish Jenkins jobs are still the previous ones:
>> if
>> > > someone creates a Jenkinsfile, we'll have immediate build in maven-box
>> > > job.
>> > >
>> > > Next step will be the move of components svnpubsub location from infra
>> > > location [1] to ASF [2] this will require a change in
>> > > distributionManagement/site/url in a new parent POM and every child
>> POMs:
>> > > if you intend to do a release, please tell and we'll check what to do
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > [1]
>> > > https://svn.apache.org/repos/infra/websites/production/maven
>> /components/
>> > > +
>> > > https://svn.apache.org/repos/infra/websites/production/maven
>> -doxia/compon
>> > > ents/
>> > >
>> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
>> > > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
>> > >
>> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
>> > >> Jira issue for source migration to Git opened:
>> > >> https://issues.apache.org/jira/browse/INFRA-16361
>> > >>
>> > >> Regards,
>> > >>
>> > >> Hervé
>> > >>
>> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
>> > >>> here it is, now Maven site and Doxia sub-site are published by
>> Jenkins
>> > >>>
>> > >>> CMS is not used any more
>> > >>> We'll just need to move components reference documentation out of
>> the
>> > >>> CMS
>> > >>> svn space: I'll do it later with infra
>> > >>>
>> > >>> now, I'll work on GitBox migration
>> > >>>
>> > >>> If someone can write a Jenkinsfile, this would be great: the job
>> has to
>> > >>> be
>> > >>> tied to websites1 node, and the command is simply "mvn site-deploy"
>> > >>>
>> > >>> Regards,
>> > >>>
>> > >>> Hervé
>> > >>>
>> > >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
>> >  FYI, switch is happening currently, I'm on HipChat with infra
>> > 
>> >  then CMS does not have any effect now: this will be Jenkins job (or
>> >  manual
>> >  build)
>> > 
>> >  please don't try to publish anything for now: I'll tell once
>> everything
>> >  is
>> >  stabilized
>> > 
>> >  Regards,
>> > 
>> >  Hervé
>> > 
>> >  Le vendredi 13 avril 2018, 18:15:21 CEST Karl Heinz Marbaise a
>> écrit :
>> > > Hi Hervé,
>> > >
>> > > On 12/04/18 08:17, Hervé BOUTEMY wrote:
>> > >> Hi,
>> > >>
>> > >> I'm working with infra for a good time on Git migration for site
>> > >> source,
>> > >> which will de-facto mean that we drop Apache CMS (that only
>> supports
>> > >> svn
>> > >> for source): see INFRA-16088 [1]
>> > >>
>> > >> Today, we got a first visible result: Jenkins was

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

2018-05-10 Thread Stephen Connolly 
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 site[3]
> > without the need to public via cms[4].
> yes, you get it
>
> >
> >
> > Great work...
> thank you
>
> >
> > BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
> > make a mvn site-deploy ?
> currently, the Jenkins job that builds and deploy the website is manually
> configured
> If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job
> could
> be replaced by the equivalent maven-box generated one
> https://builds.apache.org/job/maven-box/
>
> My personal knowledge of Jenkinsfile and how to test it before committing
> is
> null, then we're staying for the moment with the handcrafted job
>
> Initially, I thought that only the Jenkinsfile would bring us the
> immediate
> rebuild on Git commit: but it seems the Git pubsub feature is available
> also
> on handcrafted job.


Tsk Tsk did you think that little of me that I would implement pub-sub for
multibranch and leave regular in the cold just to try and drive multibranch
adoption :-(


> Then the only benefit we'll have is to remove the handmade
> job: nice to have, but nothing critical...
>
> Regards,
>
> Hervé
>
> >
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> >
> >
> > [1]: https://gitbox.apache.org/repos/asf/maven-site.git
> > [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
> > [3]: https://maven.apache.org/
> > [4]: https://cms.apache.org/maven/
> >
> > On 30/04/18 22:49, Hervé BOUTEMY wrote:
> > > sites sources migration to Git at GitBox done: now you can edit Maven
> and
> > > Doxia sites directly from GitHub through the edit link
> > >
> > > The site build and publish Jenkins jobs are still the previous ones: if
> > > someone creates a Jenkinsfile, we'll have immediate build in maven-box
> > > job.
> > >
> > > Next step will be the move of components svnpubsub location from infra
> > > location [1] to ASF [2] this will require a change in
> > > distributionManagement/site/url in a new parent POM and every child
> POMs:
> > > if you intend to do a release, please tell and we'll check what to do
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1]
> > > https://svn.apache.org/repos/infra/websites/production/
> maven/components/
> > > +
> > > https://svn.apache.org/repos/infra/websites/production/
> maven-doxia/compon
> > > ents/
> > >
> > > [2] https://svn.apache.org/repos/asf/maven/website/components/
> > > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
> > >
> > > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
> > >> Jira issue for source migration to Git opened:
> > >> https://issues.apache.org/jira/browse/INFRA-16361
> > >>
> > >> Regards,
> > >>
> > >> Hervé
> > >>
> > >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
> > >>> here it is, now Maven site and Doxia sub-site are published by
> Jenkins
> > >>>
> > >>> CMS is not used any more
> > >>> We'll just need to move components reference documentation out of the
> > >>> CMS
> > >>> svn space: I'll do it later with infra
> > >>>
> > >>> now, I'll work on GitBox migration
> > >>>
> > >>> If someone can write a Jenkinsfile, this would be great: the job has
> to
> > >>> be
> > >>> tied to websites1 node, and the command is simply "mvn site-deploy"
> > >>>
> > >>> Regards,
> > >>>
> > >>> Hervé
> > >>>
> > >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
> >  FYI, switch is happening currently, I'm on HipChat with infra
> > 
> >  then CMS does not have any effect now: this will be Jenkins job (or
> >  manual
> >  build)
> > 
> >  please don't try to publish anything for now: I'll tell once
> everything
> >  is
> >  stabilized
> > 
> >  Regards,
> > 
> >  Hervé
> > 
> >  Le vendredi 13 avril 2018, 18:15:21 CEST Karl Heinz Marbaise a
> écrit :
> > > Hi Hervé,
> > >
> > > On 12/04/18 08:17, Hervé BOUTEMY wrote:
> > >> Hi,
> > >>
> > >> I'm working with infra for a good time on Git migration for site
> > >> source,
> > >> which will de-facto mean that we drop Apache CMS (that only
> supports
> > >> svn
> > >> for source): see INFRA-16088 [1]
> > >>
> > >> Today, we got a first visible result: Jenkins was able to build
> and
> > >> publish
> > >> html output of the Maven main website to svn [2]
> > >>
> > >> We're now ready to switch to the new Jenkins build, then drop CMS:
> > >> any
> > >> objection to do it?
> > >>
> > >> The plan will be then to switch source to GitBox, to benefit from
> > >> immediate
> > >> commit detection (instead of svn hourly polling): at this step,
> > >> you'll
> > >> be
> > >> able

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

2018-05-10 Thread Hervé BOUTEMY 
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 work...
thank you

> 
> BTW: @Hervé can you explain what is meant to write the Jenkinsfile to
> make a mvn site-deploy ?
currently, the Jenkins job that builds and deploy the website is manually 
configured
If there was a Jenkinsfile in the git repo, the handcrafted Jenkins job could 
be replaced by the equivalent maven-box generated one
https://builds.apache.org/job/maven-box/

My personal knowledge of Jenkinsfile and how to test it before committing is 
null, then we're staying for the moment with the handcrafted job

Initially, I thought that only the Jenkinsfile would bring us the immediate 
rebuild on Git commit: but it seems the Git pubsub feature is available also 
on handcrafted job. Then the only benefit we'll have is to remove the handmade 
job: nice to have, but nothing critical...

Regards,

Hervé

> 
> 
> Kind regards
> Karl Heinz Marbaise
> 
> 
> 
> [1]: https://gitbox.apache.org/repos/asf/maven-site.git
> [2]: https://builds.apache.org/view/M-R/view/Maven/job/maven-site/
> [3]: https://maven.apache.org/
> [4]: https://cms.apache.org/maven/
> 
> On 30/04/18 22:49, Hervé BOUTEMY wrote:
> > sites sources migration to Git at GitBox done: now you can edit Maven and
> > Doxia sites directly from GitHub through the edit link
> > 
> > The site build and publish Jenkins jobs are still the previous ones: if
> > someone creates a Jenkinsfile, we'll have immediate build in maven-box
> > job.
> > 
> > Next step will be the move of components svnpubsub location from infra
> > location [1] to ASF [2] this will require a change in
> > distributionManagement/site/url in a new parent POM and every child POMs:
> > if you intend to do a release, please tell and we'll check what to do
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1]
> > https://svn.apache.org/repos/infra/websites/production/maven/components/
> > +
> > https://svn.apache.org/repos/infra/websites/production/maven-doxia/compon
> > ents/
> > 
> > [2] https://svn.apache.org/repos/asf/maven/website/components/
> > + https://svn.apache.org/repos/asf/maven/doxia/website/components/
> > 
> > Le dimanche 15 avril 2018, 15:25:47 CEST Hervé BOUTEMY a écrit :
> >> Jira issue for source migration to Git opened:
> >> https://issues.apache.org/jira/browse/INFRA-16361
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit :
> >>> here it is, now Maven site and Doxia sub-site are published by Jenkins
> >>> 
> >>> CMS is not used any more
> >>> We'll just need to move components reference documentation out of the
> >>> CMS
> >>> svn space: I'll do it later with infra
> >>> 
> >>> now, I'll work on GitBox migration
> >>> 
> >>> If someone can write a Jenkinsfile, this would be great: the job has to
> >>> be
> >>> tied to websites1 node, and the command is simply "mvn site-deploy"
> >>> 
> >>> Regards,
> >>> 
> >>> Hervé
> >>> 
> >>> Le samedi 14 avril 2018, 22:07:04 CEST Hervé BOUTEMY a écrit :
>  FYI, switch is happening currently, I'm on HipChat with infra
>  
>  then CMS does not have any effect now: this will be Jenkins job (or
>  manual
>  build)
>  
>  please don't try to publish anything for now: I'll tell once everything
>  is
>  stabilized
>  
>  Regards,
>  
>  Hervé
>  
>  Le vendredi 13 avril 2018, 18:15:21 CEST Karl Heinz Marbaise a écrit :
> > Hi Hervé,
> > 
> > On 12/04/18 08:17, Hervé BOUTEMY wrote:
> >> Hi,
> >> 
> >> I'm working with infra for a good time on Git migration for site
> >> source,
> >> which will de-facto mean that we drop Apache CMS (that only supports
> >> svn
> >> for source): see INFRA-16088 [1]
> >> 
> >> Today, we got a first visible result: Jenkins was able to build and
> >> publish
> >> html output of the Maven main website to svn [2]
> >> 
> >> We're now ready to switch to the new Jenkins build, then drop CMS:
> >> any
> >> objection to do it?
> >> 
> >> The plan will be then to switch source to GitBox, to benefit from
> >> immediate
> >> commit detection (instead of svn hourly polling): at this step,
> >> you'll
> >> be
> >> able to do easy site source updates through GitHub, with immediate
> >> publish. I don't see the value of adding a staging step, but if
> >> someone
> >> wants staging, it will be a matter of Jenkinsfile tweaking.
> >> 
> >> In the temporary time with Jenkins polling on source from svn ,
> >> either
> >> you'll wait for less than 1 hour or you'll manually launch the
> >> Jenkins
> >> job
> >> 
> >> any question?
> > 
> > Jenkins will build the Site