Re: [All] New repo for all proper components as submodules?

[Jochen Wiedmann]

On Sun, Aug 30, 2020 at 12:53 AM Gary Gregory  wrote:

> Any thoughts for or against creating a new git repository which would
> contain all 'proper' Commons components as git submodules?
>
> The idea is to be able to checkout all of Commons 'proper' in one go in one
> place.

Sounds to me like a lot of work (fixing remote URL's, or recloning)
with absolutely no recognizable effect. (The use case, you are
describing could be supported just as well with a shell script in
commons-parent, like

if test ! -d proper; then mkdir proper; fi
for f in commons-lang commons-io ...; do
git clone https://gitbox.apache.org/repos/asf/$f.git proper/$f
done

-- 

Look, that's why there's rules, understand? So that you think before
you break 'em.

-- (Terry Pratchett, Thief of Time)

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

Re: [All] New repo for all proper components as submodules?

[Matt Sicker]

I'm only explaining how it could be used. Caveat: I don't use git
submodules or subtrees for anything other than my dot files since that
combines things like vim plugins, zsh plugins, etc.

On Tue, 1 Sep 2020 at 23:52, Xeno Amess  wrote:
>
> > As I said previously, I would avoid using either one.  I really don’t
> know why you would want to with Java. I can understand it with applications
> written in C where you might want to compile all the dependencies along
> with the main application. But that isn’t the case in Java. Introducing
> subtrees or modules just adds complexity you don’t need.
>
> Yep, that is why I prefer some scripts to do that.
> Seems should not depend on git to do such thing...
>
> Ralph Goers  于 2020年9月2日周三 上午10:46写道：
>
> > As I said previously, I would avoid using either one.  I really don’t know
> > why you would want to with Java. I can understand it with applications
> > written in C where you might want to compile all the dependencies along
> > with the main application. But that isn’t the case in Java. Introducing
> > subtrees or modules just adds complexity you don’t need.
> >
> > Ralph
> >
> > > On Sep 1, 2020, at 6:06 AM, Gary Gregory  wrote:
> > >
> > > I found the following helpful but it is from 2016,  so I wonder how much
> > > has changed since then:
> > >
> > > https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/
> > >
> > > Gary
> > >
> > > On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:
> > >
> > >> The use case you're describing is fairly well handled by the git
> > >> subtree command. There are some git plugins that add more complex
> > >> workflows on top of that, but the base command is what you're looking
> > >> for. Git submodules, in my experience, are far more useful when
> > >> pointing to release commits and treating submodule updates like
> > >> dependency updates. If you want the equivalent of how Subversion lets
> > >> you link to another repo as a directory, that would be git-subtree,
> > >> not git-submodule.
> > >>
> > >> On Mon, 31 Aug 2020 at 09:16, Gary Gregory 
> > wrote:
> > >>>
> > >>> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
> > >>> wrote:
> > >>>
> >  On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
> >  wrote:
> > 
> > > I'm talking about girl's own submodules:
> > >
> > > https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > >
> > 
> >  I think the on-line book above has been updated since 2014 (as seen on
> > >> the
> >  front page https://git-scm.com/book/en/v2) so the reference page
> >  https://git-scm.com/docs/git-submodule should be more accurate.
> > 
> > >>> ARG: "I think the on-line book above has been updated" ->  "I think the
> > >>> on-line book above has *NOT *been updated"
> > >>>
> > >>> G
> > >>>
> > >>>
> > 
> >  Gary
> > 
> > 
> > >
> > > https://git-scm.com/docs/git-submodule
> > >
> > > Gary
> > >
> > > On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> > >
> > >> By git submodules, are you talking about a symlink to another git
> > >> repository inside one of our repositories?
> > >>
> > >> -Rob
> > >>
> > >>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> > >> wrote:
> > >>>
> > >>> Hi All,
> > >>>
> > >>> Any thoughts for or against creating a new git repository which
> > >> would
> > >>> contain all 'proper' Commons components as git submodules?
> > >>>
> > >>> The idea is to be able to checkout all of Commons 'proper' in one
> > >> go
> > >> in one
> > >>> place.
> > >>>
> > >>> Gary
> > >>
> > >>
> > >>
> > -
> > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> Matt Sicker 
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>
> > >>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >



-- 
Matt Sicker 

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

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

> As I said previously, I would avoid using either one.  I really don’t
know why you would want to with Java. I can understand it with applications
written in C where you might want to compile all the dependencies along
with the main application. But that isn’t the case in Java. Introducing
subtrees or modules just adds complexity you don’t need.

Yep, that is why I prefer some scripts to do that.
Seems should not depend on git to do such thing...

Ralph Goers  于 2020年9月2日周三 上午10:46写道：

> As I said previously, I would avoid using either one.  I really don’t know
> why you would want to with Java. I can understand it with applications
> written in C where you might want to compile all the dependencies along
> with the main application. But that isn’t the case in Java. Introducing
> subtrees or modules just adds complexity you don’t need.
>
> Ralph
>
> > On Sep 1, 2020, at 6:06 AM, Gary Gregory  wrote:
> >
> > I found the following helpful but it is from 2016,  so I wonder how much
> > has changed since then:
> >
> > https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/
> >
> > Gary
> >
> > On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:
> >
> >> The use case you're describing is fairly well handled by the git
> >> subtree command. There are some git plugins that add more complex
> >> workflows on top of that, but the base command is what you're looking
> >> for. Git submodules, in my experience, are far more useful when
> >> pointing to release commits and treating submodule updates like
> >> dependency updates. If you want the equivalent of how Subversion lets
> >> you link to another repo as a directory, that would be git-subtree,
> >> not git-submodule.
> >>
> >> On Mon, 31 Aug 2020 at 09:16, Gary Gregory 
> wrote:
> >>>
> >>> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
> >>> wrote:
> >>>
>  On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
>  wrote:
> 
> > I'm talking about girl's own submodules:
> >
> > https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >
> 
>  I think the on-line book above has been updated since 2014 (as seen on
> >> the
>  front page https://git-scm.com/book/en/v2) so the reference page
>  https://git-scm.com/docs/git-submodule should be more accurate.
> 
> >>> ARG: "I think the on-line book above has been updated" ->  "I think the
> >>> on-line book above has *NOT *been updated"
> >>>
> >>> G
> >>>
> >>>
> 
>  Gary
> 
> 
> >
> > https://git-scm.com/docs/git-submodule
> >
> > Gary
> >
> > On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> >
> >> By git submodules, are you talking about a symlink to another git
> >> repository inside one of our repositories?
> >>
> >> -Rob
> >>
> >>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> >> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> Any thoughts for or against creating a new git repository which
> >> would
> >>> contain all 'proper' Commons components as git submodules?
> >>>
> >>> The idea is to be able to checkout all of Commons 'proper' in one
> >> go
> >> in one
> >>> place.
> >>>
> >>> Gary
> >>
> >>
> >>
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[Ralph Goers]

Why?

> On Sep 1, 2020, at 8:39 PM, Matt Sicker  wrote:
> 
> It could be useful for grouping inter-dependent modules like pool/dbcp.
> 
> On Tue, Sep 1, 2020 at 21:46 Ralph Goers  wrote:
> 
>> As I said previously, I would avoid using either one.  I really don’t know
>> why you would want to with Java. I can understand it with applications
>> written in C where you might want to compile all the dependencies along
>> with the main application. But that isn’t the case in Java. Introducing
>> subtrees or modules just adds complexity you don’t need.
>> 
>> 
>> 
>> Ralph
>> 
>> 
>> 
>>> On Sep 1, 2020, at 6:06 AM, Gary Gregory  wrote:
>> 
>>> 
>> 
>>> I found the following helpful but it is from 2016,  so I wonder how much
>> 
>>> has changed since then:
>> 
>>> 
>> 
>>> https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/
>> 
>>> 
>> 
>>> Gary
>> 
>>> 
>> 
>>> On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:
>> 
>>> 
>> 
 The use case you're describing is fairly well handled by the git
>> 
 subtree command. There are some git plugins that add more complex
>> 
 workflows on top of that, but the base command is what you're looking
>> 
 for. Git submodules, in my experience, are far more useful when
>> 
 pointing to release commits and treating submodule updates like
>> 
 dependency updates. If you want the equivalent of how Subversion lets
>> 
 you link to another repo as a directory, that would be git-subtree,
>> 
 not git-submodule.
>> 
 
>> 
 On Mon, 31 Aug 2020 at 09:16, Gary Gregory 
>> wrote:
>> 
> 
>> 
> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
>> 
> wrote:
>> 
> 
>> 
>> On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
>> 
>> wrote:
>> 
>> 
>> 
>>> I'm talking about girl's own submodules:
>> 
>>> 
>> 
>>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>> 
>>> 
>> 
>> 
>> 
>> I think the on-line book above has been updated since 2014 (as seen on
>> 
 the
>> 
>> front page https://git-scm.com/book/en/v2) so the reference page
>> 
>> https://git-scm.com/docs/git-submodule should be more accurate.
>> 
>> 
>> 
> ARG: "I think the on-line book above has been updated" ->  "I think the
>> 
> on-line book above has *NOT *been updated"
>> 
> 
>> 
> G
>> 
> 
>> 
> 
>> 
>> 
>> 
>> Gary
>> 
>> 
>> 
>> 
>> 
>>> 
>> 
>>> https://git-scm.com/docs/git-submodule
>> 
>>> 
>> 
>>> Gary
>> 
>>> 
>> 
>>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>> 
>>> 
>> 
 By git submodules, are you talking about a symlink to another git
>> 
 repository inside one of our repositories?
>> 
 
>> 
 -Rob
>> 
 
>> 
> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>> 
 wrote:
>> 
> 
>> 
> Hi All,
>> 
> 
>> 
> Any thoughts for or against creating a new git repository which
>> 
 would
>> 
> contain all 'proper' Commons components as git submodules?
>> 
> 
>> 
> The idea is to be able to checkout all of Commons 'proper' in one
>> 
 go
>> 
 in one
>> 
> place.
>> 
> 
>> 
> Gary
>> 
 
>> 
 
>> 
 
>> -
>> 
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> 
 For additional commands, e-mail: dev-h...@commons.apache.org
>> 
 
>> 
 
>> 
 
>> 
 
>> 
 
>> 
 --
>> 
 Matt Sicker 
>> 
 
>> 
 -
>> 
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> 
 For additional commands, e-mail: dev-h...@commons.apache.org
>> 
 
>> 
 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -
>> 
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> 
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 
>> 
>> --
> Matt Sicker 



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

Re: [All] New repo for all proper components as submodules?

[Matt Sicker]

It could be useful for grouping inter-dependent modules like pool/dbcp.

On Tue, Sep 1, 2020 at 21:46 Ralph Goers  wrote:

> As I said previously, I would avoid using either one.  I really don’t know
> why you would want to with Java. I can understand it with applications
> written in C where you might want to compile all the dependencies along
> with the main application. But that isn’t the case in Java. Introducing
> subtrees or modules just adds complexity you don’t need.
>
>
>
> Ralph
>
>
>
> > On Sep 1, 2020, at 6:06 AM, Gary Gregory  wrote:
>
> >
>
> > I found the following helpful but it is from 2016,  so I wonder how much
>
> > has changed since then:
>
> >
>
> > https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/
>
> >
>
> > Gary
>
> >
>
> > On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:
>
> >
>
> >> The use case you're describing is fairly well handled by the git
>
> >> subtree command. There are some git plugins that add more complex
>
> >> workflows on top of that, but the base command is what you're looking
>
> >> for. Git submodules, in my experience, are far more useful when
>
> >> pointing to release commits and treating submodule updates like
>
> >> dependency updates. If you want the equivalent of how Subversion lets
>
> >> you link to another repo as a directory, that would be git-subtree,
>
> >> not git-submodule.
>
> >>
>
> >> On Mon, 31 Aug 2020 at 09:16, Gary Gregory 
> wrote:
>
> >>>
>
> >>> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
>
> >>> wrote:
>
> >>>
>
>  On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
>
>  wrote:
>
> 
>
> > I'm talking about girl's own submodules:
>
> >
>
> > https://git-scm.com/book/en/v2/Git-Tools-Submodules
>
> >
>
> 
>
>  I think the on-line book above has been updated since 2014 (as seen on
>
> >> the
>
>  front page https://git-scm.com/book/en/v2) so the reference page
>
>  https://git-scm.com/docs/git-submodule should be more accurate.
>
> 
>
> >>> ARG: "I think the on-line book above has been updated" ->  "I think the
>
> >>> on-line book above has *NOT *been updated"
>
> >>>
>
> >>> G
>
> >>>
>
> >>>
>
> 
>
>  Gary
>
> 
>
> 
>
> >
>
> > https://git-scm.com/docs/git-submodule
>
> >
>
> > Gary
>
> >
>
> > On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>
> >
>
> >> By git submodules, are you talking about a symlink to another git
>
> >> repository inside one of our repositories?
>
> >>
>
> >> -Rob
>
> >>
>
> >>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>
> >> wrote:
>
> >>>
>
> >>> Hi All,
>
> >>>
>
> >>> Any thoughts for or against creating a new git repository which
>
> >> would
>
> >>> contain all 'proper' Commons components as git submodules?
>
> >>>
>
> >>> The idea is to be able to checkout all of Commons 'proper' in one
>
> >> go
>
> >> in one
>
> >>> place.
>
> >>>
>
> >>> Gary
>
> >>
>
> >>
>
> >>
> -
>
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> >> For additional commands, e-mail: dev-h...@commons.apache.org
>
> >>
>
> >>
>
> >>
>
> >>
>
> >>
>
> >> --
>
> >> Matt Sicker 
>
> >>
>
> >> -
>
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> >> For additional commands, e-mail: dev-h...@commons.apache.org
>
> >>
>
> >>
>
>
>
>
>
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>
> --
Matt Sicker 

Re: [All] New repo for all proper components as submodules?

[Ralph Goers]

As I said previously, I would avoid using either one.  I really don’t know why 
you would want to with Java. I can understand it with applications written in C 
where you might want to compile all the dependencies along with the main 
application. But that isn’t the case in Java. Introducing subtrees or modules 
just adds complexity you don’t need.

Ralph

> On Sep 1, 2020, at 6:06 AM, Gary Gregory  wrote:
> 
> I found the following helpful but it is from 2016,  so I wonder how much
> has changed since then:
> 
> https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/
> 
> Gary
> 
> On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:
> 
>> The use case you're describing is fairly well handled by the git
>> subtree command. There are some git plugins that add more complex
>> workflows on top of that, but the base command is what you're looking
>> for. Git submodules, in my experience, are far more useful when
>> pointing to release commits and treating submodule updates like
>> dependency updates. If you want the equivalent of how Subversion lets
>> you link to another repo as a directory, that would be git-subtree,
>> not git-submodule.
>> 
>> On Mon, 31 Aug 2020 at 09:16, Gary Gregory  wrote:
>>> 
>>> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
>>> wrote:
>>> 
 On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
 wrote:
 
> I'm talking about girl's own submodules:
> 
> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> 
 
 I think the on-line book above has been updated since 2014 (as seen on
>> the
 front page https://git-scm.com/book/en/v2) so the reference page
 https://git-scm.com/docs/git-submodule should be more accurate.
 
>>> ARG: "I think the on-line book above has been updated" ->  "I think the
>>> on-line book above has *NOT *been updated"
>>> 
>>> G
>>> 
>>> 
 
 Gary
 
 
> 
> https://git-scm.com/docs/git-submodule
> 
> Gary
> 
> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> 
>> By git submodules, are you talking about a symlink to another git
>> repository inside one of our repositories?
>> 
>> -Rob
>> 
>>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>> wrote:
>>> 
>>> Hi All,
>>> 
>>> Any thoughts for or against creating a new git repository which
>> would
>>> contain all 'proper' Commons components as git submodules?
>>> 
>>> The idea is to be able to checkout all of Commons 'proper' in one
>> go
>> in one
>>> place.
>>> 
>>> Gary
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 
>> 
>> 
>> 
>> --
>> Matt Sicker 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 



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

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

I found the following helpful but it is from 2016,  so I wonder how much
has changed since then:

https://martowen.com/2016/05/01/git-submodules-vs-git-subtrees/

Gary

On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:

> The use case you're describing is fairly well handled by the git
> subtree command. There are some git plugins that add more complex
> workflows on top of that, but the base command is what you're looking
> for. Git submodules, in my experience, are far more useful when
> pointing to release commits and treating submodule updates like
> dependency updates. If you want the equivalent of how Subversion lets
> you link to another repo as a directory, that would be git-subtree,
> not git-submodule.
>
> On Mon, 31 Aug 2020 at 09:16, Gary Gregory  wrote:
> >
> > On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
> > wrote:
> >
> > > On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
> > > wrote:
> > >
> > >> I'm talking about girl's own submodules:
> > >>
> > >> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > >>
> > >
> > > I think the on-line book above has been updated since 2014 (as seen on
> the
> > > front page https://git-scm.com/book/en/v2) so the reference page
> > > https://git-scm.com/docs/git-submodule should be more accurate.
> > >
> > ARG: "I think the on-line book above has been updated" ->  "I think the
> > on-line book above has *NOT *been updated"
> >
> > G
> >
> >
> > >
> > > Gary
> > >
> > >
> > >>
> > >> https://git-scm.com/docs/git-submodule
> > >>
> > >> Gary
> > >>
> > >> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> > >>
> > >>> By git submodules, are you talking about a symlink to another git
> > >>> repository inside one of our repositories?
> > >>>
> > >>> -Rob
> > >>>
> > >>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> > >>> wrote:
> > >>> >
> > >>> > Hi All,
> > >>> >
> > >>> > Any thoughts for or against creating a new git repository which
> would
> > >>> > contain all 'proper' Commons components as git submodules?
> > >>> >
> > >>> > The idea is to be able to checkout all of Commons 'proper' in one
> go
> > >>> in one
> > >>> > place.
> > >>> >
> > >>> > Gary
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >>> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>>
> > >>>
>
>
>
> --
> Matt Sicker 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

Thanks for the pointer Matt, I'll explore...

Gary

On Mon, Aug 31, 2020, 10:34 Matt Sicker  wrote:

> The use case you're describing is fairly well handled by the git
> subtree command. There are some git plugins that add more complex
> workflows on top of that, but the base command is what you're looking
> for. Git submodules, in my experience, are far more useful when
> pointing to release commits and treating submodule updates like
> dependency updates. If you want the equivalent of how Subversion lets
> you link to another repo as a directory, that would be git-subtree,
> not git-submodule.
>
> On Mon, 31 Aug 2020 at 09:16, Gary Gregory  wrote:
> >
> > On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
> > wrote:
> >
> > > On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
> > > wrote:
> > >
> > >> I'm talking about girl's own submodules:
> > >>
> > >> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > >>
> > >
> > > I think the on-line book above has been updated since 2014 (as seen on
> the
> > > front page https://git-scm.com/book/en/v2) so the reference page
> > > https://git-scm.com/docs/git-submodule should be more accurate.
> > >
> > ARG: "I think the on-line book above has been updated" ->  "I think the
> > on-line book above has *NOT *been updated"
> >
> > G
> >
> >
> > >
> > > Gary
> > >
> > >
> > >>
> > >> https://git-scm.com/docs/git-submodule
> > >>
> > >> Gary
> > >>
> > >> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> > >>
> > >>> By git submodules, are you talking about a symlink to another git
> > >>> repository inside one of our repositories?
> > >>>
> > >>> -Rob
> > >>>
> > >>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> > >>> wrote:
> > >>> >
> > >>> > Hi All,
> > >>> >
> > >>> > Any thoughts for or against creating a new git repository which
> would
> > >>> > contain all 'proper' Commons components as git submodules?
> > >>> >
> > >>> > The idea is to be able to checkout all of Commons 'proper' in one
> go
> > >>> in one
> > >>> > place.
> > >>> >
> > >>> > Gary
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > >>> For additional commands, e-mail: dev-h...@commons.apache.org
> > >>>
> > >>>
>
>
>
> --
> Matt Sicker 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[sebb]

I have a script which downloads
https://gitbox.apache.org/repositories.json and picks out the commons
repositories.
For each one, there is another script that can check out the component repos.

It's then pretty easy to quickly scan files in all the subdirectories,
e.g. to check on pom settings.

It's not as convenient as it used to be with SVN, but it is workable.

On Mon, 31 Aug 2020 at 17:10, Xeno Amess  wrote:
>
> @Gary Gregory 
> Hi gary.
> Please see https://github.com/XenoAmess/commons-proper
> Especially see the github-actions log.
> Is this the exact function what you are looking for?
> :)
> Right now I only added 3 commons repos into this toolchain, means
> bcel,beanutils,bsf
> And the ci will fail only because bsf will fail build.
> Sorry for the formal wrong reply mailing chain, that is a mistake.
>
> Ralph Goers  于2020年8月31日周一 下午11:29写道：
>
> >
> > > On Aug 31, 2020, at 8:24 AM, Ralph Goers 
> > wrote:
> > >
> > >
> > >
> > >> On Aug 31, 2020, at 7:01 AM, Gary Gregory 
> > wrote:
> > >>
> > >> My target use case here is: I want an easy way to work on all of
> > Commons in
> > >> a new VM or a new machine, so I'd like to be able to check out all of
> > >> Commons in one go from any level for example here is an imaginary git
> > >> submodule tree:
> > >> - Apache Commons, a git repo with submodules:
> > >> - -  Apache Commons Proper, a git repo with submodules:
> > >> - - - Apache Commons Lang
> > >> - - - etc
> > >> - -  Apache Commons Sandbox, a git repo with submodules:
> > >> - - - etc
> > >>
> > >> Right now I am checking out each and every repo one at a time. Yes, we
> > >> could stash OS-specific scripts some place.
> > >>
> > >> I was hoping to start at the Apache Commons Proper level. If I need a
> > >> script to update each submodule to the latest HEAD, then this is less
> > >> elegant but understandable from a git POV.
> > >>
> > >> Maybe there is a git shorthand for this…
> > >>
> > >
> > > I do this at work but we use BitBucket. It has the concept of projects
> > and repos live under projects. So I wrote scripts that use the REST API to
> > determine all the repos under and project and then use the git command to
> > clone them all. Once you have them under a single directory it is easy to
> > write a script to do git pull on all of them to keep them updated. IntelliJ
> > also supports loading them all into a single window.
> > >
> > > I believe Git supports labels or something. I know that the ASF knows
> > that each repo belongs to a specific project so I would be surprised if you
> > couldn’t accomplish something similar to what I have done using that
> > information.
> >
> > The .asf.yaml file that can be placed in every repo allows you to specify
> > repository metadata. See
> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Repositorymetadata
> > <
> > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Repositorymetadata
> > >
> >
> > Ralph
> >
> >

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

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

@Gary Gregory 
Hi gary.
Please see https://github.com/XenoAmess/commons-proper
Especially see the github-actions log.
Is this the exact function what you are looking for?
:)
Right now I only added 3 commons repos into this toolchain, means
bcel,beanutils,bsf
And the ci will fail only because bsf will fail build.
Sorry for the formal wrong reply mailing chain, that is a mistake.

Ralph Goers  于2020年8月31日周一 下午11:29写道：

>
> > On Aug 31, 2020, at 8:24 AM, Ralph Goers 
> wrote:
> >
> >
> >
> >> On Aug 31, 2020, at 7:01 AM, Gary Gregory 
> wrote:
> >>
> >> My target use case here is: I want an easy way to work on all of
> Commons in
> >> a new VM or a new machine, so I'd like to be able to check out all of
> >> Commons in one go from any level for example here is an imaginary git
> >> submodule tree:
> >> - Apache Commons, a git repo with submodules:
> >> - -  Apache Commons Proper, a git repo with submodules:
> >> - - - Apache Commons Lang
> >> - - - etc
> >> - -  Apache Commons Sandbox, a git repo with submodules:
> >> - - - etc
> >>
> >> Right now I am checking out each and every repo one at a time. Yes, we
> >> could stash OS-specific scripts some place.
> >>
> >> I was hoping to start at the Apache Commons Proper level. If I need a
> >> script to update each submodule to the latest HEAD, then this is less
> >> elegant but understandable from a git POV.
> >>
> >> Maybe there is a git shorthand for this…
> >>
> >
> > I do this at work but we use BitBucket. It has the concept of projects
> and repos live under projects. So I wrote scripts that use the REST API to
> determine all the repos under and project and then use the git command to
> clone them all. Once you have them under a single directory it is easy to
> write a script to do git pull on all of them to keep them updated. IntelliJ
> also supports loading them all into a single window.
> >
> > I believe Git supports labels or something. I know that the ASF knows
> that each repo belongs to a specific project so I would be surprised if you
> couldn’t accomplish something similar to what I have done using that
> information.
>
> The .asf.yaml file that can be placed in every repo allows you to specify
> repository metadata. See
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Repositorymetadata
> <
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Repositorymetadata
> >
>
> Ralph
>
>

Re: [All] New repo for all proper components as submodules?

[Ralph Goers]

> On Aug 31, 2020, at 8:24 AM, Ralph Goers  wrote:
> 
> 
> 
>> On Aug 31, 2020, at 7:01 AM, Gary Gregory  wrote:
>> 
>> My target use case here is: I want an easy way to work on all of Commons in
>> a new VM or a new machine, so I'd like to be able to check out all of
>> Commons in one go from any level for example here is an imaginary git
>> submodule tree:
>> - Apache Commons, a git repo with submodules:
>> - -  Apache Commons Proper, a git repo with submodules:
>> - - - Apache Commons Lang
>> - - - etc
>> - -  Apache Commons Sandbox, a git repo with submodules:
>> - - - etc
>> 
>> Right now I am checking out each and every repo one at a time. Yes, we
>> could stash OS-specific scripts some place.
>> 
>> I was hoping to start at the Apache Commons Proper level. If I need a
>> script to update each submodule to the latest HEAD, then this is less
>> elegant but understandable from a git POV.
>> 
>> Maybe there is a git shorthand for this…
>> 
> 
> I do this at work but we use BitBucket. It has the concept of projects and 
> repos live under projects. So I wrote scripts that use the REST API to 
> determine all the repos under and project and then use the git command to 
> clone them all. Once you have them under a single directory it is easy to 
> write a script to do git pull on all of them to keep them updated. IntelliJ 
> also supports loading them all into a single window.
> 
> I believe Git supports labels or something. I know that the ASF knows that 
> each repo belongs to a specific project so I would be surprised if you 
> couldn’t accomplish something similar to what I have done using that 
> information.

The .asf.yaml file that can be placed in every repo allows you to specify 
repository metadata. See 
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#git.asf.yamlfeatures-Repositorymetadata
 


Ralph

Re: [All] New repo for all proper components as submodules?

[Ralph Goers]

> On Aug 31, 2020, at 7:01 AM, Gary Gregory  wrote:
> 
> My target use case here is: I want an easy way to work on all of Commons in
> a new VM or a new machine, so I'd like to be able to check out all of
> Commons in one go from any level for example here is an imaginary git
> submodule tree:
> - Apache Commons, a git repo with submodules:
> - -  Apache Commons Proper, a git repo with submodules:
> - - - Apache Commons Lang
> - - - etc
> - -  Apache Commons Sandbox, a git repo with submodules:
> - - - etc
> 
> Right now I am checking out each and every repo one at a time. Yes, we
> could stash OS-specific scripts some place.
> 
> I was hoping to start at the Apache Commons Proper level. If I need a
> script to update each submodule to the latest HEAD, then this is less
> elegant but understandable from a git POV.
> 
> Maybe there is a git shorthand for this…
> 

I do this at work but we use BitBucket. It has the concept of projects and 
repos live under projects. So I wrote scripts that use the REST API to 
determine all the repos under and project and then use the git command to clone 
them all. Once you have them under a single directory it is easy to write a 
script to do git pull on all of them to keep them updated. IntelliJ also 
supports loading them all into a single window.

I believe Git supports labels or something. I know that the ASF knows that each 
repo belongs to a specific project so I would be surprised if you couldn’t 
accomplish something similar to what I have done using that information.

Ralph

Re: [All] New repo for all proper components as submodules?

[Matt Sicker]

The use case you're describing is fairly well handled by the git
subtree command. There are some git plugins that add more complex
workflows on top of that, but the base command is what you're looking
for. Git submodules, in my experience, are far more useful when
pointing to release commits and treating submodule updates like
dependency updates. If you want the equivalent of how Subversion lets
you link to another repo as a directory, that would be git-subtree,
not git-submodule.

On Mon, 31 Aug 2020 at 09:16, Gary Gregory  wrote:
>
> On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
> wrote:
>
> > On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
> > wrote:
> >
> >> I'm talking about girl's own submodules:
> >>
> >> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >>
> >
> > I think the on-line book above has been updated since 2014 (as seen on the
> > front page https://git-scm.com/book/en/v2) so the reference page
> > https://git-scm.com/docs/git-submodule should be more accurate.
> >
> ARG: "I think the on-line book above has been updated" ->  "I think the
> on-line book above has *NOT *been updated"
>
> G
>
>
> >
> > Gary
> >
> >
> >>
> >> https://git-scm.com/docs/git-submodule
> >>
> >> Gary
> >>
> >> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> >>
> >>> By git submodules, are you talking about a symlink to another git
> >>> repository inside one of our repositories?
> >>>
> >>> -Rob
> >>>
> >>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> >>> wrote:
> >>> >
> >>> > Hi All,
> >>> >
> >>> > Any thoughts for or against creating a new git repository which would
> >>> > contain all 'proper' Commons components as git submodules?
> >>> >
> >>> > The idea is to be able to checkout all of Commons 'proper' in one go
> >>> in one
> >>> > place.
> >>> >
> >>> > Gary
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>> For additional commands, e-mail: dev-h...@commons.apache.org
> >>>
> >>>



-- 
Matt Sicker 

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

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Mon, Aug 31, 2020 at 10:15 AM Gary Gregory 
wrote:

> On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory 
> wrote:
>
>> I'm talking about girl's own submodules:
>>
>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>>
>
> I think the on-line book above has been updated since 2014 (as seen on the
> front page https://git-scm.com/book/en/v2) so the reference page
> https://git-scm.com/docs/git-submodule should be more accurate.
>
ARG: "I think the on-line book above has been updated" ->  "I think the
on-line book above has *NOT *been updated"

G


>
> Gary
>
>
>>
>> https://git-scm.com/docs/git-submodule
>>
>> Gary
>>
>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>>
>>> By git submodules, are you talking about a symlink to another git
>>> repository inside one of our repositories?
>>>
>>> -Rob
>>>
>>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>>> wrote:
>>> >
>>> > Hi All,
>>> >
>>> > Any thoughts for or against creating a new git repository which would
>>> > contain all 'proper' Commons components as git submodules?
>>> >
>>> > The idea is to be able to checkout all of Commons 'proper' in one go
>>> in one
>>> > place.
>>> >
>>> > Gary
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Sun, Aug 30, 2020 at 9:24 AM Gary Gregory  wrote:

> I'm talking about girl's own submodules:
>
> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>

I think the on-line book above has been updated since 2014 (as seen on the
front page https://git-scm.com/book/en/v2) so the reference page
https://git-scm.com/docs/git-submodule should be more accurate.

Gary


>
> https://git-scm.com/docs/git-submodule
>
> Gary
>
> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>
>> By git submodules, are you talking about a symlink to another git
>> repository inside one of our repositories?
>>
>> -Rob
>>
>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>> wrote:
>> >
>> > Hi All,
>> >
>> > Any thoughts for or against creating a new git repository which would
>> > contain all 'proper' Commons components as git submodules?
>> >
>> > The idea is to be able to checkout all of Commons 'proper' in one go in
>> one
>> > place.
>> >
>> > Gary
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

I'll try if I can solve your goal using maven-plugin tonight.
If I succeed I will let you know :)

Xeno Amess  于2020年8月31日周一 下午10:06写道：

> > Right now I am checking out each and every repo one at a time. Yes, we
> > could stash OS-specific scripts some place.
> >
> > I was hoping to start at the Apache Commons Proper level. If I need a
> > script to update each submodule to the latest HEAD, then this is less
> > elegant but understandable from a git POV.
> >
> > Maybe there is a git shorthand for this...
>
> Sounds like a maven-plugin is better for doing this...
>
>
> Gary Gregory  于2020年8月31日周一 下午10:03写道：
>
>> On Mon, Aug 31, 2020 at 9:59 AM Xeno Amess  wrote:
>>
>> > BTW.
>> > From my own view, we might need a testing maven project (or a github
>> repo),
>> > for ensuring all commons repos can be used together, free of dependency
>> > hell, or other internal errors about using different versions of a same
>> > dependency.
>> >
>>
>> This is not my goal at all here. If that's a goal for you, please see
>> https://gump.apache.org/
>>
>> Gary
>>
>>
>> > But I admit that will really be a time-costing work, and be really hard.
>> > I don't know if we can achieve it by adding the "proper" repo and add a
>> > module pom at base folder, and adding some tests...
>> > Just, I think it useful.
>> >
>> >
>> > John Patrick  于2020年8月31日周一 下午9:51写道：
>> >
>> > > On Mon, 31 Aug 2020 at 14:16, Gary Gregory 
>> > wrote:
>> > > >
>> > > > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker 
>> wrote:
>> > > >
>> > > > > Git submodules are pointers to other git commits. Therefore, any
>> > > component
>> > > > > changes made don’t affect the mono repo until you update said mono
>> > > repo to
>> > > > > point to the new commit. If you do this to point at the latest
>> > release
>> > > > > tags, this makes for less updates. Otherwise, you’ll want to
>> figure
>> > > out a
>> > > > > CI system for automatically updating submodules to the latest
>> master
>> > > > > commits as they pass CI.
>> > > > >
>> > > >
>> > > > Can that commit be HEAD?
>> > >
>> > > Used git submodules loads 2010-2015, and not much since. But from
>> > > memory it can't be HEAD it has to be a specific commit hash.
>> > >
>> > > We had loads of issues when people worked on the sub modules
>> > > independently, it was easier when every worked with the parent git
>> > > module. But that was early 2010's so it might now allow HEAD or a
>> > > named branch say develop or master/main.
>> > >
>> > > We also had loads of maven warnings because we had a wrapper project
>> > > so from the git parent module it saw the submodules as maven modules.
>> > > But the git parent module maven pom wasn't the parent pom of the git
>> > > submodules maven pom. As parent automatically is
>> > > ../pom.xml
>> > >
>> > > Our setup was;
>> > >
>> > > git-module
>> > > -> pom.xml (GAV project:maven-wrapper:1)
>> > > -> git-submodule-parent
>> > > --> pom.xml (GAV project:parent:1)
>> > > -> git-submodule-core
>> > > --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
>> > > correct relative path is ../git-submodule-parent/poml.xml
>> > >
>> > > They had ~35 git submodules, not sure if they are still using
>> submodules.
>> > >
>> > > So it can be useful if you want to have component based git repo's but
>> > > it does add an extra overhead layer of maintenance and everyone needs
>> > > to be onboard from experience.
>> > >
>> > > John
>> > >
>> > > >
>> > > > Gary
>> > > >
>> > > >
>> > > > >
>> > > > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
>> > > > >
>> > > > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory <
>> garydgreg...@gmail.com
>> > >
>> > > > > wrote:
>> > > > > >
>> > > > > > >
>> > > > > >
>> > > > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins <
>> chtom...@gmail.com
>> > >
>> > > > > wrote:
>> > > > > >
>> > > > > > >
>> > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > > > > > On Aug 30, 2020, at 9:44 AM, sebb 
>> wrote:
>> > > > > >
>> > > > > > > > >
>> > > > > >
>> > > > > > > > > Some questions:
>> > > > > >
>> > > > > > > > >
>> > > > > >
>> > > > > > > > > - does it affect any existing usage?
>> > > > > >
>> > > > > > > > >  i.e. can people continue to use the individual repos
>> exactly
>> > > as
>> > > > > > before
>> > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > > > > no they can’t
>> > > > > >
>> > > > > > > >
>> > > > > >
>> > > > > > >
>> > > > > >
>> > > > > > > Yes they can... this would be a new repo, and changes nothing
>> for
>> > > > > current
>> > > > > >
>> > > > > > > usage. This does not affect existing repos.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > What about my other queries?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > - changes to commit messages:
>> > > > > >
>> > > > > >  can people commit to components directly from the new repo?
>> > > > > >
>> > > > > > If so, does that change the commit messages?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > - maintenance of the 

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

> Right now I am checking out each and every repo one at a time. Yes, we
> could stash OS-specific scripts some place.
>
> I was hoping to start at the Apache Commons Proper level. If I need a
> script to update each submodule to the latest HEAD, then this is less
> elegant but understandable from a git POV.
>
> Maybe there is a git shorthand for this...

Sounds like a maven-plugin is better for doing this...


Gary Gregory  于2020年8月31日周一 下午10:03写道：

> On Mon, Aug 31, 2020 at 9:59 AM Xeno Amess  wrote:
>
> > BTW.
> > From my own view, we might need a testing maven project (or a github
> repo),
> > for ensuring all commons repos can be used together, free of dependency
> > hell, or other internal errors about using different versions of a same
> > dependency.
> >
>
> This is not my goal at all here. If that's a goal for you, please see
> https://gump.apache.org/
>
> Gary
>
>
> > But I admit that will really be a time-costing work, and be really hard.
> > I don't know if we can achieve it by adding the "proper" repo and add a
> > module pom at base folder, and adding some tests...
> > Just, I think it useful.
> >
> >
> > John Patrick  于2020年8月31日周一 下午9:51写道：
> >
> > > On Mon, 31 Aug 2020 at 14:16, Gary Gregory 
> > wrote:
> > > >
> > > > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker 
> wrote:
> > > >
> > > > > Git submodules are pointers to other git commits. Therefore, any
> > > component
> > > > > changes made don’t affect the mono repo until you update said mono
> > > repo to
> > > > > point to the new commit. If you do this to point at the latest
> > release
> > > > > tags, this makes for less updates. Otherwise, you’ll want to figure
> > > out a
> > > > > CI system for automatically updating submodules to the latest
> master
> > > > > commits as they pass CI.
> > > > >
> > > >
> > > > Can that commit be HEAD?
> > >
> > > Used git submodules loads 2010-2015, and not much since. But from
> > > memory it can't be HEAD it has to be a specific commit hash.
> > >
> > > We had loads of issues when people worked on the sub modules
> > > independently, it was easier when every worked with the parent git
> > > module. But that was early 2010's so it might now allow HEAD or a
> > > named branch say develop or master/main.
> > >
> > > We also had loads of maven warnings because we had a wrapper project
> > > so from the git parent module it saw the submodules as maven modules.
> > > But the git parent module maven pom wasn't the parent pom of the git
> > > submodules maven pom. As parent automatically is
> > > ../pom.xml
> > >
> > > Our setup was;
> > >
> > > git-module
> > > -> pom.xml (GAV project:maven-wrapper:1)
> > > -> git-submodule-parent
> > > --> pom.xml (GAV project:parent:1)
> > > -> git-submodule-core
> > > --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
> > > correct relative path is ../git-submodule-parent/poml.xml
> > >
> > > They had ~35 git submodules, not sure if they are still using
> submodules.
> > >
> > > So it can be useful if you want to have component based git repo's but
> > > it does add an extra overhead layer of maintenance and everyone needs
> > > to be onboard from experience.
> > >
> > > John
> > >
> > > >
> > > > Gary
> > > >
> > > >
> > > > >
> > > > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> > > > >
> > > > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory <
> garydgreg...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > >
> > > > > >
> > > > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins <
> chtom...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > >
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > > > > On Aug 30, 2020, at 9:44 AM, sebb 
> wrote:
> > > > > >
> > > > > > > > >
> > > > > >
> > > > > > > > > Some questions:
> > > > > >
> > > > > > > > >
> > > > > >
> > > > > > > > > - does it affect any existing usage?
> > > > > >
> > > > > > > > >  i.e. can people continue to use the individual repos
> exactly
> > > as
> > > > > > before
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > > > no they can’t
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > >
> > > > > >
> > > > > > > Yes they can... this would be a new repo, and changes nothing
> for
> > > > > current
> > > > > >
> > > > > > > usage. This does not affect existing repos.
> > > > > >
> > > > > >
> > > > > >
> > > > > > What about my other queries?
> > > > > >
> > > > > >
> > > > > >
> > > > > > - changes to commit messages:
> > > > > >
> > > > > >  can people commit to components directly from the new repo?
> > > > > >
> > > > > > If so, does that change the commit messages?
> > > > > >
> > > > > >
> > > > > >
> > > > > > - maintenance of the new repo:
> > > > > >
> > > > > > what is involved, and how will the project know when updates are
> > > needed?
> > > > > >
> > > > > >
> > > > > >
> > > > > > > Gary
> > > > > >
> > > > > > >
> > > > > >
> > > > > > > >
> > > > > >
> > > > > > > > >
> > > > > >
> > > > > > > > > - does it affect Git emails 

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Mon, Aug 31, 2020 at 9:59 AM Xeno Amess  wrote:

> BTW.
> From my own view, we might need a testing maven project (or a github repo),
> for ensuring all commons repos can be used together, free of dependency
> hell, or other internal errors about using different versions of a same
> dependency.
>

This is not my goal at all here. If that's a goal for you, please see
https://gump.apache.org/

Gary


> But I admit that will really be a time-costing work, and be really hard.
> I don't know if we can achieve it by adding the "proper" repo and add a
> module pom at base folder, and adding some tests...
> Just, I think it useful.
>
>
> John Patrick  于2020年8月31日周一 下午9:51写道：
>
> > On Mon, 31 Aug 2020 at 14:16, Gary Gregory 
> wrote:
> > >
> > > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
> > >
> > > > Git submodules are pointers to other git commits. Therefore, any
> > component
> > > > changes made don’t affect the mono repo until you update said mono
> > repo to
> > > > point to the new commit. If you do this to point at the latest
> release
> > > > tags, this makes for less updates. Otherwise, you’ll want to figure
> > out a
> > > > CI system for automatically updating submodules to the latest master
> > > > commits as they pass CI.
> > > >
> > >
> > > Can that commit be HEAD?
> >
> > Used git submodules loads 2010-2015, and not much since. But from
> > memory it can't be HEAD it has to be a specific commit hash.
> >
> > We had loads of issues when people worked on the sub modules
> > independently, it was easier when every worked with the parent git
> > module. But that was early 2010's so it might now allow HEAD or a
> > named branch say develop or master/main.
> >
> > We also had loads of maven warnings because we had a wrapper project
> > so from the git parent module it saw the submodules as maven modules.
> > But the git parent module maven pom wasn't the parent pom of the git
> > submodules maven pom. As parent automatically is
> > ../pom.xml
> >
> > Our setup was;
> >
> > git-module
> > -> pom.xml (GAV project:maven-wrapper:1)
> > -> git-submodule-parent
> > --> pom.xml (GAV project:parent:1)
> > -> git-submodule-core
> > --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
> > correct relative path is ../git-submodule-parent/poml.xml
> >
> > They had ~35 git submodules, not sure if they are still using submodules.
> >
> > So it can be useful if you want to have component based git repo's but
> > it does add an extra overhead layer of maintenance and everyone needs
> > to be onboard from experience.
> >
> > John
> >
> > >
> > > Gary
> > >
> > >
> > > >
> > > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> > > >
> > > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory  >
> > > > wrote:
> > > > >
> > > > > >
> > > > >
> > > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  >
> > > > wrote:
> > > > >
> > > > > >
> > > > >
> > > > > > >
> > > > >
> > > > > > >
> > > > >
> > > > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > Some questions:
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > - does it affect any existing usage?
> > > > >
> > > > > > > >  i.e. can people continue to use the individual repos exactly
> > as
> > > > > before
> > > > >
> > > > > > >
> > > > >
> > > > > > > no they can’t
> > > > >
> > > > > > >
> > > > >
> > > > > >
> > > > >
> > > > > > Yes they can... this would be a new repo, and changes nothing for
> > > > current
> > > > >
> > > > > > usage. This does not affect existing repos.
> > > > >
> > > > >
> > > > >
> > > > > What about my other queries?
> > > > >
> > > > >
> > > > >
> > > > > - changes to commit messages:
> > > > >
> > > > >  can people commit to components directly from the new repo?
> > > > >
> > > > > If so, does that change the commit messages?
> > > > >
> > > > >
> > > > >
> > > > > - maintenance of the new repo:
> > > > >
> > > > > what is involved, and how will the project know when updates are
> > needed?
> > > > >
> > > > >
> > > > >
> > > > > > Gary
> > > > >
> > > > > >
> > > > >
> > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > - does it affect Git emails in any way?
> > > > >
> > > > > > > >  e.g. do they have different text?
> > > > >
> > > > > > >
> > > > >
> > > > > > > same emails
> > > > >
> > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > - will it need much maintenance?
> > > > >
> > > > > > > > If so, how do we know when it needs updating?
> > > > >
> > > > > > >
> > > > >
> > > > > > > more maintainance, have to maintain a git hash at a symlink
> > pointing
> > > > > to an
> > > > >
> > > > > > > external repository
> > > > >
> > > > > > >
> > > > >
> > > > > > > -Rob
> > > > >
> > > > > > >
> > > > >
> > > > > > > >
> > > > >
> > > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory <
> > garydgreg...@gmail.com
> > > > >
> > > > >
> > > > > > > wrote:
> > > > >
> > > > > > > >>
> > > > >
> > > > > > > >> Yes yes "girl" -> "git"
> > > > >

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Mon, Aug 31, 2020 at 9:51 AM John Patrick  wrote:

> On Mon, 31 Aug 2020 at 14:16, Gary Gregory  wrote:
> >
> > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
> >
> > > Git submodules are pointers to other git commits. Therefore, any
> component
> > > changes made don’t affect the mono repo until you update said mono
> repo to
> > > point to the new commit. If you do this to point at the latest release
> > > tags, this makes for less updates. Otherwise, you’ll want to figure
> out a
> > > CI system for automatically updating submodules to the latest master
> > > commits as they pass CI.
> > >
> >
> > Can that commit be HEAD?
>
> Used git submodules loads 2010-2015, and not much since. But from
> memory it can't be HEAD it has to be a specific commit hash.


> We had loads of issues when people worked on the sub modules
> independently, it was easier when every worked with the parent git
> module. But that was early 2010's so it might now allow HEAD or a
> named branch say develop or master/main.
>
> We also had loads of maven warnings because we had a wrapper project
> so from the git parent module it saw the submodules as maven modules.
> But the git parent module maven pom wasn't the parent pom of the git
> submodules maven pom. As parent automatically is
> ../pom.xml
>
> Our setup was;
>
> git-module
> -> pom.xml (GAV project:maven-wrapper:1)
> -> git-submodule-parent
> --> pom.xml (GAV project:parent:1)
> -> git-submodule-core
> --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
> correct relative path is ../git-submodule-parent/poml.xml
>
> They had ~35 git submodules, not sure if they are still using submodules.
>
> So it can be useful if you want to have component based git repo's but
> it does add an extra overhead layer of maintenance and everyone needs
> to be onboard from experience.
>

My target use case here is: I want an easy way to work on all of Commons in
a new VM or a new machine, so I'd like to be able to check out all of
Commons in one go from any level for example here is an imaginary git
submodule tree:
- Apache Commons, a git repo with submodules:
- -  Apache Commons Proper, a git repo with submodules:
- - - Apache Commons Lang
- - - etc
- -  Apache Commons Sandbox, a git repo with submodules:
- - - etc

Right now I am checking out each and every repo one at a time. Yes, we
could stash OS-specific scripts some place.

I was hoping to start at the Apache Commons Proper level. If I need a
script to update each submodule to the latest HEAD, then this is less
elegant but understandable from a git POV.

Maybe there is a git shorthand for this...

Gary



>
> John
>
> >
> > Gary
> >
> >
> > >
> > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> > >
> > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > >
> > > >
> > > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > > >
> > > > > > >
> > > >
> > > > > > > Some questions:
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect any existing usage?
> > > >
> > > > > > >  i.e. can people continue to use the individual repos exactly
> as
> > > > before
> > > >
> > > > > >
> > > >
> > > > > > no they can’t
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > > > Yes they can... this would be a new repo, and changes nothing for
> > > current
> > > >
> > > > > usage. This does not affect existing repos.
> > > >
> > > >
> > > >
> > > > What about my other queries?
> > > >
> > > >
> > > >
> > > > - changes to commit messages:
> > > >
> > > >  can people commit to components directly from the new repo?
> > > >
> > > > If so, does that change the commit messages?
> > > >
> > > >
> > > >
> > > > - maintenance of the new repo:
> > > >
> > > > what is involved, and how will the project know when updates are
> needed?
> > > >
> > > >
> > > >
> > > > > Gary
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect Git emails in any way?
> > > >
> > > > > > >  e.g. do they have different text?
> > > >
> > > > > >
> > > >
> > > > > > same emails
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - will it need much maintenance?
> > > >
> > > > > > > If so, how do we know when it needs updating?
> > > >
> > > > > >
> > > >
> > > > > > more maintainance, have to maintain a git hash at a symlink
> pointing
> > > > to an
> > > >
> > > > > > external repository
> > > >
> > > > > >
> > > >
> > > > > > -Rob
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory <
> garydgreg...@gmail.com
> > > >
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > >> Yes yes "girl" -> "git"
> > > >
> > > > > > >>
> > > >
> > > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory <
> garydgreg...@gmail.com>
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > 

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

As example for dependency-hell, slf4j 1 and 2 use same namespace, means if
some dependency use slf4j1 and another use slf4j2, some really disgusting
thing will happen.
I suffered from that, once.

Xeno Amess  于2020年8月31日周一 下午9:59写道：

> BTW.
> From my own view, we might need a testing maven project (or a github
> repo), for ensuring all commons repos can be used together, free of
> dependency hell, or other internal errors about using different versions of
> a same dependency.
> But I admit that will really be a time-costing work, and be really hard.
> I don't know if we can achieve it by adding the "proper" repo and add a
> module pom at base folder, and adding some tests...
> Just, I think it useful.
>
>
> John Patrick  于2020年8月31日周一 下午9:51写道：
>
>> On Mon, 31 Aug 2020 at 14:16, Gary Gregory 
>> wrote:
>> >
>> > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
>> >
>> > > Git submodules are pointers to other git commits. Therefore, any
>> component
>> > > changes made don’t affect the mono repo until you update said mono
>> repo to
>> > > point to the new commit. If you do this to point at the latest release
>> > > tags, this makes for less updates. Otherwise, you’ll want to figure
>> out a
>> > > CI system for automatically updating submodules to the latest master
>> > > commits as they pass CI.
>> > >
>> >
>> > Can that commit be HEAD?
>>
>> Used git submodules loads 2010-2015, and not much since. But from
>> memory it can't be HEAD it has to be a specific commit hash.
>>
>> We had loads of issues when people worked on the sub modules
>> independently, it was easier when every worked with the parent git
>> module. But that was early 2010's so it might now allow HEAD or a
>> named branch say develop or master/main.
>>
>> We also had loads of maven warnings because we had a wrapper project
>> so from the git parent module it saw the submodules as maven modules.
>> But the git parent module maven pom wasn't the parent pom of the git
>> submodules maven pom. As parent automatically is
>> ../pom.xml
>>
>> Our setup was;
>>
>> git-module
>> -> pom.xml (GAV project:maven-wrapper:1)
>> -> git-submodule-parent
>> --> pom.xml (GAV project:parent:1)
>> -> git-submodule-core
>> --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
>> correct relative path is ../git-submodule-parent/poml.xml
>>
>> They had ~35 git submodules, not sure if they are still using submodules.
>>
>> So it can be useful if you want to have component based git repo's but
>> it does add an extra overhead layer of maintenance and everyone needs
>> to be onboard from experience.
>>
>> John
>>
>> >
>> > Gary
>> >
>> >
>> > >
>> > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
>> > >
>> > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
>> > > wrote:
>> > > >
>> > > > >
>> > > >
>> > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
>> > > wrote:
>> > > >
>> > > > >
>> > > >
>> > > > > >
>> > > >
>> > > > > >
>> > > >
>> > > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
>> > > >
>> > > > > > >
>> > > >
>> > > > > > > Some questions:
>> > > >
>> > > > > > >
>> > > >
>> > > > > > > - does it affect any existing usage?
>> > > >
>> > > > > > >  i.e. can people continue to use the individual repos exactly
>> as
>> > > > before
>> > > >
>> > > > > >
>> > > >
>> > > > > > no they can’t
>> > > >
>> > > > > >
>> > > >
>> > > > >
>> > > >
>> > > > > Yes they can... this would be a new repo, and changes nothing for
>> > > current
>> > > >
>> > > > > usage. This does not affect existing repos.
>> > > >
>> > > >
>> > > >
>> > > > What about my other queries?
>> > > >
>> > > >
>> > > >
>> > > > - changes to commit messages:
>> > > >
>> > > >  can people commit to components directly from the new repo?
>> > > >
>> > > > If so, does that change the commit messages?
>> > > >
>> > > >
>> > > >
>> > > > - maintenance of the new repo:
>> > > >
>> > > > what is involved, and how will the project know when updates are
>> needed?
>> > > >
>> > > >
>> > > >
>> > > > > Gary
>> > > >
>> > > > >
>> > > >
>> > > > > >
>> > > >
>> > > > > > >
>> > > >
>> > > > > > > - does it affect Git emails in any way?
>> > > >
>> > > > > > >  e.g. do they have different text?
>> > > >
>> > > > > >
>> > > >
>> > > > > > same emails
>> > > >
>> > > > > >
>> > > >
>> > > > > > >
>> > > >
>> > > > > > > - will it need much maintenance?
>> > > >
>> > > > > > > If so, how do we know when it needs updating?
>> > > >
>> > > > > >
>> > > >
>> > > > > > more maintainance, have to maintain a git hash at a symlink
>> pointing
>> > > > to an
>> > > >
>> > > > > > external repository
>> > > >
>> > > > > >
>> > > >
>> > > > > > -Rob
>> > > >
>> > > > > >
>> > > >
>> > > > > > >
>> > > >
>> > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory <
>> garydgreg...@gmail.com
>> > > >
>> > > >
>> > > > > > wrote:
>> > > >
>> > > > > > >>
>> > > >
>> > > > > > >> Yes yes "girl" -> "git"
>> > > >
>> > > > > > >>
>> > > >
>> > > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory <
>> 

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

BTW.
>From my own view, we might need a testing maven project (or a github repo),
for ensuring all commons repos can be used together, free of dependency
hell, or other internal errors about using different versions of a same
dependency.
But I admit that will really be a time-costing work, and be really hard.
I don't know if we can achieve it by adding the "proper" repo and add a
module pom at base folder, and adding some tests...
Just, I think it useful.


John Patrick  于2020年8月31日周一 下午9:51写道：

> On Mon, 31 Aug 2020 at 14:16, Gary Gregory  wrote:
> >
> > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
> >
> > > Git submodules are pointers to other git commits. Therefore, any
> component
> > > changes made don’t affect the mono repo until you update said mono
> repo to
> > > point to the new commit. If you do this to point at the latest release
> > > tags, this makes for less updates. Otherwise, you’ll want to figure
> out a
> > > CI system for automatically updating submodules to the latest master
> > > commits as they pass CI.
> > >
> >
> > Can that commit be HEAD?
>
> Used git submodules loads 2010-2015, and not much since. But from
> memory it can't be HEAD it has to be a specific commit hash.
>
> We had loads of issues when people worked on the sub modules
> independently, it was easier when every worked with the parent git
> module. But that was early 2010's so it might now allow HEAD or a
> named branch say develop or master/main.
>
> We also had loads of maven warnings because we had a wrapper project
> so from the git parent module it saw the submodules as maven modules.
> But the git parent module maven pom wasn't the parent pom of the git
> submodules maven pom. As parent automatically is
> ../pom.xml
>
> Our setup was;
>
> git-module
> -> pom.xml (GAV project:maven-wrapper:1)
> -> git-submodule-parent
> --> pom.xml (GAV project:parent:1)
> -> git-submodule-core
> --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
> correct relative path is ../git-submodule-parent/poml.xml
>
> They had ~35 git submodules, not sure if they are still using submodules.
>
> So it can be useful if you want to have component based git repo's but
> it does add an extra overhead layer of maintenance and everyone needs
> to be onboard from experience.
>
> John
>
> >
> > Gary
> >
> >
> > >
> > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> > >
> > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > >
> > > >
> > > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > > >
> > > > > > >
> > > >
> > > > > > > Some questions:
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect any existing usage?
> > > >
> > > > > > >  i.e. can people continue to use the individual repos exactly
> as
> > > > before
> > > >
> > > > > >
> > > >
> > > > > > no they can’t
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > > > Yes they can... this would be a new repo, and changes nothing for
> > > current
> > > >
> > > > > usage. This does not affect existing repos.
> > > >
> > > >
> > > >
> > > > What about my other queries?
> > > >
> > > >
> > > >
> > > > - changes to commit messages:
> > > >
> > > >  can people commit to components directly from the new repo?
> > > >
> > > > If so, does that change the commit messages?
> > > >
> > > >
> > > >
> > > > - maintenance of the new repo:
> > > >
> > > > what is involved, and how will the project know when updates are
> needed?
> > > >
> > > >
> > > >
> > > > > Gary
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect Git emails in any way?
> > > >
> > > > > > >  e.g. do they have different text?
> > > >
> > > > > >
> > > >
> > > > > > same emails
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - will it need much maintenance?
> > > >
> > > > > > > If so, how do we know when it needs updating?
> > > >
> > > > > >
> > > >
> > > > > > more maintainance, have to maintain a git hash at a symlink
> pointing
> > > > to an
> > > >
> > > > > > external repository
> > > >
> > > > > >
> > > >
> > > > > > -Rob
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory <
> garydgreg...@gmail.com
> > > >
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > >> Yes yes "girl" -> "git"
> > > >
> > > > > > >>
> > > >
> > > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory <
> garydgreg...@gmail.com>
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > >>> I'm talking about girl's own submodules:
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> https://git-scm.com/docs/git-submodule
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> Gary
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> On Sun, Aug 

Re: [All] New repo for all proper components as submodules?

[Matt Sicker]

If you want to point to something less specific than a commit, take a
look at git subtree instead:
https://www.atlassian.com/git/tutorials/git-subtree

On Mon, 31 Aug 2020 at 08:51, John Patrick  wrote:
>
> On Mon, 31 Aug 2020 at 14:16, Gary Gregory  wrote:
> >
> > On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
> >
> > > Git submodules are pointers to other git commits. Therefore, any component
> > > changes made don’t affect the mono repo until you update said mono repo to
> > > point to the new commit. If you do this to point at the latest release
> > > tags, this makes for less updates. Otherwise, you’ll want to figure out a
> > > CI system for automatically updating submodules to the latest master
> > > commits as they pass CI.
> > >
> >
> > Can that commit be HEAD?
>
> Used git submodules loads 2010-2015, and not much since. But from
> memory it can't be HEAD it has to be a specific commit hash.
>
> We had loads of issues when people worked on the sub modules
> independently, it was easier when every worked with the parent git
> module. But that was early 2010's so it might now allow HEAD or a
> named branch say develop or master/main.
>
> We also had loads of maven warnings because we had a wrapper project
> so from the git parent module it saw the submodules as maven modules.
> But the git parent module maven pom wasn't the parent pom of the git
> submodules maven pom. As parent automatically is
> ../pom.xml
>
> Our setup was;
>
> git-module
> -> pom.xml (GAV project:maven-wrapper:1)
> -> git-submodule-parent
> --> pom.xml (GAV project:parent:1)
> -> git-submodule-core
> --> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
> correct relative path is ../git-submodule-parent/poml.xml
>
> They had ~35 git submodules, not sure if they are still using submodules.
>
> So it can be useful if you want to have component based git repo's but
> it does add an extra overhead layer of maintenance and everyone needs
> to be onboard from experience.
>
> John
>
> >
> > Gary
> >
> >
> > >
> > > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> > >
> > > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
> > > wrote:
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > >
> > > >
> > > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > > >
> > > > > > >
> > > >
> > > > > > > Some questions:
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect any existing usage?
> > > >
> > > > > > >  i.e. can people continue to use the individual repos exactly as
> > > > before
> > > >
> > > > > >
> > > >
> > > > > > no they can’t
> > > >
> > > > > >
> > > >
> > > > >
> > > >
> > > > > Yes they can... this would be a new repo, and changes nothing for
> > > current
> > > >
> > > > > usage. This does not affect existing repos.
> > > >
> > > >
> > > >
> > > > What about my other queries?
> > > >
> > > >
> > > >
> > > > - changes to commit messages:
> > > >
> > > >  can people commit to components directly from the new repo?
> > > >
> > > > If so, does that change the commit messages?
> > > >
> > > >
> > > >
> > > > - maintenance of the new repo:
> > > >
> > > > what is involved, and how will the project know when updates are needed?
> > > >
> > > >
> > > >
> > > > > Gary
> > > >
> > > > >
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - does it affect Git emails in any way?
> > > >
> > > > > > >  e.g. do they have different text?
> > > >
> > > > > >
> > > >
> > > > > > same emails
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > - will it need much maintenance?
> > > >
> > > > > > > If so, how do we know when it needs updating?
> > > >
> > > > > >
> > > >
> > > > > > more maintainance, have to maintain a git hash at a symlink pointing
> > > > to an
> > > >
> > > > > > external repository
> > > >
> > > > > >
> > > >
> > > > > > -Rob
> > > >
> > > > > >
> > > >
> > > > > > >
> > > >
> > > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory  > > >
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > >> Yes yes "girl" -> "git"
> > > >
> > > > > > >>
> > > >
> > > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> > > >
> > > > > > wrote:
> > > >
> > > > > > >>
> > > >
> > > > > > >>> I'm talking about girl's own submodules:
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> https://git-scm.com/docs/git-submodule
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> Gary
> > > >
> > > > > > >>>
> > > >
> > > > > > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins 
> > > > wrote:
> > > >
> > > > > > >>>
> > > >
> > > > > >  By git submodules, are you talking about a symlink to another
> > > git
> > > >
> > > > > >  repository inside one of our repositories?
> > > >
> > > > > > 
> > > >
> > > > > >  -Rob
> > > >
> > > > > > 
> > > >
> > > > > > > On Aug 29, 2020, at 6:52 

Re: [All] New repo for all proper components as submodules?

[John Patrick]

On Mon, 31 Aug 2020 at 14:16, Gary Gregory  wrote:
>
> On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:
>
> > Git submodules are pointers to other git commits. Therefore, any component
> > changes made don’t affect the mono repo until you update said mono repo to
> > point to the new commit. If you do this to point at the latest release
> > tags, this makes for less updates. Otherwise, you’ll want to figure out a
> > CI system for automatically updating submodules to the latest master
> > commits as they pass CI.
> >
>
> Can that commit be HEAD?

Used git submodules loads 2010-2015, and not much since. But from
memory it can't be HEAD it has to be a specific commit hash.

We had loads of issues when people worked on the sub modules
independently, it was easier when every worked with the parent git
module. But that was early 2010's so it might now allow HEAD or a
named branch say develop or master/main.

We also had loads of maven warnings because we had a wrapper project
so from the git parent module it saw the submodules as maven modules.
But the git parent module maven pom wasn't the parent pom of the git
submodules maven pom. As parent automatically is
../pom.xml

Our setup was;

git-module
-> pom.xml (GAV project:maven-wrapper:1)
-> git-submodule-parent
--> pom.xml (GAV project:parent:1)
-> git-submodule-core
--> pom.xml (GAV project:core:1, parent GAV project:parent:1) So
correct relative path is ../git-submodule-parent/poml.xml

They had ~35 git submodules, not sure if they are still using submodules.

So it can be useful if you want to have component based git repo's but
it does add an extra overhead layer of maintenance and everyone needs
to be onboard from experience.

John

>
> Gary
>
>
> >
> > On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
> >
> > > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
> > wrote:
> > >
> > > >
> > >
> > > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
> > wrote:
> > >
> > > >
> > >
> > > > >
> > >
> > > > >
> > >
> > > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > >
> > > > > >
> > >
> > > > > > Some questions:
> > >
> > > > > >
> > >
> > > > > > - does it affect any existing usage?
> > >
> > > > > >  i.e. can people continue to use the individual repos exactly as
> > > before
> > >
> > > > >
> > >
> > > > > no they can’t
> > >
> > > > >
> > >
> > > >
> > >
> > > > Yes they can... this would be a new repo, and changes nothing for
> > current
> > >
> > > > usage. This does not affect existing repos.
> > >
> > >
> > >
> > > What about my other queries?
> > >
> > >
> > >
> > > - changes to commit messages:
> > >
> > >  can people commit to components directly from the new repo?
> > >
> > > If so, does that change the commit messages?
> > >
> > >
> > >
> > > - maintenance of the new repo:
> > >
> > > what is involved, and how will the project know when updates are needed?
> > >
> > >
> > >
> > > > Gary
> > >
> > > >
> > >
> > > > >
> > >
> > > > > >
> > >
> > > > > > - does it affect Git emails in any way?
> > >
> > > > > >  e.g. do they have different text?
> > >
> > > > >
> > >
> > > > > same emails
> > >
> > > > >
> > >
> > > > > >
> > >
> > > > > > - will it need much maintenance?
> > >
> > > > > > If so, how do we know when it needs updating?
> > >
> > > > >
> > >
> > > > > more maintainance, have to maintain a git hash at a symlink pointing
> > > to an
> > >
> > > > > external repository
> > >
> > > > >
> > >
> > > > > -Rob
> > >
> > > > >
> > >
> > > > > >
> > >
> > > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory  > >
> > >
> > > > > wrote:
> > >
> > > > > >>
> > >
> > > > > >> Yes yes "girl" -> "git"
> > >
> > > > > >>
> > >
> > > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> > >
> > > > > wrote:
> > >
> > > > > >>
> > >
> > > > > >>> I'm talking about girl's own submodules:
> > >
> > > > > >>>
> > >
> > > > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > >
> > > > > >>>
> > >
> > > > > >>> https://git-scm.com/docs/git-submodule
> > >
> > > > > >>>
> > >
> > > > > >>> Gary
> > >
> > > > > >>>
> > >
> > > > > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins 
> > > wrote:
> > >
> > > > > >>>
> > >
> > > > >  By git submodules, are you talking about a symlink to another
> > git
> > >
> > > > >  repository inside one of our repositories?
> > >
> > > > > 
> > >
> > > > >  -Rob
> > >
> > > > > 
> > >
> > > > > > On Aug 29, 2020, at 6:52 PM, Gary Gregory <
> > > garydgreg...@gmail.com>
> > >
> > > > >  wrote:
> > >
> > > > > >
> > >
> > > > > > Hi All,
> > >
> > > > > >
> > >
> > > > > > Any thoughts for or against creating a new git repository which
> > > would
> > >
> > > > > > contain all 'proper' Commons components as git submodules?
> > >
> > > > > >
> > >
> > > > > > The idea is to be able to checkout all of Commons 'proper' in
> > > one go
> > >
> > > > > in
> > >
> > > > >  one
> > >
> > > > > > place.
> > >
> > > > > >
> > >
> > > > > > Gary
> > >
> > > > > 
> > >
> 

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Mon, Aug 31, 2020 at 9:11 AM Matt Sicker  wrote:

> Git submodules are pointers to other git commits. Therefore, any component
> changes made don’t affect the mono repo until you update said mono repo to
> point to the new commit. If you do this to point at the latest release
> tags, this makes for less updates. Otherwise, you’ll want to figure out a
> CI system for automatically updating submodules to the latest master
> commits as they pass CI.
>

Can that commit be HEAD?

Gary


>
> On Mon, Aug 31, 2020 at 05:17 sebb  wrote:
>
> > On Sun, 30 Aug 2020 at 15:01, Gary Gregory 
> wrote:
> >
> > >
> >
> > > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins 
> wrote:
> >
> > >
> >
> > > >
> >
> > > >
> >
> > > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> >
> > > > >
> >
> > > > > Some questions:
> >
> > > > >
> >
> > > > > - does it affect any existing usage?
> >
> > > > >  i.e. can people continue to use the individual repos exactly as
> > before
> >
> > > >
> >
> > > > no they can’t
> >
> > > >
> >
> > >
> >
> > > Yes they can... this would be a new repo, and changes nothing for
> current
> >
> > > usage. This does not affect existing repos.
> >
> >
> >
> > What about my other queries?
> >
> >
> >
> > - changes to commit messages:
> >
> >  can people commit to components directly from the new repo?
> >
> > If so, does that change the commit messages?
> >
> >
> >
> > - maintenance of the new repo:
> >
> > what is involved, and how will the project know when updates are needed?
> >
> >
> >
> > > Gary
> >
> > >
> >
> > > >
> >
> > > > >
> >
> > > > > - does it affect Git emails in any way?
> >
> > > > >  e.g. do they have different text?
> >
> > > >
> >
> > > > same emails
> >
> > > >
> >
> > > > >
> >
> > > > > - will it need much maintenance?
> >
> > > > > If so, how do we know when it needs updating?
> >
> > > >
> >
> > > > more maintainance, have to maintain a git hash at a symlink pointing
> > to an
> >
> > > > external repository
> >
> > > >
> >
> > > > -Rob
> >
> > > >
> >
> > > > >
> >
> > > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory  >
> >
> > > > wrote:
> >
> > > > >>
> >
> > > > >> Yes yes "girl" -> "git"
> >
> > > > >>
> >
> > > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> >
> > > > wrote:
> >
> > > > >>
> >
> > > > >>> I'm talking about girl's own submodules:
> >
> > > > >>>
> >
> > > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >
> > > > >>>
> >
> > > > >>> https://git-scm.com/docs/git-submodule
> >
> > > > >>>
> >
> > > > >>> Gary
> >
> > > > >>>
> >
> > > > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins 
> > wrote:
> >
> > > > >>>
> >
> > > >  By git submodules, are you talking about a symlink to another
> git
> >
> > > >  repository inside one of our repositories?
> >
> > > > 
> >
> > > >  -Rob
> >
> > > > 
> >
> > > > > On Aug 29, 2020, at 6:52 PM, Gary Gregory <
> > garydgreg...@gmail.com>
> >
> > > >  wrote:
> >
> > > > >
> >
> > > > > Hi All,
> >
> > > > >
> >
> > > > > Any thoughts for or against creating a new git repository which
> > would
> >
> > > > > contain all 'proper' Commons components as git submodules?
> >
> > > > >
> >
> > > > > The idea is to be able to checkout all of Commons 'proper' in
> > one go
> >
> > > > in
> >
> > > >  one
> >
> > > > > place.
> >
> > > > >
> >
> > > > > Gary
> >
> > > > 
> >
> > > > 
> >
> > > > 
> > -
> >
> > > >  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >
> > > >  For additional commands, e-mail: dev-h...@commons.apache.org
> >
> > > > 
> >
> > > > 
> >
> > > > >
> >
> > > > >
> -
> >
> > > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >
> > > > > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> > > > >
> >
> > > >
> >
> > > >
> >
> > > > -
> >
> > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >
> > > > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> > > >
> >
> > > >
> >
> >
> >
> > -
> >
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
> >
> > --
> Matt Sicker 
>

Re: [All] New repo for all proper components as submodules?

[Matt Sicker]

Git submodules are pointers to other git commits. Therefore, any component
changes made don’t affect the mono repo until you update said mono repo to
point to the new commit. If you do this to point at the latest release
tags, this makes for less updates. Otherwise, you’ll want to figure out a
CI system for automatically updating submodules to the latest master
commits as they pass CI.

On Mon, Aug 31, 2020 at 05:17 sebb  wrote:

> On Sun, 30 Aug 2020 at 15:01, Gary Gregory  wrote:
>
> >
>
> > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  wrote:
>
> >
>
> > >
>
> > >
>
> > > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
>
> > > >
>
> > > > Some questions:
>
> > > >
>
> > > > - does it affect any existing usage?
>
> > > >  i.e. can people continue to use the individual repos exactly as
> before
>
> > >
>
> > > no they can’t
>
> > >
>
> >
>
> > Yes they can... this would be a new repo, and changes nothing for current
>
> > usage. This does not affect existing repos.
>
>
>
> What about my other queries?
>
>
>
> - changes to commit messages:
>
>  can people commit to components directly from the new repo?
>
> If so, does that change the commit messages?
>
>
>
> - maintenance of the new repo:
>
> what is involved, and how will the project know when updates are needed?
>
>
>
> > Gary
>
> >
>
> > >
>
> > > >
>
> > > > - does it affect Git emails in any way?
>
> > > >  e.g. do they have different text?
>
> > >
>
> > > same emails
>
> > >
>
> > > >
>
> > > > - will it need much maintenance?
>
> > > > If so, how do we know when it needs updating?
>
> > >
>
> > > more maintainance, have to maintain a git hash at a symlink pointing
> to an
>
> > > external repository
>
> > >
>
> > > -Rob
>
> > >
>
> > > >
>
> > > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory 
>
> > > wrote:
>
> > > >>
>
> > > >> Yes yes "girl" -> "git"
>
> > > >>
>
> > > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
>
> > > wrote:
>
> > > >>
>
> > > >>> I'm talking about girl's own submodules:
>
> > > >>>
>
> > > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>
> > > >>>
>
> > > >>> https://git-scm.com/docs/git-submodule
>
> > > >>>
>
> > > >>> Gary
>
> > > >>>
>
> > > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins 
> wrote:
>
> > > >>>
>
> > >  By git submodules, are you talking about a symlink to another git
>
> > >  repository inside one of our repositories?
>
> > > 
>
> > >  -Rob
>
> > > 
>
> > > > On Aug 29, 2020, at 6:52 PM, Gary Gregory <
> garydgreg...@gmail.com>
>
> > >  wrote:
>
> > > >
>
> > > > Hi All,
>
> > > >
>
> > > > Any thoughts for or against creating a new git repository which
> would
>
> > > > contain all 'proper' Commons components as git submodules?
>
> > > >
>
> > > > The idea is to be able to checkout all of Commons 'proper' in
> one go
>
> > > in
>
> > >  one
>
> > > > place.
>
> > > >
>
> > > > Gary
>
> > > 
>
> > > 
>
> > > 
> -
>
> > >  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> > >  For additional commands, e-mail: dev-h...@commons.apache.org
>
> > > 
>
> > > 
>
> > > >
>
> > > > -
>
> > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> > > > For additional commands, e-mail: dev-h...@commons.apache.org
>
> > > >
>
> > >
>
> > >
>
> > > -
>
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> > > For additional commands, e-mail: dev-h...@commons.apache.org
>
> > >
>
> > >
>
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>
> --
Matt Sicker 

Re: [All] New repo for all proper components as submodules?

[sebb]

On Sun, 30 Aug 2020 at 15:01, Gary Gregory  wrote:
>
> On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  wrote:
>
> >
> >
> > > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> > >
> > > Some questions:
> > >
> > > - does it affect any existing usage?
> > >  i.e. can people continue to use the individual repos exactly as before
> >
> > no they can’t
> >
>
> Yes they can... this would be a new repo, and changes nothing for current
> usage. This does not affect existing repos.

What about my other queries?

- changes to commit messages:
 can people commit to components directly from the new repo?
If so, does that change the commit messages?

- maintenance of the new repo:
what is involved, and how will the project know when updates are needed?

> Gary
>
> >
> > >
> > > - does it affect Git emails in any way?
> > >  e.g. do they have different text?
> >
> > same emails
> >
> > >
> > > - will it need much maintenance?
> > > If so, how do we know when it needs updating?
> >
> > more maintainance, have to maintain a git hash at a symlink pointing to an
> > external repository
> >
> > -Rob
> >
> > >
> > > On Sun, 30 Aug 2020 at 14:26, Gary Gregory 
> > wrote:
> > >>
> > >> Yes yes "girl" -> "git"
> > >>
> > >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> > wrote:
> > >>
> > >>> I'm talking about girl's own submodules:
> > >>>
> > >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> > >>>
> > >>> https://git-scm.com/docs/git-submodule
> > >>>
> > >>> Gary
> > >>>
> > >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> > >>>
> >  By git submodules, are you talking about a symlink to another git
> >  repository inside one of our repositories?
> > 
> >  -Rob
> > 
> > > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> >  wrote:
> > >
> > > Hi All,
> > >
> > > Any thoughts for or against creating a new git repository which would
> > > contain all 'proper' Commons components as git submodules?
> > >
> > > The idea is to be able to checkout all of Commons 'proper' in one go
> > in
> >  one
> > > place.
> > >
> > > Gary
> > 
> > 
> >  -
> >  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >  For additional commands, e-mail: dev-h...@commons.apache.org
> > 
> > 
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > > For additional commands, e-mail: dev-h...@commons.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >

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

Re: [All] New repo for all proper components as submodules?

[Romain Manni-Bucau]

+1, sounds like a good transversal and optional/not invasive addition.
Would we get any CI "check" job to ensure we don't miss a (new) repo or
kept an old one?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le lun. 31 août 2020 à 08:49, Thomas Vandahl  a écrit :

> On 30.08.20 00:52, Gary Gregory wrote:
> > Hi All,
> >
> > Any thoughts for or against creating a new git repository which would
> > contain all 'proper' Commons components as git submodules?
> >
> > The idea is to be able to checkout all of Commons 'proper' in one go in
> one
> > place.
>
> I understand this is in addition to the current repos?
>
> Bye, Thomas
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[Thomas Vandahl]

On 30.08.20 00:52, Gary Gregory wrote:

Hi All,

Any thoughts for or against creating a new git repository which would
contain all 'proper' Commons components as git submodules?

The idea is to be able to checkout all of Commons 'proper' in one go in one
place.


I understand this is in addition to the current repos?

Bye, Thomas

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

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Sun, Aug 30, 2020 at 10:03 AM Rob Tompkins  wrote:

>
>
> > On Aug 30, 2020, at 10:00 AM, Gary Gregory 
> wrote:
> >
> > On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  > wrote:
> >
> >>
> >>
> >>> On Aug 30, 2020, at 9:44 AM, sebb  seb...@gmail.com>> wrote:
> >>>
> >>> Some questions:
> >>>
> >>> - does it affect any existing usage?
> >>> i.e. can people continue to use the individual repos exactly as before
> >>
> >> no they can’t
> >>
> >
> > Yes they can... this would be a new repo, and changes nothing for current
> > usage. This does not affect existing repos.
>
> Oh…interesting. Then my head isn’t fully wrapped around the ideas at hand.
> I suppose that pulls me up to a +1 to see what ideas are at play.
>

Please have a quick read of the links I posted.

Gary


>
> -Rob
>
> >
> > Gary
> >
> >>
> >>>
> >>> - does it affect Git emails in any way?
> >>> e.g. do they have different text?
> >>
> >> same emails
> >>
> >>>
> >>> - will it need much maintenance?
> >>> If so, how do we know when it needs updating?
> >>
> >> more maintainance, have to maintain a git hash at a symlink pointing to
> an
> >> external repository
> >>
> >> -Rob
> >>
> >>>
> >>> On Sun, 30 Aug 2020 at 14:26, Gary Gregory 
> >> wrote:
> 
>  Yes yes "girl" -> "git"
> 
>  On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> >> wrote:
> 
> > I'm talking about girl's own submodules:
> >
> > https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >
> > https://git-scm.com/docs/git-submodule
> >
> > Gary
> >
> > On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> >
> >> By git submodules, are you talking about a symlink to another git
> >> repository inside one of our repositories?
> >>
> >> -Rob
> >>
> >>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> >> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> Any thoughts for or against creating a new git repository which
> would
> >>> contain all 'proper' Commons components as git submodules?
> >>>
> >>> The idea is to be able to checkout all of Commons 'proper' in one
> go
> >> in
> >> one
> >>> place.
> >>>
> >>> Gary
> >>
> >>
> >>
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >>> For additional commands, e-mail: dev-h...@commons.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org  dev-unsubscr...@commons.apache.org>
> >> For additional commands, e-mail: dev-h...@commons.apache.org  dev-h...@commons.apache.org>
>

Re: [All] New repo for all proper components as submodules?

[Rob Tompkins]

> On Aug 30, 2020, at 10:00 AM, Gary Gregory  wrote:
> 
> On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  > wrote:
> 
>> 
>> 
>>> On Aug 30, 2020, at 9:44 AM, sebb >> > wrote:
>>> 
>>> Some questions:
>>> 
>>> - does it affect any existing usage?
>>> i.e. can people continue to use the individual repos exactly as before
>> 
>> no they can’t
>> 
> 
> Yes they can... this would be a new repo, and changes nothing for current
> usage. This does not affect existing repos.

Oh…interesting. Then my head isn’t fully wrapped around the ideas at hand. I 
suppose that pulls me up to a +1 to see what ideas are at play.

-Rob

> 
> Gary
> 
>> 
>>> 
>>> - does it affect Git emails in any way?
>>> e.g. do they have different text?
>> 
>> same emails
>> 
>>> 
>>> - will it need much maintenance?
>>> If so, how do we know when it needs updating?
>> 
>> more maintainance, have to maintain a git hash at a symlink pointing to an
>> external repository
>> 
>> -Rob
>> 
>>> 
>>> On Sun, 30 Aug 2020 at 14:26, Gary Gregory 
>> wrote:
 
 Yes yes "girl" -> "git"
 
 On Sun, Aug 30, 2020, 09:24 Gary Gregory 
>> wrote:
 
> I'm talking about girl's own submodules:
> 
> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> 
> https://git-scm.com/docs/git-submodule
> 
> Gary
> 
> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> 
>> By git submodules, are you talking about a symlink to another git
>> repository inside one of our repositories?
>> 
>> -Rob
>> 
>>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>> wrote:
>>> 
>>> Hi All,
>>> 
>>> Any thoughts for or against creating a new git repository which would
>>> contain all 'proper' Commons components as git submodules?
>>> 
>>> The idea is to be able to checkout all of Commons 'proper' in one go
>> in
>> one
>>> place.
>>> 
>>> Gary
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@commons.apache.org 
>> 

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

On Sun, Aug 30, 2020 at 9:47 AM Rob Tompkins  wrote:

>
>
> > On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> >
> > Some questions:
> >
> > - does it affect any existing usage?
> >  i.e. can people continue to use the individual repos exactly as before
>
> no they can’t
>

Yes they can... this would be a new repo, and changes nothing for current
usage. This does not affect existing repos.

Gary

>
> >
> > - does it affect Git emails in any way?
> >  e.g. do they have different text?
>
> same emails
>
> >
> > - will it need much maintenance?
> > If so, how do we know when it needs updating?
>
> more maintainance, have to maintain a git hash at a symlink pointing to an
> external repository
>
> -Rob
>
> >
> > On Sun, 30 Aug 2020 at 14:26, Gary Gregory 
> wrote:
> >>
> >> Yes yes "girl" -> "git"
> >>
> >> On Sun, Aug 30, 2020, 09:24 Gary Gregory 
> wrote:
> >>
> >>> I'm talking about girl's own submodules:
> >>>
> >>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >>>
> >>> https://git-scm.com/docs/git-submodule
> >>>
> >>> Gary
> >>>
> >>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> >>>
>  By git submodules, are you talking about a symlink to another git
>  repository inside one of our repositories?
> 
>  -Rob
> 
> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>  wrote:
> >
> > Hi All,
> >
> > Any thoughts for or against creating a new git repository which would
> > contain all 'proper' Commons components as git submodules?
> >
> > The idea is to be able to checkout all of Commons 'proper' in one go
> in
>  one
> > place.
> >
> > Gary
> 
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>  For additional commands, e-mail: dev-h...@commons.apache.org
> 
> 
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[Bernd Eckenfels]

I don't mind if I don't have to maintain additional tracking revisions. If you 
check out all Repos once, you can easily do common work scripted across them, 
don't think a shared Repo root would help with that, but of course there is 
nothing speaking against it if you prefer that.

Bernd
--
http://bernd.eckenfels.net

Von: Rob Tompkins 
Gesendet: Sunday, August 30, 2020 3:46:27 PM
An: Commons Developers List 
Betreff: Re: [All] New repo for all proper components as submodules?

I’m a +/0 here. I’ve always had a headache in dealing with this mechanism of 
dependency managment. I would think we’d do better to rely on on the default 
dependency management system of the language (e.g. maven). That said, when 
there is no other mechanism (maybe with C++), then submodules can be 
acceptable. But they are hard to manage for folks that aren’t particularly 
adept at git. If it is for C, our expectation of our contributers is that they 
be quite good, so in that case it is indeed ok.

 Thoughts?

-Rob

> On Aug 30, 2020, at 9:25 AM, Gary Gregory  wrote:
>
> Yes yes "girl" -> "git"
>
> On Sun, Aug 30, 2020, 09:24 Gary Gregory  wrote:
>
>> I'm talking about girl's own submodules:
>>
>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>>
>> https://git-scm.com/docs/git-submodule
>>
>> Gary
>>
>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>>
>>> By git submodules, are you talking about a symlink to another git
>>> repository inside one of our repositories?
>>>
>>> -Rob
>>>
>>>> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>>> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> Any thoughts for or against creating a new git repository which would
>>>> contain all 'proper' Commons components as git submodules?
>>>>
>>>> The idea is to be able to checkout all of Commons 'proper' in one go in
>>> one
>>>> place.
>>>>
>>>> Gary
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>


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

Re: [All] New repo for all proper components as submodules?

[Rob Tompkins]

> On Aug 30, 2020, at 9:44 AM, sebb  wrote:
> 
> Some questions:
> 
> - does it affect any existing usage?
>  i.e. can people continue to use the individual repos exactly as before

no they can’t

> 
> - does it affect Git emails in any way?
>  e.g. do they have different text?

same emails

> 
> - will it need much maintenance?
> If so, how do we know when it needs updating?

more maintainance, have to maintain a git hash at a symlink pointing to an 
external repository

-Rob

> 
> On Sun, 30 Aug 2020 at 14:26, Gary Gregory  wrote:
>> 
>> Yes yes "girl" -> "git"
>> 
>> On Sun, Aug 30, 2020, 09:24 Gary Gregory  wrote:
>> 
>>> I'm talking about girl's own submodules:
>>> 
>>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>>> 
>>> https://git-scm.com/docs/git-submodule
>>> 
>>> Gary
>>> 
>>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>>> 
 By git submodules, are you talking about a symlink to another git
 repository inside one of our repositories?
 
 -Rob
 
> On Aug 29, 2020, at 6:52 PM, Gary Gregory 
 wrote:
> 
> Hi All,
> 
> Any thoughts for or against creating a new git repository which would
> contain all 'proper' Commons components as git submodules?
> 
> The idea is to be able to checkout all of Commons 'proper' in one go in
 one
> place.
> 
> Gary
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
 For additional commands, e-mail: dev-h...@commons.apache.org
 
 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


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

Re: [All] New repo for all proper components as submodules?

[Rob Tompkins]

I’m a +/0 here. I’ve always had a headache in dealing with this mechanism of 
dependency managment. I would think we’d do better to rely on on the default 
dependency management system of the language (e.g. maven). That said, when 
there is no other mechanism (maybe with C++), then submodules can be 
acceptable. But they are hard to manage for folks that aren’t particularly 
adept at git. If it is for C, our expectation of our contributers is that they 
be quite good, so in that case it is indeed ok.

 Thoughts?

-Rob

> On Aug 30, 2020, at 9:25 AM, Gary Gregory  wrote:
> 
> Yes yes "girl" -> "git"
> 
> On Sun, Aug 30, 2020, 09:24 Gary Gregory  wrote:
> 
>> I'm talking about girl's own submodules:
>> 
>> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>> 
>> https://git-scm.com/docs/git-submodule
>> 
>> Gary
>> 
>> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>> 
>>> By git submodules, are you talking about a symlink to another git
>>> repository inside one of our repositories?
>>> 
>>> -Rob
>>> 
 On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>>> wrote:
 
 Hi All,
 
 Any thoughts for or against creating a new git repository which would
 contain all 'proper' Commons components as git submodules?
 
 The idea is to be able to checkout all of Commons 'proper' in one go in
>>> one
 place.
 
 Gary
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>>> 


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

Re: [All] New repo for all proper components as submodules?

[sebb]

Some questions:

- does it affect any existing usage?
  i.e. can people continue to use the individual repos exactly as before

- does it affect Git emails in any way?
  e.g. do they have different text?

- will it need much maintenance?
 If so, how do we know when it needs updating?

On Sun, 30 Aug 2020 at 14:26, Gary Gregory  wrote:
>
> Yes yes "girl" -> "git"
>
> On Sun, Aug 30, 2020, 09:24 Gary Gregory  wrote:
>
> > I'm talking about girl's own submodules:
> >
> > https://git-scm.com/book/en/v2/Git-Tools-Submodules
> >
> > https://git-scm.com/docs/git-submodule
> >
> > Gary
> >
> > On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
> >
> >> By git submodules, are you talking about a symlink to another git
> >> repository inside one of our repositories?
> >>
> >> -Rob
> >>
> >> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> >> wrote:
> >> >
> >> > Hi All,
> >> >
> >> > Any thoughts for or against creating a new git repository which would
> >> > contain all 'proper' Commons components as git submodules?
> >> >
> >> > The idea is to be able to checkout all of Commons 'proper' in one go in
> >> one
> >> > place.
> >> >
> >> > Gary
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >>

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

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

Yes yes "girl" -> "git"

On Sun, Aug 30, 2020, 09:24 Gary Gregory  wrote:

> I'm talking about girl's own submodules:
>
> https://git-scm.com/book/en/v2/Git-Tools-Submodules
>
> https://git-scm.com/docs/git-submodule
>
> Gary
>
> On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:
>
>> By git submodules, are you talking about a symlink to another git
>> repository inside one of our repositories?
>>
>> -Rob
>>
>> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
>> wrote:
>> >
>> > Hi All,
>> >
>> > Any thoughts for or against creating a new git repository which would
>> > contain all 'proper' Commons components as git submodules?
>> >
>> > The idea is to be able to checkout all of Commons 'proper' in one go in
>> one
>> > place.
>> >
>> > Gary
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

I'm talking about girl's own submodules:

https://git-scm.com/book/en/v2/Git-Tools-Submodules

https://git-scm.com/docs/git-submodule

Gary

On Sun, Aug 30, 2020, 09:09 Rob Tompkins  wrote:

> By git submodules, are you talking about a symlink to another git
> repository inside one of our repositories?
>
> -Rob
>
> > On Aug 29, 2020, at 6:52 PM, Gary Gregory 
> wrote:
> >
> > Hi All,
> >
> > Any thoughts for or against creating a new git repository which would
> > contain all 'proper' Commons components as git submodules?
> >
> > The idea is to be able to checkout all of Commons 'proper' in one go in
> one
> > place.
> >
> > Gary
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

Ohhh
I misunderstand your thought lol.
I thought you wanna make a repo which can we ensure all commons projects
can build/run smothly together, without dependency-hell.

Gary Gregory  于2020年8月30日周日 下午8:59写道：

> My goal is not to duplicate Gump, this is about convenience of seeing and
> tracking all of Commons Proper.
>
> Gary
>
> On Sun, Aug 30, 2020, 00:50 Xeno Amess  wrote:
>
> > I doubt it can pass ci at any time...
> >
> >
> > Gary Gregory  于 2020年8月30日周日 上午6:52写道：
> >
> > > Hi All,
> > >
> > > Any thoughts for or against creating a new git repository which would
> > > contain all 'proper' Commons components as git submodules?
> > >
> > > The idea is to be able to checkout all of Commons 'proper' in one go in
> > one
> > > place.
> > >
> > > Gary
> > >
> >
>

Re: [All] New repo for all proper components as submodules?

[Rob Tompkins]

By git submodules, are you talking about a symlink to another git repository 
inside one of our repositories?

-Rob

> On Aug 29, 2020, at 6:52 PM, Gary Gregory  wrote:
> 
> Hi All,
> 
> Any thoughts for or against creating a new git repository which would
> contain all 'proper' Commons components as git submodules?
> 
> The idea is to be able to checkout all of Commons 'proper' in one go in one
> place.
> 
> Gary


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

Re: [All] New repo for all proper components as submodules?

[Gary Gregory]

My goal is not to duplicate Gump, this is about convenience of seeing and
tracking all of Commons Proper.

Gary

On Sun, Aug 30, 2020, 00:50 Xeno Amess  wrote:

> I doubt it can pass ci at any time...
>
>
> Gary Gregory  于 2020年8月30日周日 上午6:52写道：
>
> > Hi All,
> >
> > Any thoughts for or against creating a new git repository which would
> > contain all 'proper' Commons components as git submodules?
> >
> > The idea is to be able to checkout all of Commons 'proper' in one go in
> one
> > place.
> >
> > Gary
> >
>

Re: [All] New repo for all proper components as submodules?

[Xeno Amess]

I doubt it can pass ci at any time...


Gary Gregory  于 2020年8月30日周日 上午6:52写道：

> Hi All,
>
> Any thoughts for or against creating a new git repository which would
> contain all 'proper' Commons components as git submodules?
>
> The idea is to be able to checkout all of Commons 'proper' in one go in one
> place.
>
> Gary
>

[All] New repo for all proper components as submodules?

[Gary Gregory]

Hi All,

Any thoughts for or against creating a new git repository which would
contain all 'proper' Commons components as git submodules?

The idea is to be able to checkout all of Commons 'proper' in one go in one
place.

Gary