You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Hervé BOUTEMY <he...@free.fr> on 2017/11/01 06:28:02 UTC
Re: migrating some code to Git
for lazy people, I took time to create the 4 repo on personal GitHub space:
https://github.com/hboutemy/maven-apache-parent
https://github.com/hboutemy/maven-parent
https://github.com/hboutemy/maven-default-skin
https://github.com/hboutemy/maven-fluido-skin
I won't do the same in the future for the 26 shared and 45 plugins, since
manual repo creation is not fun...
Regards,
Hervé
Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> As you probably noticed, I migrated maven-dist-tool [1] to git, using self-
> service Gitbox for the empty repo creation and a migrate-sandbox.sh shell
> script [2] to populate them (after Sling example)
>
> It worked like a charm!
>
> If nobody objects, in 72h, I'll use migrate-pom.sh and migrate-skins.sh to
> create 4 new repos: maven-apache-parent, maven-parent, maven-default-skin
> and maven-fluido-skin
> Please take time to execute the scripts for yourself and check that the
> result is ok for you.
>
> I already prepared migrate-plugins.sh and migrate-shared.sh scripts: I'm
> waiting for Jenkins integration results before trying to migrate this part,
> but you can also take time to check that the resulting git repos from the
> scripts are good.
>
> Regards,
>
> Hervé
>
> [1] https://github.com/apache/maven-dist-tool/
>
> [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: migrating some code to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
for french speaking people, I found a very interesting blog post that looked
to match our use case = just a collection of git repos without cross-repo
development in usual cases
see http://www.yoannsculo.fr/git-repo-outil-gestion-multiples-repositories-arracher-cheveux/
there are some subtle explanation about branch desynchronization: I didn't
really try, but I feel we may be hit
I did not really find much useful doc on Google repo: I don't if it's the name
of the tool that is too generic for a search engine.
But at least, with this blog post, I found exactly our use case.
Regards,
Hervé
Le jeudi 2 novembre 2017, 04:53:18 CET Olivier Lamy a écrit :
> impressive!!
> thanks to setup this!
>
> Cheers
> Olivier
>
> On 2 November 2017 at 03:48, Hervé BOUTEMY <he...@free.fr> wrote:
> > and here is the Google repo demo, with every git repo configured (even the
> > 6
> > tests):
> > https://github.com/hboutemy/maven-aggregator
> >
> > looks promising: if you use the bootstrapping commands from the readme,
> > you
> > should be able to use the repositories in a natural way with basic git
> > commands
> > If you don't play with branches, you should be able to run "repo sync" at
> > any
> > time
> >
> > Please test and report if you're convinced or not
> >
> > If it works well, I'll put this maven-aggregator git repo in GitBox as an
> > official way to get full Maven source (looks as good as trunks from svn)
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> > > adding 2 more repos to the list:
> > > https://github.com/hboutemy/maven-doxia-converter
> > > https://github.com/hboutemy/maven-doxia-linkcheck
> > >
> > > Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > > > for lazy people, I took time to create the 4 repo on personal GitHub
> > > > space:
> > > > https://github.com/hboutemy/maven-apache-parent
> > > > https://github.com/hboutemy/maven-parent
> > > > https://github.com/hboutemy/maven-default-skin
> > > > https://github.com/hboutemy/maven-fluido-skin
> > > >
> > > > I won't do the same in the future for the 26 shared and 45 plugins,
> >
> > since
> >
> > > > manual repo creation is not fun...
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > > > As you probably noticed, I migrated maven-dist-tool [1] to git,
> > > > > using
> > > > > self-
> > > > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > > > shell
> > > > > script [2] to populate them (after Sling example)
> > > > >
> > > > > It worked like a charm!
> > > > >
> > > > > If nobody objects, in 72h, I'll use migrate-pom.sh and
> >
> > migrate-skins.sh
> >
> > > > > to
> > > > > create 4 new repos: maven-apache-parent, maven-parent,
> > > > > maven-default-skin
> > > > > and maven-fluido-skin
> > > > > Please take time to execute the scripts for yourself and check that
> >
> > the
> >
> > > > > result is ok for you.
> >
> > > > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts:
> > I'm
> >
> > > > > waiting for Jenkins integration results before trying to migrate
> > > > > this
> > > > > part,
> > > > > but you can also take time to check that the resulting git repos
> > > > > from
> > > > > the
> > > > > scripts are good.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1] https://github.com/apache/maven-dist-tool/
> > > > >
> > > > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > > > >
> > > > > ------------------------------------------------------------
> >
> > ---------
> >
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: migrating some code to Git
Posted by Olivier Lamy <ol...@apache.org>.
impressive!!
thanks to setup this!
Cheers
Olivier
On 2 November 2017 at 03:48, Hervé BOUTEMY <he...@free.fr> wrote:
> and here is the Google repo demo, with every git repo configured (even the
> 6
> tests):
> https://github.com/hboutemy/maven-aggregator
>
> looks promising: if you use the bootstrapping commands from the readme, you
> should be able to use the repositories in a natural way with basic git
> commands
> If you don't play with branches, you should be able to run "repo sync" at
> any
> time
>
> Please test and report if you're convinced or not
>
> If it works well, I'll put this maven-aggregator git repo in GitBox as an
> official way to get full Maven source (looks as good as trunks from svn)
>
> Regards,
>
> Hervé
>
> Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> > adding 2 more repos to the list:
> > https://github.com/hboutemy/maven-doxia-converter
> > https://github.com/hboutemy/maven-doxia-linkcheck
> >
> > Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > > for lazy people, I took time to create the 4 repo on personal GitHub
> > > space:
> > > https://github.com/hboutemy/maven-apache-parent
> > > https://github.com/hboutemy/maven-parent
> > > https://github.com/hboutemy/maven-default-skin
> > > https://github.com/hboutemy/maven-fluido-skin
> > >
> > > I won't do the same in the future for the 26 shared and 45 plugins,
> since
> > > manual repo creation is not fun...
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > > As you probably noticed, I migrated maven-dist-tool [1] to git, using
> > > > self-
> > > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > > shell
> > > > script [2] to populate them (after Sling example)
> > > >
> > > > It worked like a charm!
> > > >
> > > > If nobody objects, in 72h, I'll use migrate-pom.sh and
> migrate-skins.sh
> > > > to
> > > > create 4 new repos: maven-apache-parent, maven-parent,
> > > > maven-default-skin
> > > > and maven-fluido-skin
> > > > Please take time to execute the scripts for yourself and check that
> the
> > > > result is ok for you.
> > > >
> > > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts:
> I'm
> > > > waiting for Jenkins integration results before trying to migrate this
> > > > part,
> > > > but you can also take time to check that the resulting git repos from
> > > > the
> > > > scripts are good.
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1] https://github.com/apache/maven-dist-tool/
> > > >
> > > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: migrating some code to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
and here is the Google repo demo, with every git repo configured (even the 6
tests):
https://github.com/hboutemy/maven-aggregator
looks promising: if you use the bootstrapping commands from the readme, you
should be able to use the repositories in a natural way with basic git
commands
If you don't play with branches, you should be able to run "repo sync" at any
time
Please test and report if you're convinced or not
If it works well, I'll put this maven-aggregator git repo in GitBox as an
official way to get full Maven source (looks as good as trunks from svn)
Regards,
Hervé
Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> adding 2 more repos to the list:
> https://github.com/hboutemy/maven-doxia-converter
> https://github.com/hboutemy/maven-doxia-linkcheck
>
> Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > for lazy people, I took time to create the 4 repo on personal GitHub
> > space:
> > https://github.com/hboutemy/maven-apache-parent
> > https://github.com/hboutemy/maven-parent
> > https://github.com/hboutemy/maven-default-skin
> > https://github.com/hboutemy/maven-fluido-skin
> >
> > I won't do the same in the future for the 26 shared and 45 plugins, since
> > manual repo creation is not fun...
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > As you probably noticed, I migrated maven-dist-tool [1] to git, using
> > > self-
> > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > shell
> > > script [2] to populate them (after Sling example)
> > >
> > > It worked like a charm!
> > >
> > > If nobody objects, in 72h, I'll use migrate-pom.sh and migrate-skins.sh
> > > to
> > > create 4 new repos: maven-apache-parent, maven-parent,
> > > maven-default-skin
> > > and maven-fluido-skin
> > > Please take time to execute the scripts for yourself and check that the
> > > result is ok for you.
> > >
> > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts: I'm
> > > waiting for Jenkins integration results before trying to migrate this
> > > part,
> > > but you can also take time to check that the resulting git repos from
> > > the
> > > scripts are good.
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://github.com/apache/maven-dist-tool/
> > >
> > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: migrating some code to Git
Posted by Arnaud Héritier <ah...@gmail.com>.
Awesome work Hervé
Thanks a lot
For archetypes split I don't know. Technically we should split them and
they could have different lifecycles but in reality there is no real
activity thus I'm not sure it has some interest
On Sat, Nov 4, 2017 at 2:56 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> migration done [1]
> we now have 22 git repos (maven-resolver has 3 independant branches...)
>
> I'm waiting for feedback before creating maven-aggregator @ ASF (for Google
> repo manifest)
>
> next big migrations will be shared and plugins once Stephen videos and
> solution on scaling Jenkins for our organization will be ready
>
> There a few cases to discuss:
> - Apache Resource Bundles: should IMHO be merged into one unique release:
> any
> taker?
> - Archetypes: split (wait for Jenkins) or not split (and do now)?
> - Maven and Doxia sites: need to see if CMS can checkout from Git, or even
> if
> we should not use CMS any more to build but use Jenkins...
>
> Regards,
>
> Hervé
>
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> Le samedi 4 novembre 2017, 09:50:28 CET Hervé BOUTEMY a écrit :
> > no objection: starting the migration of these 6 repos
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> > > adding 2 more repos to the list:
> > > https://github.com/hboutemy/maven-doxia-converter
> > > https://github.com/hboutemy/maven-doxia-linkcheck
> > >
> > > Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > > > for lazy people, I took time to create the 4 repo on personal GitHub
> > > > space:
> > > > https://github.com/hboutemy/maven-apache-parent
> > > > https://github.com/hboutemy/maven-parent
> > > > https://github.com/hboutemy/maven-default-skin
> > > > https://github.com/hboutemy/maven-fluido-skin
> > > >
> > > > I won't do the same in the future for the 26 shared and 45 plugins,
> > > > since
> > > > manual repo creation is not fun...
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > > > As you probably noticed, I migrated maven-dist-tool [1] to git,
> using
> > > > > self-
> > > > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > > > shell
> > > > > script [2] to populate them (after Sling example)
> > > > >
> > > > > It worked like a charm!
> > > > >
> > > > > If nobody objects, in 72h, I'll use migrate-pom.sh and
> > > > > migrate-skins.sh
> > > > > to
> > > > > create 4 new repos: maven-apache-parent, maven-parent,
> > > > > maven-default-skin
> > > > > and maven-fluido-skin
> > > > > Please take time to execute the scripts for yourself and check that
> > > > > the
> > > > > result is ok for you.
> > > > >
> > > > > I already prepared migrate-plugins.sh and migrate-shared.sh
> scripts:
> > > > > I'm
> > > > > waiting for Jenkins integration results before trying to migrate
> this
> > > > > part,
> > > > > but you can also take time to check that the resulting git repos
> from
> > > > > the
> > > > > scripts are good.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1] https://github.com/apache/maven-dist-tool/
> > > > >
> > > > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > > > >
> > > > > ------------------------------------------------------------
> ---------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: dev-help@maven.apache.org
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: migrating some code to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
migration done [1]
we now have 22 git repos (maven-resolver has 3 independant branches...)
I'm waiting for feedback before creating maven-aggregator @ ASF (for Google
repo manifest)
next big migrations will be shared and plugins once Stephen videos and
solution on scaling Jenkins for our organization will be ready
There a few cases to discuss:
- Apache Resource Bundles: should IMHO be merged into one unique release: any
taker?
- Archetypes: split (wait for Jenkins) or not split (and do now)?
- Maven and Doxia sites: need to see if CMS can checkout from Git, or even if
we should not use CMS any more to build but use Jenkins...
Regards,
Hervé
[1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
Le samedi 4 novembre 2017, 09:50:28 CET Hervé BOUTEMY a écrit :
> no objection: starting the migration of these 6 repos
>
> Regards,
>
> Hervé
>
> Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> > adding 2 more repos to the list:
> > https://github.com/hboutemy/maven-doxia-converter
> > https://github.com/hboutemy/maven-doxia-linkcheck
> >
> > Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > > for lazy people, I took time to create the 4 repo on personal GitHub
> > > space:
> > > https://github.com/hboutemy/maven-apache-parent
> > > https://github.com/hboutemy/maven-parent
> > > https://github.com/hboutemy/maven-default-skin
> > > https://github.com/hboutemy/maven-fluido-skin
> > >
> > > I won't do the same in the future for the 26 shared and 45 plugins,
> > > since
> > > manual repo creation is not fun...
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > > As you probably noticed, I migrated maven-dist-tool [1] to git, using
> > > > self-
> > > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > > shell
> > > > script [2] to populate them (after Sling example)
> > > >
> > > > It worked like a charm!
> > > >
> > > > If nobody objects, in 72h, I'll use migrate-pom.sh and
> > > > migrate-skins.sh
> > > > to
> > > > create 4 new repos: maven-apache-parent, maven-parent,
> > > > maven-default-skin
> > > > and maven-fluido-skin
> > > > Please take time to execute the scripts for yourself and check that
> > > > the
> > > > result is ok for you.
> > > >
> > > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts:
> > > > I'm
> > > > waiting for Jenkins integration results before trying to migrate this
> > > > part,
> > > > but you can also take time to check that the resulting git repos from
> > > > the
> > > > scripts are good.
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1] https://github.com/apache/maven-dist-tool/
> > > >
> > > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: migrating some code to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
no objection: starting the migration of these 6 repos
Regards,
Hervé
Le mercredi 1 novembre 2017, 12:09:58 CET Hervé BOUTEMY a écrit :
> adding 2 more repos to the list:
> https://github.com/hboutemy/maven-doxia-converter
> https://github.com/hboutemy/maven-doxia-linkcheck
>
> Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> > for lazy people, I took time to create the 4 repo on personal GitHub
> > space:
> > https://github.com/hboutemy/maven-apache-parent
> > https://github.com/hboutemy/maven-parent
> > https://github.com/hboutemy/maven-default-skin
> > https://github.com/hboutemy/maven-fluido-skin
> >
> > I won't do the same in the future for the 26 shared and 45 plugins, since
> > manual repo creation is not fun...
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > > As you probably noticed, I migrated maven-dist-tool [1] to git, using
> > > self-
> > > service Gitbox for the empty repo creation and a migrate-sandbox.sh
> > > shell
> > > script [2] to populate them (after Sling example)
> > >
> > > It worked like a charm!
> > >
> > > If nobody objects, in 72h, I'll use migrate-pom.sh and migrate-skins.sh
> > > to
> > > create 4 new repos: maven-apache-parent, maven-parent,
> > > maven-default-skin
> > > and maven-fluido-skin
> > > Please take time to execute the scripts for yourself and check that the
> > > result is ok for you.
> > >
> > > I already prepared migrate-plugins.sh and migrate-shared.sh scripts: I'm
> > > waiting for Jenkins integration results before trying to migrate this
> > > part,
> > > but you can also take time to check that the resulting git repos from
> > > the
> > > scripts are good.
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://github.com/apache/maven-dist-tool/
> > >
> > > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: migrating some code to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
adding 2 more repos to the list:
https://github.com/hboutemy/maven-doxia-converter
https://github.com/hboutemy/maven-doxia-linkcheck
Le mercredi 1 novembre 2017, 07:28:02 CET Hervé BOUTEMY a écrit :
> for lazy people, I took time to create the 4 repo on personal GitHub space:
> https://github.com/hboutemy/maven-apache-parent
> https://github.com/hboutemy/maven-parent
> https://github.com/hboutemy/maven-default-skin
> https://github.com/hboutemy/maven-fluido-skin
>
> I won't do the same in the future for the 26 shared and 45 plugins, since
> manual repo creation is not fun...
>
> Regards,
>
> Hervé
>
> Le mardi 31 octobre 2017, 16:08:01 CET Hervé BOUTEMY a écrit :
> > As you probably noticed, I migrated maven-dist-tool [1] to git, using
> > self-
> > service Gitbox for the empty repo creation and a migrate-sandbox.sh shell
> > script [2] to populate them (after Sling example)
> >
> > It worked like a charm!
> >
> > If nobody objects, in 72h, I'll use migrate-pom.sh and migrate-skins.sh to
> > create 4 new repos: maven-apache-parent, maven-parent, maven-default-skin
> > and maven-fluido-skin
> > Please take time to execute the scripts for yourself and check that the
> > result is ok for you.
> >
> > I already prepared migrate-plugins.sh and migrate-shared.sh scripts: I'm
> > waiting for Jenkins integration results before trying to migrate this
> > part,
> > but you can also take time to check that the resulting git repos from the
> > scripts are good.
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://github.com/apache/maven-dist-tool/
> >
> > [2] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org