You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by Achim Hügen <ac...@gmx.de> on 2007/01/12 16:11:41 UTC
SVN Repository Restructuring
Hi,
I'm preparing a new repository structure.
https://svn.apache.org/repos/asf/hivemind/
site (global site)
hivemind1
branches
tags
trunk
hivemind2
branches
tags
trunk
This leaves us room for more subprojects.
If nobody objects I will change it later today
and post how to switch you local workspaces.
Achim
Re: SVN Repository Restructuring
Posted by James Carman <ja...@carmanconsulting.com>.
Cool! Then I'm +1
On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>
>
> James Carman schrieb:
> > Looks good to me. Just make sure you do the SVN magic that will allow
> > us to maintain history (I believe svn copy does that for us). So, the
> > files within /hivemind/trunk should match up with the stuff in
> > /hivemind1/trunk. Right?
>
> Right. I'll execute a "svn move" command which is a combined copy and
> delete operation.
>
> Achim
>
>
Re: SVN Repository Restructuring
Posted by Achim Hügen <ac...@gmx.de>.
James Carman schrieb:
> Looks good to me. Just make sure you do the SVN magic that will allow
> us to maintain history (I believe svn copy does that for us). So, the
> files within /hivemind/trunk should match up with the stuff in
> /hivemind1/trunk. Right?
Right. I'll execute a "svn move" command which is a combined copy and
delete operation.
Achim
Re: SVN Repository Restructuring
Posted by James Carman <ja...@carmanconsulting.com>.
Looks good to me. Just make sure you do the SVN magic that will allow
us to maintain history (I believe svn copy does that for us). So, the
files within /hivemind/trunk should match up with the stuff in
/hivemind1/trunk. Right?
On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> Hi,
>
> I'm preparing a new repository structure.
>
> https://svn.apache.org/repos/asf/hivemind/
>
> site (global site)
> hivemind1
> branches
> tags
> trunk
> hivemind2
> branches
> tags
> trunk
>
> This leaves us room for more subprojects.
> If nobody objects I will change it later today
> and post how to switch you local workspaces.
>
> Achim
>
>
>
Re: SVN Repository Restructuring
Posted by Howard Lewis Ship <hl...@gmail.com>.
That's the magic of SVN ... you really can change your mind later.
Within reason.
On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> I've used the single project layout for now.
> We can change the layout of the hivemind2 folder later
> if anybody agrees on it.
>
> Achim
>
> Am Fri, 12 Jan 2007 19:41:40 +0100 schrieb Howard Lewis Ship
> <hl...@gmail.com>:
>
> > Didn't format very well.
> >
> > There isn't a "global" branch.
> >
> > Under hivemind2, everythings a sub-project.
> >
> > Each subproject has branches/tags/trunk.
> >
> > One subproject, hivemind-project, is actually the parent of the others,
> > with
> >
> > <modules>
> > <module>../hivemind-framework</module>
> > <module>../hivemind-library</module>
> > . . .
> > </modules>
> >
> > Such that a build there will jump into each other module and do a build.
> >
> > You don't, and don't want to, branch the entire project. What you want
> > are individual
> > sub-projects that can each have their own development cycle.
> >
> > On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> >> What is the consequence for branching?
> >> Can we still branch the whole project with all modules?
> >> Where does this global branch goes to?
> >>
> >> hivemind2
> >> hivemind-framework
> >> branches
> >> tags
> >> trunk
> >> hivemind-library
> >> branches
> >> tags
> >> trunk
> >> branches???
> >>
> >>
> >> Achim
> >>
> >> Am Fri, 12 Jan 2007 17:14:16 +0100 schrieb Howard Lewis Ship
> >> <hl...@gmail.com>:
> >>
> >> > I think you would be better served allowing each sub-project to have
> >> > its own branches/tag/trunk:
> >> >
> >> > site
> >> > hivemind1
> >> > ...
> >> > hivemind2
> >> > hivemind-framework
> >> > branches
> >> > tags
> >> > trunk
> >> > hivemind-library
> >> > branches
> >> > tags
> >> > trunk
> >> > something-not-yet-identified
> >> > branches
> >> > tags
> >> > trunk
> >> >
> >> > Also, aligning the folder names with the Maven module names helps keep
> >> > everything sane.
> >> >
> >> > This is the structure I've been working on in Tapestry 5.
> >> >
> >> > There' should also be another peer folder, hivemin2/hivemind-project
> >> > that generates the hivemind2 site and contains the master POM for the
> >> > other hivemind2 projects. Again, Tapestry5 as the reference.
> >> >
> >> > On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> >> >> Hi,
> >> >>
> >> >> I'm preparing a new repository structure.
> >> >>
> >> >> https://svn.apache.org/repos/asf/hivemind/
> >> >>
> >> >> site (global site)
> >> >> hivemind1
> >> >> branches
> >> >> tags
> >> >> trunk
> >> >> hivemind2
> >> >> branches
> >> >> tags
> >> >> trunk
> >> >>
> >> >> This leaves us room for more subprojects.
> >> >> If nobody objects I will change it later today
> >> >> and post how to switch you local workspaces.
> >> >>
> >> >> Achim
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >
> >
>
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
Re: SVN Repository Restructuring
Posted by Achim Hügen <ac...@gmx.de>.
Of course I meant 'everybody' ...
Am Fri, 12 Jan 2007 22:01:05 +0100 schrieb Achim Hügen
<ac...@gmx.de>:
> I've used the single project layout for now.
> We can change the layout of the hivemind2 folder later
> if anybody agrees on it.
>
> Achim
>
> Am Fri, 12 Jan 2007 19:41:40 +0100 schrieb Howard Lewis Ship
> <hl...@gmail.com>:
>
>> Didn't format very well.
>>
>> There isn't a "global" branch.
>>
>> Under hivemind2, everythings a sub-project.
>>
>> Each subproject has branches/tags/trunk.
>>
>> One subproject, hivemind-project, is actually the parent of the others,
>> with
>>
>> <modules>
>> <module>../hivemind-framework</module>
>> <module>../hivemind-library</module>
>> . . .
>> </modules>
>>
>> Such that a build there will jump into each other module and do a build.
>>
>> You don't, and don't want to, branch the entire project. What you want
>> are individual
>> sub-projects that can each have their own development cycle.
>>
>> On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>>> What is the consequence for branching?
>>> Can we still branch the whole project with all modules?
>>> Where does this global branch goes to?
>>>
>>> hivemind2
>>> hivemind-framework
>>> branches
>>> tags
>>> trunk
>>> hivemind-library
>>> branches
>>> tags
>>> trunk
>>> branches???
>>>
>>>
>>> Achim
>>>
>>> Am Fri, 12 Jan 2007 17:14:16 +0100 schrieb Howard Lewis Ship
>>> <hl...@gmail.com>:
>>>
>>> > I think you would be better served allowing each sub-project to have
>>> > its own branches/tag/trunk:
>>> >
>>> > site
>>> > hivemind1
>>> > ...
>>> > hivemind2
>>> > hivemind-framework
>>> > branches
>>> > tags
>>> > trunk
>>> > hivemind-library
>>> > branches
>>> > tags
>>> > trunk
>>> > something-not-yet-identified
>>> > branches
>>> > tags
>>> > trunk
>>> >
>>> > Also, aligning the folder names with the Maven module names helps
>>> keep
>>> > everything sane.
>>> >
>>> > This is the structure I've been working on in Tapestry 5.
>>> >
>>> > There' should also be another peer folder, hivemin2/hivemind-project
>>> > that generates the hivemind2 site and contains the master POM for the
>>> > other hivemind2 projects. Again, Tapestry5 as the reference.
>>> >
>>> > On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>>> >> Hi,
>>> >>
>>> >> I'm preparing a new repository structure.
>>> >>
>>> >> https://svn.apache.org/repos/asf/hivemind/
>>> >>
>>> >> site (global site)
>>> >> hivemind1
>>> >> branches
>>> >> tags
>>> >> trunk
>>> >> hivemind2
>>> >> branches
>>> >> tags
>>> >> trunk
>>> >>
>>> >> This leaves us room for more subprojects.
>>> >> If nobody objects I will change it later today
>>> >> and post how to switch you local workspaces.
>>> >>
>>> >> Achim
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>
Re: SVN Repository Restructuring
Posted by Achim Hügen <ac...@gmx.de>.
I've used the single project layout for now.
We can change the layout of the hivemind2 folder later
if anybody agrees on it.
Achim
Am Fri, 12 Jan 2007 19:41:40 +0100 schrieb Howard Lewis Ship
<hl...@gmail.com>:
> Didn't format very well.
>
> There isn't a "global" branch.
>
> Under hivemind2, everythings a sub-project.
>
> Each subproject has branches/tags/trunk.
>
> One subproject, hivemind-project, is actually the parent of the others,
> with
>
> <modules>
> <module>../hivemind-framework</module>
> <module>../hivemind-library</module>
> . . .
> </modules>
>
> Such that a build there will jump into each other module and do a build.
>
> You don't, and don't want to, branch the entire project. What you want
> are individual
> sub-projects that can each have their own development cycle.
>
> On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>> What is the consequence for branching?
>> Can we still branch the whole project with all modules?
>> Where does this global branch goes to?
>>
>> hivemind2
>> hivemind-framework
>> branches
>> tags
>> trunk
>> hivemind-library
>> branches
>> tags
>> trunk
>> branches???
>>
>>
>> Achim
>>
>> Am Fri, 12 Jan 2007 17:14:16 +0100 schrieb Howard Lewis Ship
>> <hl...@gmail.com>:
>>
>> > I think you would be better served allowing each sub-project to have
>> > its own branches/tag/trunk:
>> >
>> > site
>> > hivemind1
>> > ...
>> > hivemind2
>> > hivemind-framework
>> > branches
>> > tags
>> > trunk
>> > hivemind-library
>> > branches
>> > tags
>> > trunk
>> > something-not-yet-identified
>> > branches
>> > tags
>> > trunk
>> >
>> > Also, aligning the folder names with the Maven module names helps keep
>> > everything sane.
>> >
>> > This is the structure I've been working on in Tapestry 5.
>> >
>> > There' should also be another peer folder, hivemin2/hivemind-project
>> > that generates the hivemind2 site and contains the master POM for the
>> > other hivemind2 projects. Again, Tapestry5 as the reference.
>> >
>> > On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>> >> Hi,
>> >>
>> >> I'm preparing a new repository structure.
>> >>
>> >> https://svn.apache.org/repos/asf/hivemind/
>> >>
>> >> site (global site)
>> >> hivemind1
>> >> branches
>> >> tags
>> >> trunk
>> >> hivemind2
>> >> branches
>> >> tags
>> >> trunk
>> >>
>> >> This leaves us room for more subprojects.
>> >> If nobody objects I will change it later today
>> >> and post how to switch you local workspaces.
>> >>
>> >> Achim
>> >>
>> >>
>> >
>> >
>>
>>
>>
>
>
Re: SVN Repository Restructuring
Posted by Howard Lewis Ship <hl...@gmail.com>.
Didn't format very well.
There isn't a "global" branch.
Under hivemind2, everythings a sub-project.
Each subproject has branches/tags/trunk.
One subproject, hivemind-project, is actually the parent of the others, with
<modules>
<module>../hivemind-framework</module>
<module>../hivemind-library</module>
. . .
</modules>
Such that a build there will jump into each other module and do a build.
You don't, and don't want to, branch the entire project. What you want
are individual
sub-projects that can each have their own development cycle.
On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> What is the consequence for branching?
> Can we still branch the whole project with all modules?
> Where does this global branch goes to?
>
> hivemind2
> hivemind-framework
> branches
> tags
> trunk
> hivemind-library
> branches
> tags
> trunk
> branches???
>
>
> Achim
>
> Am Fri, 12 Jan 2007 17:14:16 +0100 schrieb Howard Lewis Ship
> <hl...@gmail.com>:
>
> > I think you would be better served allowing each sub-project to have
> > its own branches/tag/trunk:
> >
> > site
> > hivemind1
> > ...
> > hivemind2
> > hivemind-framework
> > branches
> > tags
> > trunk
> > hivemind-library
> > branches
> > tags
> > trunk
> > something-not-yet-identified
> > branches
> > tags
> > trunk
> >
> > Also, aligning the folder names with the Maven module names helps keep
> > everything sane.
> >
> > This is the structure I've been working on in Tapestry 5.
> >
> > There' should also be another peer folder, hivemin2/hivemind-project
> > that generates the hivemind2 site and contains the master POM for the
> > other hivemind2 projects. Again, Tapestry5 as the reference.
> >
> > On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> >> Hi,
> >>
> >> I'm preparing a new repository structure.
> >>
> >> https://svn.apache.org/repos/asf/hivemind/
> >>
> >> site (global site)
> >> hivemind1
> >> branches
> >> tags
> >> trunk
> >> hivemind2
> >> branches
> >> tags
> >> trunk
> >>
> >> This leaves us room for more subprojects.
> >> If nobody objects I will change it later today
> >> and post how to switch you local workspaces.
> >>
> >> Achim
> >>
> >>
> >
> >
>
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
Re: SVN Repository Restructuring
Posted by Achim Hügen <ac...@gmx.de>.
What is the consequence for branching?
Can we still branch the whole project with all modules?
Where does this global branch goes to?
hivemind2
hivemind-framework
branches
tags
trunk
hivemind-library
branches
tags
trunk
branches???
Achim
Am Fri, 12 Jan 2007 17:14:16 +0100 schrieb Howard Lewis Ship
<hl...@gmail.com>:
> I think you would be better served allowing each sub-project to have
> its own branches/tag/trunk:
>
> site
> hivemind1
> ...
> hivemind2
> hivemind-framework
> branches
> tags
> trunk
> hivemind-library
> branches
> tags
> trunk
> something-not-yet-identified
> branches
> tags
> trunk
>
> Also, aligning the folder names with the Maven module names helps keep
> everything sane.
>
> This is the structure I've been working on in Tapestry 5.
>
> There' should also be another peer folder, hivemin2/hivemind-project
> that generates the hivemind2 site and contains the master POM for the
> other hivemind2 projects. Again, Tapestry5 as the reference.
>
> On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
>> Hi,
>>
>> I'm preparing a new repository structure.
>>
>> https://svn.apache.org/repos/asf/hivemind/
>>
>> site (global site)
>> hivemind1
>> branches
>> tags
>> trunk
>> hivemind2
>> branches
>> tags
>> trunk
>>
>> This leaves us room for more subprojects.
>> If nobody objects I will change it later today
>> and post how to switch you local workspaces.
>>
>> Achim
>>
>>
>
>
Re: SVN Repository Restructuring
Posted by Howard Lewis Ship <hl...@gmail.com>.
I think you would be better served allowing each sub-project to have
its own branches/tag/trunk:
site
hivemind1
...
hivemind2
hivemind-framework
branches
tags
trunk
hivemind-library
branches
tags
trunk
something-not-yet-identified
branches
tags
trunk
Also, aligning the folder names with the Maven module names helps keep
everything sane.
This is the structure I've been working on in Tapestry 5.
There' should also be another peer folder, hivemin2/hivemind-project
that generates the hivemind2 site and contains the master POM for the
other hivemind2 projects. Again, Tapestry5 as the reference.
On 1/12/07, Achim Hügen <ac...@gmx.de> wrote:
> Hi,
>
> I'm preparing a new repository structure.
>
> https://svn.apache.org/repos/asf/hivemind/
>
> site (global site)
> hivemind1
> branches
> tags
> trunk
> hivemind2
> branches
> tags
> trunk
>
> This leaves us room for more subprojects.
> If nobody objects I will change it later today
> and post how to switch you local workspaces.
>
> Achim
>
>
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com