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 wrote:
> migration done [1]
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 organi
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 nov
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 e
impressive!!
thanks to setup this!
Cheers
Olivier
On 2 November 2017 at 03:48, Hervé BOUTEMY 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 command
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 do
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/
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 th
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
great, thank you!
we'll discuss it on thursday, when we meet :)
Regards,
Hervé
Le lundi 23 octobre 2017, 10:34:29 CEST Arnaud Héritier a écrit :
> I can help you on this
>
> On Mon, Oct 23, 2017 at 12:15 AM, Hervé BOUTEMY
>
> wrote:
> > I'm happy to do what I'm able to do
> >
> > for the nex
I can help you on this
On Mon, Oct 23, 2017 at 12:15 AM, Hervé BOUTEMY
wrote:
> I'm happy to do what I'm able to do
>
> for the next ones, I fear I don't know how to prepare target git repos:
> I'll
> need help
>
> Regards,
>
> Hervé
>
> Le dimanche 22 octobre 2017, 23:26:44 CEST Olivier Lamy a
I'm happy to do what I'm able to do
for the next ones, I fear I don't know how to prepare target git repos: I'll
need help
Regards,
Hervé
Le dimanche 22 octobre 2017, 23:26:44 CEST Olivier Lamy a écrit :
> Great!
> Thanks to take care of this!
>
> On Mon, 23 Oct 2017 at 7:00 am, Arnaud Hériti
Great!
Thanks to take care of this!
On Mon, 23 Oct 2017 at 7:00 am, Arnaud Héritier wrote:
> Awesome !
>
> On Sun, Oct 22, 2017 at 12:00 PM, Robert Scholte
> wrote:
>
> > Great job, thank you all!
> >
> > Robert
> >
> >
> > On Sun, 22 Oct 2017 11:45:02 +0200, Hervé BOUTEMY >
> > wrote:
> >
> >
Awesome !
On Sun, Oct 22, 2017 at 12:00 PM, Robert Scholte
wrote:
> Great job, thank you all!
>
> Robert
>
>
> On Sun, 22 Oct 2017 11:45:02 +0200, Hervé BOUTEMY
> wrote:
>
> migration done: only remaining task is to rename "trunk" HEAD branch
>> inherited
>> from svn history to "master" (and ev
Great job, thank you all!
Robert
On Sun, 22 Oct 2017 11:45:02 +0200, Hervé BOUTEMY
wrote:
migration done: only remaining task is to rename "trunk" HEAD branch
inherited
from svn history to "master" (and eventually add a MOVED_TO_GIT file in
origin
svn)
The Apache git hosting provided
migration done: only remaining task is to rename "trunk" HEAD branch inherited
from svn history to "master" (and eventually add a MOVED_TO_GIT file in origin
svn)
The Apache git hosting provided is GitBox, unlike previous component that use
Git-Wip: with GitBox, the content is modifiable both a
jira issue created:
https://issues.apache.org/jira/browse/INFRA-15253
Regards,
Hervé
Le samedi 7 octobre 2017, 12:32:00 CEST Hervé BOUTEMY a écrit :
> I wrote a little shell script to check differences between tags in svn and
> git checkout
> the only differences I found for the 6 git repos are:
trying as attachment: hope this will be kept by the ML
usually, only the first variable "MAVEN_REPO=xxx" has to be changed, but Doxia
components required a little tweak on the next 2 variables "SVNBASE=" and
"GITREPO="
Regards,
Hervé
Le samedi 7 octobre 2017, 22:35:07 CEST Arnaud Héritier a é
+1 to create INFRA jira issue to switch following 6
components from svn to the current git mirror:
- Doxia core
- Doxia Sitetools
- Enforcer
- Jxr
- Plugin Tools
- Release
On Sat, Oct 7, 2017 at 10:35 PM, Arnaud Héritier
wrote:
> +1
>
> Can you share the script ?
>
> On Sat, Oct 7, 2017 at 12:32
+1
Can you share the script ?
On Sat, Oct 7, 2017 at 12:32 PM, Hervé BOUTEMY
wrote:
> I wrote a little shell script to check differences between tags in svn and
> git
> checkout
> the only differences I found for the 6 git repos are:
> 1. empty dirs (which exist in svn but are pruned in git)
>
I wrote a little shell script to check differences between tags in svn and git
checkout
the only differences I found for the 6 git repos are:
1. empty dirs (which exist in svn but are pruned in git)
2. one strage case in enforcer-1.2 where a few files seem to have newlines
issues
to me, this can
re-reading our migration process documentation [1], I see "check especially
behaviour on checking out tag"
I suppose that we could compare content between git checkout and svn checkout
for HEAD and every past release
did somebody prepare a shell script for that?
Regards,
Hervé
[1] https://cw
great, thank you for your help
in fact, AFAIK, Apache has already automatic svn2git exports [1] that are then
mirrored to github.
Then we already have:
- https://github.com/apache/maven-doxia/
- https://github.com/apache/maven-doxia-sitetools/
- https://github.com/apache/maven-enforcer/
- https:/
Count me in (for both actual migration and related tasks).
My weapon of choice for SVN -->>GIT would be:
https://github.com/nirvdrum/svn2git (I managed to move dozen of repos few years
ago).
Regards,
Dejan
On 2017-10-04 01:48, Hervé BOUTEMY wrote:
> I'd like to work on Plugin Tools with g
I'd like to work on Plugin Tools with git
While at it, looking at our plan [1], I see we have a few other components
that are ready to migrate:
- Doxia core
- Doxia Sitetools
- Enforcer
- Jxr
- Plugin Tools
- Release
What checks are required before switching these 6 components?
Any volunteer?
R
25 matches
Mail list logo
