Oh So it is not a tool but a process. I see. Sounds very tempting to be honest bit also think we should wait "after summer" to not change all at once.
What do you think? Le 5 juil. 2017 02:21, "John D. Ament" <johndam...@apache.org> a écrit : > Romain, > > For the site generation, if you want to switch to gitwcsub (and dump the > SVN repo) its simply a matter of having a job (buildbot or jenkins) that > will build the commit and push the result to a special branch (most are > using asf-site). Since you're already using mvn to generate the site, I > think all you'd have to do is specify the new repo + branch name. > > John > > > On Tue, Jul 4, 2017 at 12:20 PM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > > > Ok submitted > > https://git-wip-us.apache.org/repos/asf/tomee-tomee-site-generator.git, > > > > @John: do you have more details about gitwcsub, didnt find much except it > > is the git replacement of svnpubsub? idea would be to sync a generated > > folder with the remote "content" repo. Very worse case I can add it to > our > > generator with a java svn or git client, shouldnt take the night ;) > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > 2017-07-04 17:20 GMT+02:00 John D. Ament <johndam...@apache.org>: > > > > > Would be better to request a git repo via https://reporeq.apache.org/ > if > > > you want a repository. You may also want to consider using gitwcsub > > > instead of svnpubsub for the actual generated site. > > > > > > John > > > > > > On Tue, Jul 4, 2017 at 9:15 AM Romain Manni-Bucau < > rmannibu...@gmail.com > > > > > > wrote: > > > > > > > Ok, let say if there is no -1 tonight I'll update the ticket to ask > it > > - > > > it > > > > doesnt hurt worse case so dont think we need to wait much more, in > > > > particular if we want to work on the website now. Let me know if it > is > > a > > > > concern at any level. > > > > > > > > > > > > Romain Manni-Bucau > > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > > <https://blog-rmannibucau.rhcloud.com> | Old Blog > > > > <http://rmannibucau.wordpress.com> | Github < > > > > https://github.com/rmannibucau> | > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > > > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > > > > > 2017-07-04 15:04 GMT+02:00 Jonathan Gallimore < > > > > jonathan.gallim...@gmail.com> > > > > : > > > > > > > > > As in +1 for moving the project :-) > > > > > > > > > > On Tue, Jul 4, 2017 at 2:03 PM, Jonathan Gallimore < > > > > > jonathan.gallim...@gmail.com> wrote: > > > > > > > > > > > +1 > > > > > > > > > > > > On Tue, Jul 4, 2017 at 2:02 PM, Ivan Junckes Filho < > > > > > ivanjunc...@gmail.com> > > > > > > wrote: > > > > > > > > > > > >> I think last time I checked github for the website was not up to > > > date. > > > > > >> > > > > > >> On Tue, Jul 4, 2017 at 10:00 AM, Daniel Cunha < > > > daniels...@apache.org> > > > > > >> wrote: > > > > > >> > > > > > >> > Well, TomEE already moved to git, you don't need to use SVN. > > > > > >> > PR integration already works fine, I saw that with last > > > Jean-Louis's > > > > > >> merge. > > > > > >> > > > > > > >> > But yes, will be awesome to have it, we can use it like a > stage > > > and > > > > > the > > > > > >> > process to deploy in prod will be identical. > > > > > >> > > > > > > >> > +1 for that. > > > > > >> > > > > > > >> > On Tue, Jul 4, 2017 at 9:56 AM, Ivan Junckes Filho < > > > > > >> ivanjunc...@gmail.com> > > > > > >> > wrote: > > > > > >> > > > > > > >> > > This would be great, way better than doing svn patches. > > > > > >> > > > > > > > >> > > +1 > > > > > >> > > > > > > > >> > > On Tue, Jul 4, 2017 at 9:54 AM, Romain Manni-Bucau < > > > > > >> > rmannibu...@gmail.com> > > > > > >> > > wrote: > > > > > >> > > > > > > > >> > > > Hi guys, > > > > > >> > > > > > > > > >> > > > I asked INFRA to proxy our new website project on github > but > > > it > > > > > >> looks > > > > > >> > > hard, > > > > > >> > > > they propose us to move the project to another git repo. > > > > > >> > > > > > > > > >> > > > Anyone against it? > > > > > >> > > > > > > > > >> > > > For reference here is the ticket: > > > > > >> > > > https://issues.apache.org/jira/browse/INFRA-14249 > > > > > >> > > > > > > > > >> > > > Concretely we would get a git-asf/site-tomee-ng.git (or > > > > > equivalent) > > > > > >> and > > > > > >> > > > have a github proxy. > > > > > >> > > > > > > > > >> > > > In term of deployment it would still be the same, ie we > copy > > > the > > > > > >> output > > > > > >> > > to > > > > > >> > > > content/ of the cms subversion repo or we wire pubsub > maven > > > > > plugin. > > > > > >> > > > > > > > > >> > > > Romain Manni-Bucau > > > > > >> > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > > > >> > > > <https://blog-rmannibucau.rhcloud.com> | Old Blog > > > > > >> > > > <http://rmannibucau.wordpress.com> | Github < > > > > https://github.com/ > > > > > >> > > > rmannibucau> | > > > > > >> > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | > JavaEE > > > > > Factory > > > > > >> > > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > > >> > > > > > > > > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > -- > > > > > >> > Daniel Cunha > > > > > >> > https://twitter.com/dvlc_ > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > >
