11:49 a.m.
Adding Scott and jboss-as7-deb(a)lists.jboss.org.
No, I'm not on the jboss as internal list, not sure why we need to discuss it there?
This has come up a couple of times recently. The main issue I see is that this will result
in around 80-100 git repositories, and a lot of scripting to create coordinated releases.
It sounds like an admin and contribution nightmare to me.
I've thought about the problem Scott raises, and the best solution I've come up
with so far is copy and paste:
git clone git://github.com/jbossas/quickstart.git ../quickstaets
cp -r ../quickstart/kitchensink/* .
git add src pom.xml
git push
which is only one more command.
We can also use a subtree merge (which is what you need to look at Scott, not submodules),
but I feel this is much more complex to advise to users, as it involves explaining what a
subtree merge is, over everyone knowing what a copy and paste is.
On 14 Mar 2012, at 01:00, Sande Gilda wrote:
Did you see this? It sounds like it would be a problem to administer
and release. What do you think?
-------- Original Message --------
Subject: Breakup quickstarts into separate repos?
Date: Tue, 13 Mar 2012 17:11:25 -0400 (EDT)
From: Scott Stark <sstark(a)redhat.com>
To: jboss-as(a)redhat.com
Would it make sense to break each quickstart into it's own repository and then
integrate them back into the quickstart repository using the git submodule? What I would
like to be able to do is something like the following in an openshift app repo to switch
over to the quickstart:
git remote add upstream -m master git://github.com/jbossas/kitchensink.git
git pull -s recursive -X theirs upstream master
git push
There is no notion of checking out a subdirectory of a git repo. One problem I see with
using submodules is that when I checkout the root project containing the submodules, the
submodules content is not checked out. There is a comment in one submodule tutorial that
claims later versions of git due checkout the submodule content, but with my git version
1.7.9.1 I don't see that happening.
6:35 p.m.
New subject: Breakup quickstarts into separate repos?
To answer Paul's question and respond to Pete here, the only reason is to have a
simple set of steps to take a new openshift application repo and update it to one of the
as7 quickstarts. One additional step is needed over what Pete shows as you need to remove
the existing source since the original base app has classes/descriptors that no longer
apply.
Maybe the subtree merge logic could be added to the rhc openshift tools to simplify this.
I'll play around with some things.
----- Original Message -----
From: "Pete Muir" <pmuir(a)redhat.com>
To: "Sande Gilda" <sgilda(a)redhat.com>
Cc: "Paul Gier" <pgier(a)redhat.com>, "Shelly McGowan"
<smcgowan(a)redhat.com>, "Burr Sutter" <bsutter(a)redhat.com>,
"Scott Stark" <sstark(a)redhat.com>, "jboss-as7-dev(a)lists.jboss.org
Development" <jboss-as7-dev(a)lists.jboss.org>
Sent: Wednesday, March 14, 2012 3:49:57 AM
Subject: Re: Breakup quickstarts into separate repos?
Adding Scott and jboss-as7-deb(a)lists.jboss.org.
No, I'm not on the jboss as internal list, not sure why we need to discuss it there?
This has come up a couple of times recently. The main issue I see is that this will result
in around 80-100 git repositories, and a lot of scripting to create coordinated releases.
It sounds like an admin and contribution nightmare to me.
I've thought about the problem Scott raises, and the best solution I've come up
with so far is copy and paste:
git clone git://github.com/jbossas/quickstart.git ../quickstaets
cp -r ../quickstart/kitchensink/* .
git add src pom.xml
git push
which is only one more command.
We can also use a subtree merge (which is what you need to look at Scott, not submodules),
but I feel this is much more complex to advise to users, as it involves explaining what a
subtree merge is, over everyone knowing what a copy and paste is.
On 14 Mar 2012, at 01:00, Sande Gilda wrote:
Did you see this? It sounds like it would be a problem to administer
and release. What do you think?
-------- Original Message --------
Subject: Breakup quickstarts into separate repos?
Date: Tue, 13 Mar 2012 17:11:25 -0400 (EDT)
From: Scott Stark <sstark(a)redhat.com>
To: jboss-as(a)redhat.com
Would it make sense to break each quickstart into it's own repository and then
integrate them back into the quickstart repository using the git submodule? What I would
like to be able to do is something like the following in an openshift app repo to switch
over to the quickstart:
git remote add upstream -m master git://github.com/jbossas/kitchensink.git
git pull -s recursive -X theirs upstream master
git push
There is no notion of checking out a subdirectory of a git repo. One problem I see with
using submodules is that when I checkout the root project containing the submodules, the
submodules content is not checked out. There is a comment in one submodule tutorial that
claims later versions of git due checkout the submodule content, but with my git version
1.7.9.1 I don't see that happening.
3:29 p.m.
New subject: Breakup quickstarts into separate repos?
Another approach for these could be to have the release be the one that splits out the
examples into multiple repositories for more direct use in openshift.
p.s. having it as singular git repos also helps tools like jboss tools to allow focused
import instead of "everything".
/max
On Mar 14, 2012, at 6:35 PM, Scott Stark wrote:
To answer Paul's question and respond to Pete here, the only
reason is to have a simple set of steps to take a new openshift application repo and
update it to one of the as7 quickstarts. One additional step is needed over what Pete
shows as you need to remove the existing source since the original base app has
classes/descriptors that no longer apply.
Maybe the subtree merge logic could be added to the rhc openshift tools to simplify this.
I'll play around with some things.
----- Original Message -----
From: "Pete Muir" <pmuir(a)redhat.com>
To: "Sande Gilda" <sgilda(a)redhat.com>
Cc: "Paul Gier" <pgier(a)redhat.com>, "Shelly McGowan"
<smcgowan(a)redhat.com>, "Burr Sutter" <bsutter(a)redhat.com>,
"Scott Stark" <sstark(a)redhat.com>, "jboss-as7-dev(a)lists.jboss.org
Development" <jboss-as7-dev(a)lists.jboss.org>
Sent: Wednesday, March 14, 2012 3:49:57 AM
Subject: Re: Breakup quickstarts into separate repos?
Adding Scott and jboss-as7-deb(a)lists.jboss.org.
No, I'm not on the jboss as internal list, not sure why we need to discuss it there?
This has come up a couple of times recently. The main issue I see is that this will
result in around 80-100 git repositories, and a lot of scripting to create coordinated
releases. It sounds like an admin and contribution nightmare to me.
I've thought about the problem Scott raises, and the best solution I've come up
with so far is copy and paste:
git clone git://github.com/jbossas/quickstart.git ../quickstaets
cp -r ../quickstart/kitchensink/* .
git add src pom.xml
git push
which is only one more command.
We can also use a subtree merge (which is what you need to look at Scott, not
submodules), but I feel this is much more complex to advise to users, as it involves
explaining what a subtree merge is, over everyone knowing what a copy and paste is.
On 14 Mar 2012, at 01:00, Sande Gilda wrote:
> Did you see this? It sounds like it would be a problem to administer and release.
What do you think?
>
> -------- Original Message --------
> Subject: Breakup quickstarts into separate repos?
> Date: Tue, 13 Mar 2012 17:11:25 -0400 (EDT)
> From: Scott Stark <sstark(a)redhat.com>
> To: jboss-as(a)redhat.com
>
> Would it make sense to break each quickstart into it's own repository and then
integrate them back into the quickstart repository using the git submodule? What I would
like to be able to do is something like the following in an openshift app repo to switch
over to the quickstart:
>
> git remote add upstream -m master git://github.com/jbossas/kitchensink.git
> git pull -s recursive -X theirs upstream master
> git push
>
> There is no notion of checking out a subdirectory of a git repo. One problem I see
with using submodules is that when I checkout the root project containing the submodules,
the submodules content is not checked out. There is a comment in one submodule tutorial
that claims later versions of git due checkout the submodule content, but with my git
version 1.7.9.1 I don't see that happening.
>
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4398
days inactive
4419
days old
2 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Pete Muir -
Scott Stark