You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@tesla.io> on 2014/02/13 04:37:36 UTC
Convert everything to Git
Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
Jason (who would be happy to never execute svn again)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Jason van Zyl <ja...@takari.io>.
That's only because you haven't met me in person.
On Feb 12, 2014, at 10:38 PM, Fred Cooke <fr...@gmail.com> wrote:
> I like you more and more! :-)
>
>
> On Thu, Feb 13, 2014 at 4:37 PM, Jason van Zyl <ja...@tesla.io> wrote:
>
>> Can we start the process of converting everything to Git. I don't really
>> see any benefit in using Subversion any longer.
>>
>> If so then we should just get together for a day and convert them and then
>> get infra to use what we converted to do the flip.
>>
>> Jason (who would be happy to never execute svn again)
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
Simplex sigillum veri. (Simplicity is the seal of truth.)
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
I like you more and more! :-)
On Thu, Feb 13, 2014 at 4:37 PM, Jason van Zyl <ja...@tesla.io> wrote:
> Can we start the process of converting everything to Git. I don't really
> see any benefit in using Subversion any longer.
>
> If so then we should just get together for a day and convert them and then
> get infra to use what we converted to do the flip.
>
> Jason (who would be happy to never execute svn again)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
The SVN repo should probably be retained anyway, just in RO format, and
with a new URL that indicates it shouldn't be used. You can try to retain
all history, but it's never quite in the same form, really. Perhaps no one
cares, though?
+1 for decompose into individual repos.
Fred.
PS, perhaps one day we'll meet, who knows. :-p
On Thu, Feb 13, 2014 at 5:50 PM, Jason van Zyl <ja...@takari.io> wrote:
> Probably a little more decompose like a repository for each plugin and
> shared component. No reason all history can't be retained.
>
> On Feb 12, 2014, at 11:03 PM, Mark Derricutt <ma...@talios.com> wrote:
>
> > Do you envisage one master git repo, or multiple repositories for each
> moveable piece?
> >
> > Full history retainment?
> >
> > On 13 Feb 2014, at 16:37, Jason van Zyl wrote:
> >
> >> Can we start the process of converting everything to Git. I don't
> really see any benefit in using Subversion any longer.
> >>
> >> If so then we should just get together for a day and convert them and
> then get infra to use what we converted to do the flip.
> >>
> >> Jason (who would be happy to never execute svn again)
> >> ---------------------------------------------------------------------
> >> 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
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> To do two things at once is to do neither.
>
> -- Publilius Syrus, Roman slave, first century B.C.
>
>
>
>
>
>
>
>
>
>
Re: Convert everything to Git
Posted by Jason van Zyl <ja...@takari.io>.
Probably a little more decompose like a repository for each plugin and shared component. No reason all history can't be retained.
On Feb 12, 2014, at 11:03 PM, Mark Derricutt <ma...@talios.com> wrote:
> Do you envisage one master git repo, or multiple repositories for each moveable piece?
>
> Full history retainment?
>
> On 13 Feb 2014, at 16:37, Jason van Zyl wrote:
>
>> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>>
>> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>>
>> Jason (who would be happy to never execute svn again)
>> ---------------------------------------------------------------------
>> 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
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
To do two things at once is to do neither.
-- Publilius Syrus, Roman slave, first century B.C.
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
Do you envisage one master git repo, or multiple repositories for each
moveable piece?
Full history retainment?
On 13 Feb 2014, at 16:37, Jason van Zyl wrote:
> Can we start the process of converting everything to Git. I don't
> really see any benefit in using Subversion any longer.
>
> If so then we should just get together for a day and convert them and
> then get infra to use what we converted to do the flip.
>
> Jason (who would be happy to never execute svn again)
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by Thomas Koch <th...@koch.ro>.
With myrepos one (or a team) can list many VCS repos in a config file and do
batch operations on all of the repos or selectively clone (checkout) repos.
http://myrepos.branchable.com
myrepos is written in perl and packaged in Debian:
http://packages.qa.debian.org/m/myrepos.html
Regards, Thomas Koch
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
On 14 Feb 2014, at 2:27, Jason van Zyl wrote:
> Why wouldn't you put something with its own release cycle in its own
> repository?
maven-release-plugin and git's branching/tagging really kinda make that
hard to avoid.
Unless we move EVERYTHING to generations :)
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Barrie Treloar <ba...@gmail.com>.
On 13 February 2014 23:57, Jason van Zyl <ja...@takari.io> wrote:
[del]
> The biggest win for me is working on branches. Working with branches in SVN is horrible, only worse in p4 which is saying a lot. The ability to easily create branches, squash commits, incrementally improve them without fear. I constantly rebase against master and it's really easy with all the great tools like GitX, GitTower, or SourceTree to easily see changes. The Eclipse support for Git is a million times better, and doing anything Git related with JGit in Java is always a pleasure (because the #2 CGit guy, wrote JGit)
[del]
> But for me it's a primarily a personal workflow issue.
I'd really appreciate a write up on that workflow.
I'm still too green using git and I'd rather follow something that
others have thought about and blessed than try to develop that on my
own.
It would also help people wanting to contribute to focus on
contribution rather than version control gymnastics.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Robert Scholte <rf...@apache.org>.
MRELEASE-862, which should fix MRELEASE-812 (both fixed for next release)
However, rumors go this fixes the Git Issue(s), but also that it doesn't.
No good feedback, so I'm not sure if this will be the N-th release in a
row with bad Git support.
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-862
[2] https://jira.codehaus.org/browse/MRELEASE-812
Op Fri, 14 Feb 2014 05:15:11 +0100 schreef Mark Derricutt
<ma...@talios.com>:
> On 14 Feb 2014, at 2:27, Jason van Zyl wrote:
>
>> Why wouldn't you put something with its own release cycle in its own
>> repository?
>
> Actually, whilst we're on the subject - can we get a
> maven-release-plugin out which locks in a newer version of the *-scm-*
> dependencies as currently, m-r-p BREAKS on current git ( due to git
> finally changing the output format of git-status ). So we need to config
> with:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.4.2</version>
> <dependencies>
> <dependency>
> <groupId>org.apache.maven.scm</groupId>
>
> <artifactId>maven-scm-provider-gitexe</artifactId>
> <version>1.9</version>
> </dependency>
> </dependencies>
> .....
>
> Not sure if I ever raised a bug for this in Jira or not...
>
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
On 14 Feb 2014, at 2:27, Jason van Zyl wrote:
> Why wouldn't you put something with its own release cycle in its own
> repository?
Actually, whilst we're on the subject - can we get a
maven-release-plugin out which locks in a newer version of the *-scm-*
dependencies as currently, m-r-p BREAKS on current git ( due to git
finally changing the output format of git-status ). So we need to config
with:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.2</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9</version>
</dependency>
</dependencies>
.....
Not sure if I ever raised a bug for this in Jira or not...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Stephen Connolly <st...@gmail.com>.
Same/similar issue with svn:externals today... IOW if there are unpinned
svn:externals m-r-p does not pin & unpin them during the release:prepare
stage.
I think the scm api may need some refactoring to enable these kind of mixed
repository actions
On 14 February 2014 08:33, Tomasz Krakowiak <ni...@gmail.com>wrote:
> Are you aware that maven-release-plugin isn't currently working with git
> submodules because of http://jira.codehaus.org/browse/SCM-530 ?
>
> (I'm just warning you, so you wouldn't have painful surprise one day)
>
>
> Wiadomość napisana przez Hervé BOUTEMY <he...@free.fr> w dniu 14
> lut 2014, o godz. 09:19:
>
> > No doubt it can be done in general, but the question is on ASF
> (canonical) git
> > repo [1]
> > at the moment, everything seems flat
> > IMHO, some git expert should work with infra to make it more structured
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://git-wip-us.apache.org/repos/asf
> >
> > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> >> I have my private git repo setup in a nested way. No reason you
> couldn't do
> >> that the same for this.
> >>
> >> baseurl/org/apache/mvn/core/componentA.git
> >>
> >> etc.
> >>
> >> Unsure if this addresses your concerns or not, but it's certainly neat
> and
> >> tidy at the server end, and the user can duplicate the path structure
> the
> >> same at home.
> >>
> >> Fred.
> >>
> >> On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
> >>> I'm not a git expert: if there are solutions, yes, they have to be
> found,
> >>> explained, tested, before we launch "convert everything to git"
> >>>
> >>> thank you for any good idea and then any tests from people wanting the
> >>> great
> >>> migration to happen (without wreaking havoc)
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> >>>> Jenkins could build from a super-repo that uses git submodule.
> >>>>
> >>>> Since a quite a few versions ago, git-submodules can now follow a
> branch
> >>>> rather than a fixed SHA1.
> >>>>
> >>>> So you could build/test monolithically, branch/commit individually.
> >>>>
> >>>> Compromise maybe?
> >>>>
> >>>> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> >>>>> each entry would mean 1 git repo + 1Jenkins job (or even more, since
> >>>>> plugins
> >>>>> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> >>>>> for Maven
> >>>>> 3.1.x)
> >>>>> IMHO, we're not ready for such granularity, neither at git nor
> Jenkins
> >>>>> level
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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: Convert everything to Git
Posted by Baptiste Mathus <ml...@batmat.net>.
OK.
But for the record, I was not (yet) proposing to release using the
submodule repo.
More the strategy proposed by Mark: use submodules 'just" to ease
retrieving a whole lot of projects under a working directory tree, and then
release project by project (=repo by repo) as-of today.
Anyway, I suppose that if this workflow was to become required/on the
critical path, this bug would receive more attention to get tackled.
2014-02-14 9:33 GMT+01:00 Tomasz Krakowiak <ni...@gmail.com>:
> Are you aware that maven-release-plugin isn’t currently working with git
> submodules because of http://jira.codehaus.org/browse/SCM-530 ?
>
> (I’m just warning you, so you wouldn’t have painful surprise one day)
>
>
> Wiadomość napisana przez Hervé BOUTEMY <he...@free.fr> w dniu 14
> lut 2014, o godz. 09:19:
>
> > No doubt it can be done in general, but the question is on ASF
> (canonical) git
> > repo [1]
> > at the moment, everything seems flat
> > IMHO, some git expert should work with infra to make it more structured
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://git-wip-us.apache.org/repos/asf
> >
> > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> >> I have my private git repo setup in a nested way. No reason you
> couldn't do
> >> that the same for this.
> >>
> >> baseurl/org/apache/mvn/core/componentA.git
> >>
> >> etc.
> >>
> >> Unsure if this addresses your concerns or not, but it's certainly neat
> and
> >> tidy at the server end, and the user can duplicate the path structure
> the
> >> same at home.
> >>
> >> Fred.
> >>
> >> On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
> >>> I'm not a git expert: if there are solutions, yes, they have to be
> found,
> >>> explained, tested, before we launch "convert everything to git"
> >>>
> >>> thank you for any good idea and then any tests from people wanting the
> >>> great
> >>> migration to happen (without wreaking havoc)
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> >>>> Jenkins could build from a super-repo that uses git submodule.
> >>>>
> >>>> Since a quite a few versions ago, git-submodules can now follow a
> branch
> >>>> rather than a fixed SHA1.
> >>>>
> >>>> So you could build/test monolithically, branch/commit individually.
> >>>>
> >>>> Compromise maybe?
> >>>>
> >>>> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> >>>>> each entry would mean 1 git repo + 1Jenkins job (or even more, since
> >>>>> plugins
> >>>>> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> >>>>> for Maven
> >>>>> 3.1.x)
> >>>>> IMHO, we're not ready for such granularity, neither at git nor
> Jenkins
> >>>>> level
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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
> >
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!
>
Re: Convert everything to Git
Posted by Tomasz Krakowiak <ni...@gmail.com>.
Are you aware that maven-release-plugin isn’t currently working with git submodules because of http://jira.codehaus.org/browse/SCM-530 ?
(I’m just warning you, so you wouldn’t have painful surprise one day)
Wiadomość napisana przez Hervé BOUTEMY <he...@free.fr> w dniu 14 lut 2014, o godz. 09:19:
> No doubt it can be done in general, but the question is on ASF (canonical) git
> repo [1]
> at the moment, everything seems flat
> IMHO, some git expert should work with infra to make it more structured
>
> Regards,
>
> Hervé
>
> [1] https://git-wip-us.apache.org/repos/asf
>
> Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
>> I have my private git repo setup in a nested way. No reason you couldn't do
>> that the same for this.
>>
>> baseurl/org/apache/mvn/core/componentA.git
>>
>> etc.
>>
>> Unsure if this addresses your concerns or not, but it's certainly neat and
>> tidy at the server end, and the user can duplicate the path structure the
>> same at home.
>>
>> Fred.
>>
>> On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <he...@free.fr>wrote:
>>> I'm not a git expert: if there are solutions, yes, they have to be found,
>>> explained, tested, before we launch "convert everything to git"
>>>
>>> thank you for any good idea and then any tests from people wanting the
>>> great
>>> migration to happen (without wreaking havoc)
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
>>>> Jenkins could build from a super-repo that uses git submodule.
>>>>
>>>> Since a quite a few versions ago, git-submodules can now follow a branch
>>>> rather than a fixed SHA1.
>>>>
>>>> So you could build/test monolithically, branch/commit individually.
>>>>
>>>> Compromise maybe?
>>>>
>>>> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
>>>>> each entry would mean 1 git repo + 1Jenkins job (or even more, since
>>>>> plugins
>>>>> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
>>>>> for Maven
>>>>> 3.1.x)
>>>>> IMHO, we're not ready for such granularity, neither at git nor Jenkins
>>>>> level
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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: Convert everything to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
Linking to podcasts and articles is intertresting, especially for those who
haven't done it before.
What this needs i a volunteer to do the task.....
K
16. feb. 2014 04:07 skrev "Mark Derricutt" <ma...@talios.com> følgende:
> A really good podcast on the subject of migration a large project, and
> large team from subversion to git can be heard at:
>
> http://episodes.gitminutes.com/2013/08/gitminutes-20-
> mick-wever-on-migrating.html
>
> Also:
>
> http://episodes.gitminutes.com/2013/12/gitminutes-26-
> campbell-barton-on-tricky.html
>
> was a very good episode on tricky migrations to git. Recommending
> listening for anyone contemplating such a large migration.
>
> This was a blog post I wrote ages ago on my own svn->git migration:
>
> http://www.theoryinpractice.net/post/1350252794/
> repository-migration-from-subversion-to-git
>
> Once I got my workflow down with doing filter-branch's it was reasonably
> painless to extract a repository into smaller repositories. Time consuming,
> but not toooo difficult.
>
> Mark
>
>
> On 14 Feb 2014, at 21:35, Fred Cooke wrote:
>
> Some of the converters/one of the converters correctly creates git tags
>> from svn branches, however I'm unsure what happens if the "tag" has been
>> committed to as sometimes happens with n00b devs in SVN land.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
A really good podcast on the subject of migration a large project, and
large team from subversion to git can be heard at:
http://episodes.gitminutes.com/2013/08/gitminutes-20-mick-wever-on-migrating.html
Also:
http://episodes.gitminutes.com/2013/12/gitminutes-26-campbell-barton-on-tricky.html
was a very good episode on tricky migrations to git. Recommending
listening for anyone contemplating such a large migration.
This was a blog post I wrote ages ago on my own svn->git migration:
http://www.theoryinpractice.net/post/1350252794/repository-migration-from-subversion-to-git
Once I got my workflow down with doing filter-branch's it was reasonably
painless to extract a repository into smaller repositories. Time
consuming, but not toooo difficult.
Mark
On 14 Feb 2014, at 21:35, Fred Cooke wrote:
> Some of the converters/one of the converters correctly creates git
> tags
> from svn branches, however I'm unsure what happens if the "tag" has
> been
> committed to as sometimes happens with n00b devs in SVN land.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
Some of the converters/one of the converters correctly creates git tags
from svn branches, however I'm unsure what happens if the "tag" has been
committed to as sometimes happens with n00b devs in SVN land.
On Fri, Feb 14, 2014 at 9:31 PM, Lennart Jörelid
<le...@gmail.com>wrote:
> While I agree that the migration from Subversion to Git can be somewhat
> labour-intensive,
> it can be an ongoing activity, simply migrating piece by piece.
>
> Since there is a particular issue with the Maven release plugin creating
> what is normally
> interpreted as Git branches (as opposed to Git tags) one does normally need
> to run some
> correct-the-history type scripts following the standard migration. Of
> course, the more nonstandard
> of a Subversion stucture one originates from, the more complex these
> scripts become.
>
> The migration itself is - in my experience - something fairly
> straightforward.
> It's the script-to-correct-history phase which follows the VCS migration
> that is somewhat cumbersome.
>
> ... and it therefore becomes important to migrate big repos piece by piece.
>
>
> 2014-02-14 9:23 GMT+01:00 Kristian Rosenvold <kristian.rosenvold@gmail.com
> >:
>
> > I think the main problem with especially maven-plugins is the sheer
> amount
> > of work required to convert these to individual repositories, especially
> > due to the somewhat not-good structure of the current clone.
> >
> > The others should be fairly straight forward, splitting maven-shared
> > included.
> >
> > Kristian
> >
> >
> >
> >
> >
> > 2014-02-14 9:19 GMT+01:00 Hervé BOUTEMY <he...@free.fr>:
> >
> > > No doubt it can be done in general, but the question is on ASF
> > (canonical)
> > > git
> > > repo [1]
> > > at the moment, everything seems flat
> > > IMHO, some git expert should work with infra to make it more structured
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://git-wip-us.apache.org/repos/asf
> > >
> > > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> > > > I have my private git repo setup in a nested way. No reason you
> > couldn't
> > > do
> > > > that the same for this.
> > > >
> > > > baseurl/org/apache/mvn/core/componentA.git
> > > >
> > > > etc.
> > > >
> > > > Unsure if this addresses your concerns or not, but it's certainly
> neat
> > > and
> > > > tidy at the server end, and the user can duplicate the path structure
> > the
> > > > same at home.
> > > >
> > > > Fred.
> > > >
> > > > On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <
> herve.boutemy@free.fr
> > > >wrote:
> > > > > I'm not a git expert: if there are solutions, yes, they have to be
> > > found,
> > > > > explained, tested, before we launch "convert everything to git"
> > > > >
> > > > > thank you for any good idea and then any tests from people wanting
> > the
> > > > > great
> > > > > migration to happen (without wreaking havoc)
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > > > > > Jenkins could build from a super-repo that uses git submodule.
> > > > > >
> > > > > > Since a quite a few versions ago, git-submodules can now follow a
> > > branch
> > > > > > rather than a fixed SHA1.
> > > > > >
> > > > > > So you could build/test monolithically, branch/commit
> individually.
> > > > > >
> > > > > > Compromise maybe?
> > > > > >
> > > > > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > > > > > each entry would mean 1 git repo + 1Jenkins job (or even more,
> > > since
> > > > > > > plugins
> > > > > > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven
> > 3.0.x, 1
> > > > > > > for Maven
> > > > > > > 3.1.x)
> > > > > > > IMHO, we're not ready for such granularity, neither at git nor
> > > Jenkins
> > > > > > > level
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > 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
> > >
> > >
> >
>
>
>
> --
>
> --
> +==============================+
> | Bästa hälsningar,
> | [sw. "Best regards"]
> |
> | Lennart Jörelid
> | EAI Architect & Integrator
> |
> | jGuru Europe AB
> | Mölnlycke - Kista
> |
> | Email: lj@jguru.se
> | URL: www.jguru.se
> | Phone
> | (skype): jgurueurope
> | (intl): +46 708 507 603
> | (domestic): 0708 - 507 603
> +==============================+
>
Re: Convert everything to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
We already know that maven-plugins is going to be a big PITA unless we just
decide to stay with the current git-svn clone and accept it structure.
Having done quite a few migrations I know I'd be spending a truckload of
time getting the filter-branch scripts and the rewrites working properly
(the advantage being that once it's right for one project it can probably
be applied to all of them).
I think the many-repo issue can be solved with scripts or tooling, it does
not bother me too much. But the current maven-plugins (and to some extent
maven-shared) are a problem.
Essentially nothing will happen with maven-plugins until someone steps up
to do it.
Kristian
2014-02-14 9:31 GMT+01:00 Lennart Jörelid <le...@gmail.com>:
> While I agree that the migration from Subversion to Git can be somewhat
> labour-intensive,
> it can be an ongoing activity, simply migrating piece by piece.
>
> Since there is a particular issue with the Maven release plugin creating
> what is normally
> interpreted as Git branches (as opposed to Git tags) one does normally need
> to run some
> correct-the-history type scripts following the standard migration. Of
> course, the more nonstandard
> of a Subversion stucture one originates from, the more complex these
> scripts become.
>
> The migration itself is - in my experience - something fairly
> straightforward.
> It's the script-to-correct-history phase which follows the VCS migration
> that is somewhat cumbersome.
>
> ... and it therefore becomes important to migrate big repos piece by piece.
>
>
> 2014-02-14 9:23 GMT+01:00 Kristian Rosenvold <kristian.rosenvold@gmail.com
> >:
>
> > I think the main problem with especially maven-plugins is the sheer
> amount
> > of work required to convert these to individual repositories, especially
> > due to the somewhat not-good structure of the current clone.
> >
> > The others should be fairly straight forward, splitting maven-shared
> > included.
> >
> > Kristian
> >
> >
> >
> >
> >
> > 2014-02-14 9:19 GMT+01:00 Hervé BOUTEMY <he...@free.fr>:
> >
> > > No doubt it can be done in general, but the question is on ASF
> > (canonical)
> > > git
> > > repo [1]
> > > at the moment, everything seems flat
> > > IMHO, some git expert should work with infra to make it more structured
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://git-wip-us.apache.org/repos/asf
> > >
> > > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> > > > I have my private git repo setup in a nested way. No reason you
> > couldn't
> > > do
> > > > that the same for this.
> > > >
> > > > baseurl/org/apache/mvn/core/componentA.git
> > > >
> > > > etc.
> > > >
> > > > Unsure if this addresses your concerns or not, but it's certainly
> neat
> > > and
> > > > tidy at the server end, and the user can duplicate the path structure
> > the
> > > > same at home.
> > > >
> > > > Fred.
> > > >
> > > > On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <
> herve.boutemy@free.fr
> > > >wrote:
> > > > > I'm not a git expert: if there are solutions, yes, they have to be
> > > found,
> > > > > explained, tested, before we launch "convert everything to git"
> > > > >
> > > > > thank you for any good idea and then any tests from people wanting
> > the
> > > > > great
> > > > > migration to happen (without wreaking havoc)
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > > > > > Jenkins could build from a super-repo that uses git submodule.
> > > > > >
> > > > > > Since a quite a few versions ago, git-submodules can now follow a
> > > branch
> > > > > > rather than a fixed SHA1.
> > > > > >
> > > > > > So you could build/test monolithically, branch/commit
> individually.
> > > > > >
> > > > > > Compromise maybe?
> > > > > >
> > > > > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > > > > > each entry would mean 1 git repo + 1Jenkins job (or even more,
> > > since
> > > > > > > plugins
> > > > > > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven
> > 3.0.x, 1
> > > > > > > for Maven
> > > > > > > 3.1.x)
> > > > > > > IMHO, we're not ready for such granularity, neither at git nor
> > > Jenkins
> > > > > > > level
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > 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
> > >
> > >
> >
>
>
>
> --
>
> --
> +==============================+
> | Bästa hälsningar,
> | [sw. "Best regards"]
> |
> | Lennart Jörelid
> | EAI Architect & Integrator
> |
> | jGuru Europe AB
> | Mölnlycke - Kista
> |
> | Email: lj@jguru.se
> | URL: www.jguru.se
> | Phone
> | (skype): jgurueurope
> | (intl): +46 708 507 603
> | (domestic): 0708 - 507 603
> +==============================+
>
Re: Convert everything to Git
Posted by Lennart Jörelid <le...@gmail.com>.
While I agree that the migration from Subversion to Git can be somewhat
labour-intensive,
it can be an ongoing activity, simply migrating piece by piece.
Since there is a particular issue with the Maven release plugin creating
what is normally
interpreted as Git branches (as opposed to Git tags) one does normally need
to run some
correct-the-history type scripts following the standard migration. Of
course, the more nonstandard
of a Subversion stucture one originates from, the more complex these
scripts become.
The migration itself is - in my experience - something fairly
straightforward.
It's the script-to-correct-history phase which follows the VCS migration
that is somewhat cumbersome.
... and it therefore becomes important to migrate big repos piece by piece.
2014-02-14 9:23 GMT+01:00 Kristian Rosenvold <kr...@gmail.com>:
> I think the main problem with especially maven-plugins is the sheer amount
> of work required to convert these to individual repositories, especially
> due to the somewhat not-good structure of the current clone.
>
> The others should be fairly straight forward, splitting maven-shared
> included.
>
> Kristian
>
>
>
>
>
> 2014-02-14 9:19 GMT+01:00 Hervé BOUTEMY <he...@free.fr>:
>
> > No doubt it can be done in general, but the question is on ASF
> (canonical)
> > git
> > repo [1]
> > at the moment, everything seems flat
> > IMHO, some git expert should work with infra to make it more structured
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://git-wip-us.apache.org/repos/asf
> >
> > Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> > > I have my private git repo setup in a nested way. No reason you
> couldn't
> > do
> > > that the same for this.
> > >
> > > baseurl/org/apache/mvn/core/componentA.git
> > >
> > > etc.
> > >
> > > Unsure if this addresses your concerns or not, but it's certainly neat
> > and
> > > tidy at the server end, and the user can duplicate the path structure
> the
> > > same at home.
> > >
> > > Fred.
> > >
> > > On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <herve.boutemy@free.fr
> > >wrote:
> > > > I'm not a git expert: if there are solutions, yes, they have to be
> > found,
> > > > explained, tested, before we launch "convert everything to git"
> > > >
> > > > thank you for any good idea and then any tests from people wanting
> the
> > > > great
> > > > migration to happen (without wreaking havoc)
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > > > > Jenkins could build from a super-repo that uses git submodule.
> > > > >
> > > > > Since a quite a few versions ago, git-submodules can now follow a
> > branch
> > > > > rather than a fixed SHA1.
> > > > >
> > > > > So you could build/test monolithically, branch/commit individually.
> > > > >
> > > > > Compromise maybe?
> > > > >
> > > > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > > > > each entry would mean 1 git repo + 1Jenkins job (or even more,
> > since
> > > > > > plugins
> > > > > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven
> 3.0.x, 1
> > > > > > for Maven
> > > > > > 3.1.x)
> > > > > > IMHO, we're not ready for such granularity, neither at git nor
> > Jenkins
> > > > > > level
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > 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
> >
> >
>
--
--
+==============================+
| Bästa hälsningar,
| [sw. "Best regards"]
|
| Lennart Jörelid
| EAI Architect & Integrator
|
| jGuru Europe AB
| Mölnlycke - Kista
|
| Email: lj@jguru.se
| URL: www.jguru.se
| Phone
| (skype): jgurueurope
| (intl): +46 708 507 603
| (domestic): 0708 - 507 603
+==============================+
Re: Convert everything to Git
Posted by Kristian Rosenvold <kr...@gmail.com>.
I think the main problem with especially maven-plugins is the sheer amount
of work required to convert these to individual repositories, especially
due to the somewhat not-good structure of the current clone.
The others should be fairly straight forward, splitting maven-shared
included.
Kristian
2014-02-14 9:19 GMT+01:00 Hervé BOUTEMY <he...@free.fr>:
> No doubt it can be done in general, but the question is on ASF (canonical)
> git
> repo [1]
> at the moment, everything seems flat
> IMHO, some git expert should work with infra to make it more structured
>
> Regards,
>
> Hervé
>
> [1] https://git-wip-us.apache.org/repos/asf
>
> Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> > I have my private git repo setup in a nested way. No reason you couldn't
> do
> > that the same for this.
> >
> > baseurl/org/apache/mvn/core/componentA.git
> >
> > etc.
> >
> > Unsure if this addresses your concerns or not, but it's certainly neat
> and
> > tidy at the server end, and the user can duplicate the path structure the
> > same at home.
> >
> > Fred.
> >
> > On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <herve.boutemy@free.fr
> >wrote:
> > > I'm not a git expert: if there are solutions, yes, they have to be
> found,
> > > explained, tested, before we launch "convert everything to git"
> > >
> > > thank you for any good idea and then any tests from people wanting the
> > > great
> > > migration to happen (without wreaking havoc)
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > > > Jenkins could build from a super-repo that uses git submodule.
> > > >
> > > > Since a quite a few versions ago, git-submodules can now follow a
> branch
> > > > rather than a fixed SHA1.
> > > >
> > > > So you could build/test monolithically, branch/commit individually.
> > > >
> > > > Compromise maybe?
> > > >
> > > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > > > each entry would mean 1 git repo + 1Jenkins job (or even more,
> since
> > > > > plugins
> > > > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> > > > > for Maven
> > > > > 3.1.x)
> > > > > IMHO, we're not ready for such granularity, neither at git nor
> Jenkins
> > > > > level
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
No doubt it can be done in general, but the question is on ASF (canonical) git
repo [1]
at the moment, everything seems flat
IMHO, some git expert should work with infra to make it more structured
Regards,
Hervé
[1] https://git-wip-us.apache.org/repos/asf
Le vendredi 14 février 2014 20:23:34 Fred Cooke a écrit :
> I have my private git repo setup in a nested way. No reason you couldn't do
> that the same for this.
>
> baseurl/org/apache/mvn/core/componentA.git
>
> etc.
>
> Unsure if this addresses your concerns or not, but it's certainly neat and
> tidy at the server end, and the user can duplicate the path structure the
> same at home.
>
> Fred.
>
> On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <he...@free.fr>wrote:
> > I'm not a git expert: if there are solutions, yes, they have to be found,
> > explained, tested, before we launch "convert everything to git"
> >
> > thank you for any good idea and then any tests from people wanting the
> > great
> > migration to happen (without wreaking havoc)
> >
> > Regards,
> >
> > Hervé
> >
> > Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > > Jenkins could build from a super-repo that uses git submodule.
> > >
> > > Since a quite a few versions ago, git-submodules can now follow a branch
> > > rather than a fixed SHA1.
> > >
> > > So you could build/test monolithically, branch/commit individually.
> > >
> > > Compromise maybe?
> > >
> > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> > > > plugins
> > > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> > > > for Maven
> > > > 3.1.x)
> > > > IMHO, we're not ready for such granularity, neither at git nor Jenkins
> > > > level
> > >
> > > ---------------------------------------------------------------------
> > > 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: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
I have my private git repo setup in a nested way. No reason you couldn't do
that the same for this.
baseurl/org/apache/mvn/core/componentA.git
etc.
Unsure if this addresses your concerns or not, but it's certainly neat and
tidy at the server end, and the user can duplicate the path structure the
same at home.
Fred.
On Fri, Feb 14, 2014 at 7:33 PM, Hervé BOUTEMY <he...@free.fr>wrote:
> I'm not a git expert: if there are solutions, yes, they have to be found,
> explained, tested, before we launch "convert everything to git"
>
> thank you for any good idea and then any tests from people wanting the
> great
> migration to happen (without wreaking havoc)
>
> Regards,
>
> Hervé
>
> Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> > Jenkins could build from a super-repo that uses git submodule.
> >
> > Since a quite a few versions ago, git-submodules can now follow a branch
> > rather than a fixed SHA1.
> >
> > So you could build/test monolithically, branch/commit individually.
> >
> > Compromise maybe?
> >
> > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> > > plugins
> > > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> > > for Maven
> > > 3.1.x)
> > > IMHO, we're not ready for such granularity, neither at git nor Jenkins
> > > level
> >
> > ---------------------------------------------------------------------
> > 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: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
I'm not a git expert: if there are solutions, yes, they have to be found,
explained, tested, before we launch "convert everything to git"
thank you for any good idea and then any tests from people wanting the great
migration to happen (without wreaking havoc)
Regards,
Hervé
Le vendredi 14 février 2014 17:10:07 Mark Derricutt a écrit :
> Jenkins could build from a super-repo that uses git submodule.
>
> Since a quite a few versions ago, git-submodules can now follow a branch
> rather than a fixed SHA1.
>
> So you could build/test monolithically, branch/commit individually.
>
> Compromise maybe?
>
> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> > plugins
> > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> > for Maven
> > 3.1.x)
> > IMHO, we're not ready for such granularity, neither at git nor Jenkins
> > level
>
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
Le jeudi 13 février 2014 14:29:12 Jason van Zyl a écrit :
> On Feb 13, 2014, at 12:28 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> > Le jeudi 13 février 2014 08:27:14 Jason van Zyl a écrit :
> >> On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> >>> the only show stopper I know is for svn trunk which contains a lot of
> >>> components
> >>>
> >>> so -1 for plugins, shared, skins, resources
> >>
> >> Why wouldn't you put something with its own release cycle in its own
> >> repository?
> >
> > because plugins = 44 entries, shared = 20 entries, skins = 6 entries,
> > resources = 5 entries
> > sum = 75 entries
> >
> > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> > plugins have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x,
> > 1 for Maven 3.1.x)
> > IMHO, we're not ready for such granularity, neither at git nor Jenkins
> > level
> I'm used to more granularity in Git, if something has a separate lifecycle
> it doesn't bother me to have a different repo for it. In the case where
> there are a bunch of things that have different artifactIds but really only
> get released together then group those together. I can't speak to what
> Jenkins can handle.
yes, I know that this is the good solution if we switch to git
I'm just anticipating consequences, since we have 100 release roots, and
actual svn structure reduce these as much less svn trunks. I know that with
git, the right structure is 100 release roots = 100 git repos.
If git repos could be organized in directory structures, like dist area for
exemple, Ithis would be better, particularly if the 100 Maven repos were in a
maven subdirectory, instead of flat inside Apache git root.
And such differences go to ASF Jenkins, and to ASF Sonar.
I don't know who will take t his charge the lot of work that such a change
will require: having done the work (with a few others) for svnpubsub, and
anticipating git migration wil require even more work, I just want to be sure
that sufficient energy will be given to the effective switch because sufficient
people are convinced there is a real win for the Maven comunity (not only
technical facts from git zealots, who are probably right on much points, but
just ignore consequences on the whole project)
> >>> but no problem for me for other release roots containing only one
> >>> component
> >>> [1]
> >>>
> >>> notice I don't see much gain: did we get much patches for components
> >>> already in git? did nobody send a patch through github for a svn
> >>> component replicated to github? Is everybody fluent with git (I still
> >>> ses
> >>> much "merge" commits in git)
> >>> So what's the rationale, really? (apart from bashing one scm over the
> >>> other, in one or another direction)
> >>
> >> The biggest win for me is working on branches. Working with branches in
> >> SVN
> >> is horrible, only worse in p4 which is saying a lot.
> >
> > what is "p4"?
>
> Perforce.
>
> > which component from the 75 previous entries have branches? should require
> > branches?
>
> For Maven core I have 10 branches locally, I share some of them with others
> and this is very easy with Git. This is the issue with SVN, it's so
> cumbersome to make branches and use them no one does.
> >> The ability to easily
> >> create branches, squash commits, incrementally improve them without fear.
> >> I
> >> constantly rebase against master and it's really easy with all the great
> >> tools like GitX, GitTower, or SourceTree to easily see changes. The
> >> Eclipse
> >> support for Git is a million times better, and doing anything Git related
> >> with JGit in Java is always a pleasure (because the #2 CGit guy, wrote
> >> JGit)
> >
> > do you mean you intend to contribute to other components than core?
>
> I think it would make it easier for anyone to contribute if they wanted to.
>
> >> As far as potential contribution if you look at Apache projects at Github
> >> there are varying numbers of forks and pull requests but for some of them
> >> it's pretty significant.
> >>
> >> But for me it's a primarily a personal workflow issue.
> >>
> >>> So I'm -0 on such a change for parts where I feel it would be feasible
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> [1]
> >>> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/
> >>> d
> >>> ist-tool-check-source-release.html>
> >>>
> >>> Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
> >>>> Can we start the process of converting everything to Git. I don't
> >>>> really
> >>>> see any benefit in using Subversion any longer.
> >>>>
> >>>> If so then we should just get together for a day and convert them and
> >>>> then
> >>>> get infra to use what we converted to do the flip.
> >>>>
> >>>> Jason (who would be happy to never execute svn again)
> >>>> ---------------------------------------------------------------------
> >>>> 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
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> http://twitter.com/takari_io
> >> ---------------------------------------------------------
> >>
> >> Our achievements speak for themselves. What we have to keep track
> >> of are our failures, discouragements and doubts. We tend to forget
> >> the past difficulties, the many false starts, and the painful
> >> groping. We see our past achievements as the end result of a
> >> clean forward thrust, and our present difficulties as
> >> signs of decline and decay.
> >>
> >> -- Eric Hoffer, Reflections on the Human Condition
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
> -- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Stephen Connolly <st...@gmail.com>.
On 13 February 2014 17:28, Hervé BOUTEMY <he...@free.fr> wrote:
> Le jeudi 13 février 2014 08:27:14 Jason van Zyl a écrit :
> > On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr>
> wrote:
> > > the only show stopper I know is for svn trunk which contains a lot of
> > > components
> > >
> > > so -1 for plugins, shared, skins, resources
> >
> > Why wouldn't you put something with its own release cycle in its own
> > repository?
> because plugins = 44 entries, shared = 20 entries, skins = 6 entries,
> resources = 5 entries
> sum = 75 entries
>
> each entry would mean 1 git repo + 1Jenkins job (or even more, since
> plugins
> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for
> Maven
> 3.1.x)
> IMHO, we're not ready for such granularity, neither at git nor Jenkins
> level
>
We should look at getting the literate plugin installed on ASF jenkins once
I get it finished... would greatly simplify the job requirements
>
>
> > > but no problem for me for other release roots containing only one
> > > component
> > > [1]
> > >
> > > notice I don't see much gain: did we get much patches for components
> > > already in git? did nobody send a patch through github for a svn
> > > component replicated to github? Is everybody fluent with git (I still
> ses
> > > much "merge" commits in git)
> > > So what's the rationale, really? (apart from bashing one scm over the
> > > other, in one or another direction)
> >
> > The biggest win for me is working on branches. Working with branches in
> SVN
> > is horrible, only worse in p4 which is saying a lot.
> what is "p4"?
> which component from the 75 previous entries have branches? should require
> branches?
>
> > The ability to easily
> > create branches, squash commits, incrementally improve them without
> fear. I
> > constantly rebase against master and it's really easy with all the great
> > tools like GitX, GitTower, or SourceTree to easily see changes. The
> Eclipse
> > support for Git is a million times better, and doing anything Git related
> > with JGit in Java is always a pleasure (because the #2 CGit guy, wrote
> > JGit)
> do you mean you intend to contribute to other components than core?
>
> >
> > As far as potential contribution if you look at Apache projects at Github
> > there are varying numbers of forks and pull requests but for some of them
> > it's pretty significant.
> >
> > But for me it's a primarily a personal workflow issue.
> >
> > > So I'm -0 on such a change for parts where I feel it would be feasible
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1]
> > >
> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/d
> > > ist-tool-check-source-release.html>
> > > Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
> > >> Can we start the process of converting everything to Git. I don't
> really
> > >> see any benefit in using Subversion any longer.
> > >>
> > >> If so then we should just get together for a day and convert them and
> > >> then
> > >> get infra to use what we converted to do the flip.
> > >>
> > >> Jason (who would be happy to never execute svn again)
> > >> ---------------------------------------------------------------------
> > >> 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
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > ---------------------------------------------------------
> >
> > Our achievements speak for themselves. What we have to keep track
> > of are our failures, discouragements and doubts. We tend to forget
> > the past difficulties, the many false starts, and the painful
> > groping. We see our past achievements as the end result of a
> > clean forward thrust, and our present difficulties as
> > signs of decline and decay.
> >
> > -- Eric Hoffer, Reflections on the Human Condition
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
Great posts, Jason! There are so many reasons to dump SVN, but controlled
branch sharing and personal work flow are big ones for me, too. I have a
dozen or more local branches of my project, too, and like you, I rebase
against what I publish until they're ready, then publish them, and rebase
the others, etc. It gives you immense power to work freely and experiment
and ultimately contribute higher quality material once you finally publish.
But I'm clearly preaching to the choir ;-)
On Fri, Feb 14, 2014 at 8:29 AM, Jason van Zyl <ja...@takari.io> wrote:
> On Feb 13, 2014, at 12:28 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>
> > Le jeudi 13 février 2014 08:27:14 Jason van Zyl a écrit :
> >> On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr>
> wrote:
> >>> the only show stopper I know is for svn trunk which contains a lot of
> >>> components
> >>>
> >>> so -1 for plugins, shared, skins, resources
> >>
> >> Why wouldn't you put something with its own release cycle in its own
> >> repository?
> > because plugins = 44 entries, shared = 20 entries, skins = 6 entries,
> > resources = 5 entries
> > sum = 75 entries
> >
> > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> plugins
> > have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for
> Maven
> > 3.1.x)
> > IMHO, we're not ready for such granularity, neither at git nor Jenkins
> level
>
> I'm used to more granularity in Git, if something has a separate lifecycle
> it doesn't bother me to have a different repo for it. In the case where
> there are a bunch of things that have different artifactIds but really only
> get released together then group those together. I can't speak to what
> Jenkins can handle.
>
> >
> >
> >>> but no problem for me for other release roots containing only one
> >>> component
> >>> [1]
> >>>
> >>> notice I don't see much gain: did we get much patches for components
> >>> already in git? did nobody send a patch through github for a svn
> >>> component replicated to github? Is everybody fluent with git (I still
> ses
> >>> much "merge" commits in git)
> >>> So what's the rationale, really? (apart from bashing one scm over the
> >>> other, in one or another direction)
> >>
> >> The biggest win for me is working on branches. Working with branches in
> SVN
> >> is horrible, only worse in p4 which is saying a lot.
> > what is "p4"?
>
> Perforce.
>
> > which component from the 75 previous entries have branches? should
> require
> > branches?
> >
>
> For Maven core I have 10 branches locally, I share some of them with
> others and this is very easy with Git. This is the issue with SVN, it's so
> cumbersome to make branches and use them no one does.
>
> >> The ability to easily
> >> create branches, squash commits, incrementally improve them without
> fear. I
> >> constantly rebase against master and it's really easy with all the great
> >> tools like GitX, GitTower, or SourceTree to easily see changes. The
> Eclipse
> >> support for Git is a million times better, and doing anything Git
> related
> >> with JGit in Java is always a pleasure (because the #2 CGit guy, wrote
> >> JGit)
> > do you mean you intend to contribute to other components than core?
> >
>
> I think it would make it easier for anyone to contribute if they wanted to.
>
> >>
> >> As far as potential contribution if you look at Apache projects at
> Github
> >> there are varying numbers of forks and pull requests but for some of
> them
> >> it's pretty significant.
> >>
> >> But for me it's a primarily a personal workflow issue.
> >>
> >>> So I'm -0 on such a change for parts where I feel it would be feasible
> >>>
> >>> Regards,
> >>>
> >>> Hervé
> >>>
> >>> [1]
> >>>
> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/d
> >>> ist-tool-check-source-release.html>
> >>> Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
> >>>> Can we start the process of converting everything to Git. I don't
> really
> >>>> see any benefit in using Subversion any longer.
> >>>>
> >>>> If so then we should just get together for a day and convert them and
> >>>> then
> >>>> get infra to use what we converted to do the flip.
> >>>>
> >>>> Jason (who would be happy to never execute svn again)
> >>>> ---------------------------------------------------------------------
> >>>> 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
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> http://twitter.com/takari_io
> >> ---------------------------------------------------------
> >>
> >> Our achievements speak for themselves. What we have to keep track
> >> of are our failures, discouragements and doubts. We tend to forget
> >> the past difficulties, the many false starts, and the painful
> >> groping. We see our past achievements as the end result of a
> >> clean forward thrust, and our present difficulties as
> >> signs of decline and decay.
> >>
> >> -- Eric Hoffer, Reflections on the Human Condition
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
> -- Thoreau
>
>
>
>
>
>
>
>
>
>
Re: Convert everything to Git
Posted by Jason van Zyl <ja...@takari.io>.
On Feb 13, 2014, at 12:28 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> Le jeudi 13 février 2014 08:27:14 Jason van Zyl a écrit :
>> On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr> wrote:
>>> the only show stopper I know is for svn trunk which contains a lot of
>>> components
>>>
>>> so -1 for plugins, shared, skins, resources
>>
>> Why wouldn't you put something with its own release cycle in its own
>> repository?
> because plugins = 44 entries, shared = 20 entries, skins = 6 entries,
> resources = 5 entries
> sum = 75 entries
>
> each entry would mean 1 git repo + 1Jenkins job (or even more, since plugins
> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for Maven
> 3.1.x)
> IMHO, we're not ready for such granularity, neither at git nor Jenkins level
I'm used to more granularity in Git, if something has a separate lifecycle it doesn't bother me to have a different repo for it. In the case where there are a bunch of things that have different artifactIds but really only get released together then group those together. I can't speak to what Jenkins can handle.
>
>
>>> but no problem for me for other release roots containing only one
>>> component
>>> [1]
>>>
>>> notice I don't see much gain: did we get much patches for components
>>> already in git? did nobody send a patch through github for a svn
>>> component replicated to github? Is everybody fluent with git (I still ses
>>> much "merge" commits in git)
>>> So what's the rationale, really? (apart from bashing one scm over the
>>> other, in one or another direction)
>>
>> The biggest win for me is working on branches. Working with branches in SVN
>> is horrible, only worse in p4 which is saying a lot.
> what is "p4"?
Perforce.
> which component from the 75 previous entries have branches? should require
> branches?
>
For Maven core I have 10 branches locally, I share some of them with others and this is very easy with Git. This is the issue with SVN, it's so cumbersome to make branches and use them no one does.
>> The ability to easily
>> create branches, squash commits, incrementally improve them without fear. I
>> constantly rebase against master and it's really easy with all the great
>> tools like GitX, GitTower, or SourceTree to easily see changes. The Eclipse
>> support for Git is a million times better, and doing anything Git related
>> with JGit in Java is always a pleasure (because the #2 CGit guy, wrote
>> JGit)
> do you mean you intend to contribute to other components than core?
>
I think it would make it easier for anyone to contribute if they wanted to.
>>
>> As far as potential contribution if you look at Apache projects at Github
>> there are varying numbers of forks and pull requests but for some of them
>> it's pretty significant.
>>
>> But for me it's a primarily a personal workflow issue.
>>
>>> So I'm -0 on such a change for parts where I feel it would be feasible
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> [1]
>>> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/d
>>> ist-tool-check-source-release.html>
>>> Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
>>>> Can we start the process of converting everything to Git. I don't really
>>>> see any benefit in using Subversion any longer.
>>>>
>>>> If so then we should just get together for a day and convert them and
>>>> then
>>>> get infra to use what we converted to do the flip.
>>>>
>>>> Jason (who would be happy to never execute svn again)
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>> Our achievements speak for themselves. What we have to keep track
>> of are our failures, discouragements and doubts. We tend to forget
>> the past difficulties, the many false starts, and the painful
>> groping. We see our past achievements as the end result of a
>> clean forward thrust, and our present difficulties as
>> signs of decline and decay.
>>
>> -- Eric Hoffer, Reflections on the Human Condition
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
Re: Convert everything to Git
Posted by Baptiste Mathus <bm...@batmat.net>.
git clone --recursive
https://github.com/Batmat/asciidoctor-maven-plugin-issue-494-html5-backend-not-working?
2014-02-14 9:21 GMT+01:00 Hervé BOUTEMY <he...@free.fr>:
> found the doc: seems interesting
>
> any live example to show?
> or a demo on skins, for example, ie not much submodules, so it seems a good
> cancidate for tests
>
> Regards,
>
> Hervé
>
> Le vendredi 14 février 2014 08:46:32 Baptiste Mathus a écrit :
> > +1 on the submodule solution. We started using it some months ago since
> the
> > branch option came out.
> > As a simplistic analogy, you can see it as svn: externals equivalent.
> >
> > It helps developers (and ci configuration) to retrieve many related
> > projects in only one clone command.
> >
> > My 2 cents
> >
> > Le 14 févr. 2014 05:10, "Mark Derricutt" <ma...@talios.com> a écrit :
> > > Jenkins could build from a super-repo that uses git submodule.
> > >
> > > Since a quite a few versions ago, git-submodules can now follow a
> branch
> > > rather than a fixed SHA1.
> > >
> > > So you could build/test monolithically, branch/commit individually.
> > >
> > > Compromise maybe?
> > >
> > > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> > >
> > >> plugins
> > >> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> for
> > >> Maven
> > >> 3.1.x)
> > >> IMHO, we're not ready for such granularity, neither at git nor Jenkins
> > >> level
> > >
> > > ---------------------------------------------------------------------
> > > 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
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
found the doc: seems interesting
any live example to show?
or a demo on skins, for example, ie not much submodules, so it seems a good
cancidate for tests
Regards,
Hervé
Le vendredi 14 février 2014 08:46:32 Baptiste Mathus a écrit :
> +1 on the submodule solution. We started using it some months ago since the
> branch option came out.
> As a simplistic analogy, you can see it as svn: externals equivalent.
>
> It helps developers (and ci configuration) to retrieve many related
> projects in only one clone command.
>
> My 2 cents
>
> Le 14 févr. 2014 05:10, "Mark Derricutt" <ma...@talios.com> a écrit :
> > Jenkins could build from a super-repo that uses git submodule.
> >
> > Since a quite a few versions ago, git-submodules can now follow a branch
> > rather than a fixed SHA1.
> >
> > So you could build/test monolithically, branch/commit individually.
> >
> > Compromise maybe?
> >
> > On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> > each entry would mean 1 git repo + 1Jenkins job (or even more, since
> >
> >> plugins
> >> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for
> >> Maven
> >> 3.1.x)
> >> IMHO, we're not ready for such granularity, neither at git nor Jenkins
> >> level
> >
> > ---------------------------------------------------------------------
> > 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: Convert everything to Git
Posted by Baptiste Mathus <bm...@batmat.net>.
+1 on the submodule solution. We started using it some months ago since the
branch option came out.
As a simplistic analogy, you can see it as svn: externals equivalent.
It helps developers (and ci configuration) to retrieve many related
projects in only one clone command.
My 2 cents
Le 14 févr. 2014 05:10, "Mark Derricutt" <ma...@talios.com> a écrit :
> Jenkins could build from a super-repo that uses git submodule.
>
> Since a quite a few versions ago, git-submodules can now follow a branch
> rather than a fixed SHA1.
>
> So you could build/test monolithically, branch/commit individually.
>
> Compromise maybe?
>
>
> On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
>
> each entry would mean 1 git repo + 1Jenkins job (or even more, since
>> plugins
>> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for
>> Maven
>> 3.1.x)
>> IMHO, we're not ready for such granularity, neither at git nor Jenkins
>> level
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
Jenkins could build from a super-repo that uses git submodule.
Since a quite a few versions ago, git-submodules can now follow a branch
rather than a fixed SHA1.
So you could build/test monolithically, branch/commit individually.
Compromise maybe?
On 14 Feb 2014, at 6:28, Hervé BOUTEMY wrote:
> each entry would mean 1 git repo + 1Jenkins job (or even more, since
> plugins
> have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1
> for Maven
> 3.1.x)
> IMHO, we're not ready for such granularity, neither at git nor Jenkins
> level
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
Le jeudi 13 février 2014 08:27:14 Jason van Zyl a écrit :
> On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> > the only show stopper I know is for svn trunk which contains a lot of
> > components
> >
> > so -1 for plugins, shared, skins, resources
>
> Why wouldn't you put something with its own release cycle in its own
> repository?
because plugins = 44 entries, shared = 20 entries, skins = 6 entries,
resources = 5 entries
sum = 75 entries
each entry would mean 1 git repo + 1Jenkins job (or even more, since plugins
have multiple Jenkins jobs: 1 for Maven 2.2.x, 1 for Maven 3.0.x, 1 for Maven
3.1.x)
IMHO, we're not ready for such granularity, neither at git nor Jenkins level
> > but no problem for me for other release roots containing only one
> > component
> > [1]
> >
> > notice I don't see much gain: did we get much patches for components
> > already in git? did nobody send a patch through github for a svn
> > component replicated to github? Is everybody fluent with git (I still ses
> > much "merge" commits in git)
> > So what's the rationale, really? (apart from bashing one scm over the
> > other, in one or another direction)
>
> The biggest win for me is working on branches. Working with branches in SVN
> is horrible, only worse in p4 which is saying a lot.
what is "p4"?
which component from the 75 previous entries have branches? should require
branches?
> The ability to easily
> create branches, squash commits, incrementally improve them without fear. I
> constantly rebase against master and it's really easy with all the great
> tools like GitX, GitTower, or SourceTree to easily see changes. The Eclipse
> support for Git is a million times better, and doing anything Git related
> with JGit in Java is always a pleasure (because the #2 CGit guy, wrote
> JGit)
do you mean you intend to contribute to other components than core?
>
> As far as potential contribution if you look at Apache projects at Github
> there are varying numbers of forks and pull requests but for some of them
> it's pretty significant.
>
> But for me it's a primarily a personal workflow issue.
>
> > So I'm -0 on such a change for parts where I feel it would be feasible
> >
> > Regards,
> >
> > Hervé
> >
> > [1]
> > https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/d
> > ist-tool-check-source-release.html>
> > Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
> >> Can we start the process of converting everything to Git. I don't really
> >> see any benefit in using Subversion any longer.
> >>
> >> If so then we should just get together for a day and convert them and
> >> then
> >> get infra to use what we converted to do the flip.
> >>
> >> Jason (who would be happy to never execute svn again)
> >> ---------------------------------------------------------------------
> >> 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
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> Our achievements speak for themselves. What we have to keep track
> of are our failures, discouragements and doubts. We tend to forget
> the past difficulties, the many false starts, and the painful
> groping. We see our past achievements as the end result of a
> clean forward thrust, and our present difficulties as
> signs of decline and decay.
>
> -- Eric Hoffer, Reflections on the Human Condition
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Jason van Zyl <ja...@takari.io>.
On Feb 13, 2014, at 1:36 AM, Hervé BOUTEMY <he...@free.fr> wrote:
> the only show stopper I know is for svn trunk which contains a lot of
> components
>
> so -1 for plugins, shared, skins, resources
>
Why wouldn't you put something with its own release cycle in its own repository?
> but no problem for me for other release roots containing only one component
> [1]
>
> notice I don't see much gain: did we get much patches for components already
> in git? did nobody send a patch through github for a svn component replicated
> to github? Is everybody fluent with git (I still ses much "merge" commits in
> git)
> So what's the rationale, really? (apart from bashing one scm over the other,
> in one or another direction)
>
The biggest win for me is working on branches. Working with branches in SVN is horrible, only worse in p4 which is saying a lot. The ability to easily create branches, squash commits, incrementally improve them without fear. I constantly rebase against master and it's really easy with all the great tools like GitX, GitTower, or SourceTree to easily see changes. The Eclipse support for Git is a million times better, and doing anything Git related with JGit in Java is always a pleasure (because the #2 CGit guy, wrote JGit)
As far as potential contribution if you look at Apache projects at Github there are varying numbers of forks and pull requests but for some of them it's pretty significant.
But for me it's a primarily a personal workflow issue.
> So I'm -0 on such a change for parts where I feel it would be feasible
>
> Regards,
>
> Hervé
>
> [1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html
>
> Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
>> Can we start the process of converting everything to Git. I don't really see
>> any benefit in using Subversion any longer.
>>
>> If so then we should just get together for a day and convert them and then
>> get infra to use what we converted to do the flip.
>>
>> Jason (who would be happy to never execute svn again)
>> ---------------------------------------------------------------------
>> 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
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
Our achievements speak for themselves. What we have to keep track
of are our failures, discouragements and doubts. We tend to forget
the past difficulties, the many false starts, and the painful
groping. We see our past achievements as the end result of a
clean forward thrust, and our present difficulties as
signs of decline and decay.
-- Eric Hoffer, Reflections on the Human Condition
Re: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
the only show stopper I know is for svn trunk which contains a lot of
components
so -1 for plugins, shared, skins, resources
but no problem for me for other release roots containing only one component
[1]
notice I don't see much gain: did we get much patches for components already
in git? did nobody send a patch through github for a svn component replicated
to github? Is everybody fluent with git (I still ses much "merge" commits in
git)
So what's the rationale, really? (apart from bashing one scm over the other,
in one or another direction)
So I'm -0 on such a change for parts where I feel it would be feasible
Regards,
Hervé
[1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html
Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit :
> Can we start the process of converting everything to Git. I don't really see
> any benefit in using Subversion any longer.
>
> If so then we should just get together for a day and convert them and then
> get infra to use what we converted to do the flip.
>
> Jason (who would be happy to never execute svn again)
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by sebb <se...@gmail.com>.
AIUI, SVN is still required by Infra because of svnpubsub:
- for the dist repo (that is not a big deal)
- for websites (might cause some grief)
On 13 February 2014 03:37, Jason van Zyl <ja...@tesla.io> wrote:
> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>
> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>
> Jason (who would be happy to never execute svn again)
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by Dennis Lundberg <de...@gmail.com>.
On Thu, Feb 20, 2014 at 10:27 PM, Jason van Zyl <ja...@takari.io> wrote:
>
> On Feb 20, 2014, at 1:07 PM, Dennis Lundberg <de...@gmail.com> wrote:
>
>> Hi Jason
>>
>> While I'm finally starting to see the potential with a DVCS like git,
>> there are a couple of things that stands in the way of migrating, for
>> example plugins, to git:
>>
>> 1. Judging by our resident git gurus, it will require quite some
>> effort to prepare for and execute the actual migration. Do we have
>> someone with enough knowledge and time to do it?
>>
>
> I'm willing and I think Kristian would help as well.
>
>> 2. Our own tooling, in particular maven-release-plugin, still isn't
>> good enough for git use. IMO we need to get that fixed and verified on
>> our own releases before we migrate any more components to git.
>>
>
> I only release core and that works fine which begs the question: do we want to normalize our repository structure to simplify the tooling requirements. What exactly doesn't work? Trying to release a single thing out of a repository containing many things?
See the issues that Robert pointed out. I haven't run into the issues
myself, but I've seen lots of reports and discussions about them.
Let's use our projects that have already moved to git, and make them
work well together with maven-release-plugin and git. When that is
done and working fine, people willing to do the migration of the other
projects can dive in.
>
>> On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
>>> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>>>
>>> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>>>
>>> Jason (who would be happy to never execute svn again)
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> I never make the mistake of arguing with people for whose opinions I have no respect.
>
> -- Edward Gibbon
>
>
>
>
>
>
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Robert Scholte <rf...@apache.org>.
Personally I don't have the need, but if we want to move projects to Git,
this is probably one of the easy ones.
Robert
Op Wed, 12 Mar 2014 03:03:21 +0100 schreef Hervé BOUTEMY
<he...@free.fr>:
> no problem for me on this one
>
> if someone creates a new git repository, it would be nice to create a
> Maven
> root git repository with submodules definition to every actual git module
>
> Regards,
>
> Hervé
>
> Le mardi 11 mars 2014 16:34:26 Baptiste Mathus a écrit :
>> Hi all,
>>
>> Wondering, wouldn't maven-release be a good next candidate for a Git
>> migration?
>> I'm currently working locally with the maven-release github mirror, but
>> just had to checkout svn trunk to have a look at MRELEASE-431's robert's
>> current proposal (yes, I could've also git svn'ed it).
>>
>> Cheers
>>
>> 2014-02-20 23:13 GMT+01:00 Fred Cooke <fr...@gmail.com>:
>> > + <extension>
>> > + <groupId>org.apache.maven.wagon</groupId>
>> > + <artifactId>wagon-ssh-external</artifactId>
>> > + <version>${extension.version.wagon}</version>
>> > + </extension>
>> >
>> > It was SSH settings that were not being respected. Things like ports
>> and
>> > ssh hosts vs DNS lookups, etc.
>> >
>> > There were other issues with multi-module-parents vs ONLY-parents vs
>> > aggregator poms. MRELEASE-814
>> >
>> > https://jira.codehaus.org/browse/MRELEASE-812
>> > https://jira.codehaus.org/browse/MRELEASE-815
>> >
>> > Other issues were m-site-p in terms of variables and inheritance and
>> > uploads, which work OK for general generation.
>> >
>> > IIRC the results of these bugs was that I had a lot of unwanted
>> > duplication
>> > of config that I couldn't inherit because it got mal-processed.
>> Nothing
>> > worse, but duplication is evil and makes baby Jesus and other equally
>> > ordinary small children cry.
>> >
>> > Then there are things that are just generally broken and don't affect
>> git
>> > worse than other SCMs
>> >
>> > <!-- <scmCommentPrefix>Releasing
>> ${project.artifactId}
>> > version ${project.version} </scmCommentPrefix> --> <!-- Space trimmed
>> and
>> > version snapshot, yuck. -->
>> >
>> > But I'm OT now.
>> >
>> > Fred.
>> >
>> > On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <ma...@talios.com>
>> wrote:
>> > > On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
>> > > I only release core and that works fine which begs the question:
>> do we
>> > >
>> > >> want to normalize our repository structure to simplify the tooling
>> > >> requirements. What exactly doesn't work? Trying to release a single
>> >
>> > thing
>> >
>> > >> out of a repository containing many things?
>> > >
>> > > A stock m-r-p config will break using the latest releases of git (
>> due
>> > > to
>> > > depending on an old version of the -scm- artefacts ) which I've
>> > > mentioned
>> > > before, and I believe there are commits awaiting release to resolve
>> > > this.
>> > >
>> > > m-r-p also _really_ likes to release from the root directory of a
>> > > repository, so doing independent releases from sub
>> directories/modules
>> > > is
>> > > difficult ( there is a setting which lets this work, but that's just
>> > > unpleasant ) - but due to git's tagging/branching being repository
>> wide
>> > > just releasing an individual module really is unpleasant.
>> > >
>> > > Basically, if modules have a constant release cadence/version
>> numbering
>> > > scheme, they can release together in a single repo, otherwise they
>> > > should
>> > > be separate. This however I don't see as a "problem with git
>> tooling in
>> > > maven" - just good practise.
>> > >
>> > > Mark
>> >
>> > --
>> > Baptiste <Batmat> MATHUS - http://batmat.net
>> > Sauvez un arbre,
>> > Mangez un castor ! nbsp;!
>
>
> ---------------------------------------------------------------------
> 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: Convert everything to Git
Posted by Hervé BOUTEMY <he...@free.fr>.
no problem for me on this one
if someone creates a new git repository, it would be nice to create a Maven
root git repository with submodules definition to every actual git module
Regards,
Hervé
Le mardi 11 mars 2014 16:34:26 Baptiste Mathus a écrit :
> Hi all,
>
> Wondering, wouldn't maven-release be a good next candidate for a Git
> migration?
> I'm currently working locally with the maven-release github mirror, but
> just had to checkout svn trunk to have a look at MRELEASE-431's robert's
> current proposal (yes, I could've also git svn'ed it).
>
> Cheers
>
> 2014-02-20 23:13 GMT+01:00 Fred Cooke <fr...@gmail.com>:
> > + <extension>
> > + <groupId>org.apache.maven.wagon</groupId>
> > + <artifactId>wagon-ssh-external</artifactId>
> > + <version>${extension.version.wagon}</version>
> > + </extension>
> >
> > It was SSH settings that were not being respected. Things like ports and
> > ssh hosts vs DNS lookups, etc.
> >
> > There were other issues with multi-module-parents vs ONLY-parents vs
> > aggregator poms. MRELEASE-814
> >
> > https://jira.codehaus.org/browse/MRELEASE-812
> > https://jira.codehaus.org/browse/MRELEASE-815
> >
> > Other issues were m-site-p in terms of variables and inheritance and
> > uploads, which work OK for general generation.
> >
> > IIRC the results of these bugs was that I had a lot of unwanted
> > duplication
> > of config that I couldn't inherit because it got mal-processed. Nothing
> > worse, but duplication is evil and makes baby Jesus and other equally
> > ordinary small children cry.
> >
> > Then there are things that are just generally broken and don't affect git
> > worse than other SCMs
> >
> > <!-- <scmCommentPrefix>Releasing ${project.artifactId}
> > version ${project.version} </scmCommentPrefix> --> <!-- Space trimmed and
> > version snapshot, yuck. -->
> >
> > But I'm OT now.
> >
> > Fred.
> >
> > On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <ma...@talios.com> wrote:
> > > On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
> > > I only release core and that works fine which begs the question: do we
> > >
> > >> want to normalize our repository structure to simplify the tooling
> > >> requirements. What exactly doesn't work? Trying to release a single
> >
> > thing
> >
> > >> out of a repository containing many things?
> > >
> > > A stock m-r-p config will break using the latest releases of git ( due
> > > to
> > > depending on an old version of the -scm- artefacts ) which I've
> > > mentioned
> > > before, and I believe there are commits awaiting release to resolve
> > > this.
> > >
> > > m-r-p also _really_ likes to release from the root directory of a
> > > repository, so doing independent releases from sub directories/modules
> > > is
> > > difficult ( there is a setting which lets this work, but that's just
> > > unpleasant ) - but due to git's tagging/branching being repository wide
> > > just releasing an individual module really is unpleasant.
> > >
> > > Basically, if modules have a constant release cadence/version numbering
> > > scheme, they can release together in a single repo, otherwise they
> > > should
> > > be separate. This however I don't see as a "problem with git tooling in
> > > maven" - just good practise.
> > >
> > > Mark
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor ! nbsp;!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Baptiste Mathus <ml...@batmat.net>.
Hi all,
Wondering, wouldn't maven-release be a good next candidate for a Git
migration?
I'm currently working locally with the maven-release github mirror, but
just had to checkout svn trunk to have a look at MRELEASE-431's robert's
current proposal (yes, I could've also git svn'ed it).
Cheers
2014-02-20 23:13 GMT+01:00 Fred Cooke <fr...@gmail.com>:
> + <extension>
> + <groupId>org.apache.maven.wagon</groupId>
> + <artifactId>wagon-ssh-external</artifactId>
> + <version>${extension.version.wagon}</version>
> + </extension>
>
> It was SSH settings that were not being respected. Things like ports and
> ssh hosts vs DNS lookups, etc.
>
> There were other issues with multi-module-parents vs ONLY-parents vs
> aggregator poms. MRELEASE-814
>
> https://jira.codehaus.org/browse/MRELEASE-812
> https://jira.codehaus.org/browse/MRELEASE-815
>
> Other issues were m-site-p in terms of variables and inheritance and
> uploads, which work OK for general generation.
>
> IIRC the results of these bugs was that I had a lot of unwanted duplication
> of config that I couldn't inherit because it got mal-processed. Nothing
> worse, but duplication is evil and makes baby Jesus and other equally
> ordinary small children cry.
>
> Then there are things that are just generally broken and don't affect git
> worse than other SCMs
>
> <!-- <scmCommentPrefix>Releasing ${project.artifactId}
> version ${project.version} </scmCommentPrefix> --> <!-- Space trimmed and
> version snapshot, yuck. -->
>
> But I'm OT now.
>
> Fred.
>
>
> On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <ma...@talios.com> wrote:
>
> > On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
> >
> > I only release core and that works fine which begs the question: do we
> >> want to normalize our repository structure to simplify the tooling
> >> requirements. What exactly doesn't work? Trying to release a single
> thing
> >> out of a repository containing many things?
> >>
> >
> > A stock m-r-p config will break using the latest releases of git ( due to
> > depending on an old version of the -scm- artefacts ) which I've mentioned
> > before, and I believe there are commits awaiting release to resolve this.
> >
> > m-r-p also _really_ likes to release from the root directory of a
> > repository, so doing independent releases from sub directories/modules is
> > difficult ( there is a setting which lets this work, but that's just
> > unpleasant ) - but due to git's tagging/branching being repository wide
> > just releasing an individual module really is unpleasant.
> >
> > Basically, if modules have a constant release cadence/version numbering
> > scheme, they can release together in a single repo, otherwise they should
> > be separate. This however I don't see as a "problem with git tooling in
> > maven" - just good practise.
> >
> > Mark
> >
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!
>
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
+ <extension>
+ <groupId>org.apache.maven.wagon</groupId>
+ <artifactId>wagon-ssh-external</artifactId>
+ <version>${extension.version.wagon}</version>
+ </extension>
It was SSH settings that were not being respected. Things like ports and
ssh hosts vs DNS lookups, etc.
There were other issues with multi-module-parents vs ONLY-parents vs
aggregator poms. MRELEASE-814
https://jira.codehaus.org/browse/MRELEASE-812
https://jira.codehaus.org/browse/MRELEASE-815
Other issues were m-site-p in terms of variables and inheritance and
uploads, which work OK for general generation.
IIRC the results of these bugs was that I had a lot of unwanted duplication
of config that I couldn't inherit because it got mal-processed. Nothing
worse, but duplication is evil and makes baby Jesus and other equally
ordinary small children cry.
Then there are things that are just generally broken and don't affect git
worse than other SCMs
<!-- <scmCommentPrefix>Releasing ${project.artifactId}
version ${project.version} </scmCommentPrefix> --> <!-- Space trimmed and
version snapshot, yuck. -->
But I'm OT now.
Fred.
On Fri, Feb 21, 2014 at 10:58 AM, Mark Derricutt <ma...@talios.com> wrote:
> On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
>
> I only release core and that works fine which begs the question: do we
>> want to normalize our repository structure to simplify the tooling
>> requirements. What exactly doesn't work? Trying to release a single thing
>> out of a repository containing many things?
>>
>
> A stock m-r-p config will break using the latest releases of git ( due to
> depending on an old version of the -scm- artefacts ) which I've mentioned
> before, and I believe there are commits awaiting release to resolve this.
>
> m-r-p also _really_ likes to release from the root directory of a
> repository, so doing independent releases from sub directories/modules is
> difficult ( there is a setting which lets this work, but that's just
> unpleasant ) - but due to git's tagging/branching being repository wide
> just releasing an individual module really is unpleasant.
>
> Basically, if modules have a constant release cadence/version numbering
> scheme, they can release together in a single repo, otherwise they should
> be separate. This however I don't see as a "problem with git tooling in
> maven" - just good practise.
>
> Mark
>
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
> I only release core and that works fine which begs the question: do we
> want to normalize our repository structure to simplify the tooling
> requirements. What exactly doesn't work? Trying to release a single
> thing out of a repository containing many things?
A stock m-r-p config will break using the latest releases of git ( due
to depending on an old version of the -scm- artefacts ) which I've
mentioned before, and I believe there are commits awaiting release to
resolve this.
m-r-p also _really_ likes to release from the root directory of a
repository, so doing independent releases from sub directories/modules
is difficult ( there is a setting which lets this work, but that's just
unpleasant ) - but due to git's tagging/branching being repository wide
just releasing an individual module really is unpleasant.
Basically, if modules have a constant release cadence/version numbering
scheme, they can release together in a single repo, otherwise they
should be separate. This however I don't see as a "problem with git
tooling in maven" - just good practise.
Mark
Re: Convert everything to Git
Posted by Fred Cooke <fr...@gmail.com>.
The entire SCM interface is very SVN-centric IMO. I raised a number of git
related m-rel-p issues some time ago, but have been busy moving countries
and more in the mean time. I doubt there has been progress on them, though.
One pretty much required a core change to Maven (perhaps something for
4.0.0?) which IIRC people were adamantly against.
One example off the top of my head is allowing meaningful tags to be
created. Another was the git provider not respecting git configuration, I
worked around that by using native git IIRC. There were other things,
nothing HUGE, and mostly work-around-able but still not ideal for general
use IMO.
Fred.
On Fri, Feb 21, 2014 at 10:27 AM, Jason van Zyl <ja...@takari.io> wrote:
>
> On Feb 20, 2014, at 1:07 PM, Dennis Lundberg <de...@gmail.com>
> wrote:
>
> > Hi Jason
> >
> > While I'm finally starting to see the potential with a DVCS like git,
> > there are a couple of things that stands in the way of migrating, for
> > example plugins, to git:
> >
> > 1. Judging by our resident git gurus, it will require quite some
> > effort to prepare for and execute the actual migration. Do we have
> > someone with enough knowledge and time to do it?
> >
>
> I'm willing and I think Kristian would help as well.
>
> > 2. Our own tooling, in particular maven-release-plugin, still isn't
> > good enough for git use. IMO we need to get that fixed and verified on
> > our own releases before we migrate any more components to git.
> >
>
> I only release core and that works fine which begs the question: do we
> want to normalize our repository structure to simplify the tooling
> requirements. What exactly doesn't work? Trying to release a single thing
> out of a repository containing many things?
>
> > On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
> >> Can we start the process of converting everything to Git. I don't
> really see any benefit in using Subversion any longer.
> >>
> >> If so then we should just get together for a day and convert them and
> then get infra to use what we converted to do the flip.
> >>
> >> Jason (who would be happy to never execute svn again)
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> I never make the mistake of arguing with people for whose opinions I have
> no respect.
>
> -- Edward Gibbon
>
>
>
>
>
>
>
>
>
>
Re: Convert everything to Git
Posted by Stephen Connolly <st...@gmail.com>.
Yep. I release projects every day with git and m-r-p. The only issues I
know of are if you are wanting to release a portion of the repository or a
reactor that does not start at the root of the repository... but I don't do
that and I think it is a stupid thing to do anyway, so not a problem for me
(though I can agree that users may have a valid desire to do the things I
think are stupid... for example lots of users of Jenkins seem to want to
use the evil job type[1])
[1]:
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
On 20 February 2014 22:00, Mark Derricutt <ma...@talios.com> wrote:
> That is easily worked around tho by adding a <dependency> setting for the
> newer -scm- modules.
>
> mark
>
>
> On 21 Feb 2014, at 10:29, Benson Margulies wrote:
>
> The M-R-P has a giant bug such that the current version of it and the
>> current version of git do not work together. I think the bug is
>> particularly severe for multiple releasable projects in one repo, but
>> the details are not sticking in my head.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Convert everything to Git
Posted by Mark Derricutt <ma...@talios.com>.
That is easily worked around tho by adding a <dependency> setting for
the newer -scm- modules.
mark
On 21 Feb 2014, at 10:29, Benson Margulies wrote:
> The M-R-P has a giant bug such that the current version of it and the
> current version of git do not work together. I think the bug is
> particularly severe for multiple releasable projects in one repo, but
> the details are not sticking in my head.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Benson Margulies <bi...@gmail.com>.
On Thu, Feb 20, 2014 at 4:27 PM, Jason van Zyl <ja...@takari.io> wrote:
>
> On Feb 20, 2014, at 1:07 PM, Dennis Lundberg <de...@gmail.com> wrote:
>
>> Hi Jason
>>
>> While I'm finally starting to see the potential with a DVCS like git,
>> there are a couple of things that stands in the way of migrating, for
>> example plugins, to git:
>>
>> 1. Judging by our resident git gurus, it will require quite some
>> effort to prepare for and execute the actual migration. Do we have
>> someone with enough knowledge and time to do it?
>>
>
> I'm willing and I think Kristian would help as well.
>
>> 2. Our own tooling, in particular maven-release-plugin, still isn't
>> good enough for git use. IMO we need to get that fixed and verified on
>> our own releases before we migrate any more components to git.
>>
>
> I only release core and that works fine which begs the question: do we want to normalize our repository structure to simplify the tooling requirements. What exactly doesn't work? Trying to release a single thing out of a repository containing many things?
The M-R-P has a giant bug such that the current version of it and the
current version of git do not work together. I think the bug is
particularly severe for multiple releasable projects in one repo, but
the details are not sticking in my head.
Personally I have grown fond of the jgitflow-maven-plugin, but it has
a bug inventory.
>
>> On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
>>> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>>>
>>> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>>>
>>> Jason (who would be happy to never execute svn again)
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> I never make the mistake of arguing with people for whose opinions I have no respect.
>
> -- Edward Gibbon
>
>
>
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Convert everything to Git
Posted by Jason van Zyl <ja...@takari.io>.
On Feb 20, 2014, at 1:07 PM, Dennis Lundberg <de...@gmail.com> wrote:
> Hi Jason
>
> While I'm finally starting to see the potential with a DVCS like git,
> there are a couple of things that stands in the way of migrating, for
> example plugins, to git:
>
> 1. Judging by our resident git gurus, it will require quite some
> effort to prepare for and execute the actual migration. Do we have
> someone with enough knowledge and time to do it?
>
I'm willing and I think Kristian would help as well.
> 2. Our own tooling, in particular maven-release-plugin, still isn't
> good enough for git use. IMO we need to get that fixed and verified on
> our own releases before we migrate any more components to git.
>
I only release core and that works fine which begs the question: do we want to normalize our repository structure to simplify the tooling requirements. What exactly doesn't work? Trying to release a single thing out of a repository containing many things?
> On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
>> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>>
>> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>>
>> Jason (who would be happy to never execute svn again)
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
I never make the mistake of arguing with people for whose opinions I have no respect.
-- Edward Gibbon
Re: Convert everything to Git
Posted by Igor Fedorenko <ig...@ifedorenko.com>.
Maven Core is in git and has been for quite some time now... or you mean
some other Mave Core?
https://git-wip-us.apache.org/repos/asf?p=maven.git
--
Regards,
Igor
On 2/20/2014, 16:12, Paul Benedict wrote:
> Would it be a good test to first try migrating individual plugin projects
> to GIT before attempting Maven Core?
>
>
> On Thu, Feb 20, 2014 at 3:07 PM, Dennis Lundberg
> <de...@gmail.com>wrote:
>
>> Hi Jason
>>
>> While I'm finally starting to see the potential with a DVCS like git,
>> there are a couple of things that stands in the way of migrating, for
>> example plugins, to git:
>>
>> 1. Judging by our resident git gurus, it will require quite some
>> effort to prepare for and execute the actual migration. Do we have
>> someone with enough knowledge and time to do it?
>>
>> 2. Our own tooling, in particular maven-release-plugin, still isn't
>> good enough for git use. IMO we need to get that fixed and verified on
>> our own releases before we migrate any more components to git.
>>
>> On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
>>> Can we start the process of converting everything to Git. I don't really
>> see any benefit in using Subversion any longer.
>>>
>>> If so then we should just get together for a day and convert them and
>> then get infra to use what we converted to do the flip.
>>>
>>> Jason (who would be happy to never execute svn again)
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> 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: Convert everything to Git
Posted by Paul Benedict <pb...@apache.org>.
Would it be a good test to first try migrating individual plugin projects
to GIT before attempting Maven Core?
On Thu, Feb 20, 2014 at 3:07 PM, Dennis Lundberg
<de...@gmail.com>wrote:
> Hi Jason
>
> While I'm finally starting to see the potential with a DVCS like git,
> there are a couple of things that stands in the way of migrating, for
> example plugins, to git:
>
> 1. Judging by our resident git gurus, it will require quite some
> effort to prepare for and execute the actual migration. Do we have
> someone with enough knowledge and time to do it?
>
> 2. Our own tooling, in particular maven-release-plugin, still isn't
> good enough for git use. IMO we need to get that fixed and verified on
> our own releases before we migrate any more components to git.
>
> On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
> > Can we start the process of converting everything to Git. I don't really
> see any benefit in using Subversion any longer.
> >
> > If so then we should just get together for a day and convert them and
> then get infra to use what we converted to do the flip.
> >
> > Jason (who would be happy to never execute svn again)
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Cheers,
Paul
Re: Convert everything to Git
Posted by Dennis Lundberg <de...@gmail.com>.
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of things that stands in the way of migrating, for
example plugins, to git:
1. Judging by our resident git gurus, it will require quite some
effort to prepare for and execute the actual migration. Do we have
someone with enough knowledge and time to do it?
2. Our own tooling, in particular maven-release-plugin, still isn't
good enough for git use. IMO we need to get that fixed and verified on
our own releases before we migrate any more components to git.
On Thu, Feb 13, 2014 at 4:37 AM, Jason van Zyl <ja...@tesla.io> wrote:
> Can we start the process of converting everything to Git. I don't really see any benefit in using Subversion any longer.
>
> If so then we should just get together for a day and convert them and then get infra to use what we converted to do the flip.
>
> Jason (who would be happy to never execute svn again)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org