You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Sean Schofield <se...@gmail.com> on 2005/06/21 18:38:47 UTC
SVN Reorg
I'd like to start doing the SVN reorg this Thursday. I propose that
on Thursday AM, Manfred temporarily disable SVN commit access to all
but Manfred and myself. I'll also request that SVN emails be turned
off temporarily while we move things. I'll then do the SVN reorg on
Thursday and we can reactivate SVN commit and the emails.
I've worked everything out in a test SVN repository and the new
structure is nearly identical to what was discussed in my earlier
thread. Ultimately I think we should just go ahead and move it and
see if we are all happy with the results. We can make minor changes
to the structure without any problems.
There are a few things that will have to be sorted out after the
initial phase. One example is unit tests which are kind of scattered.
Things like this which are not totally essential will not be moved.
Before the move I will label the current repository as
(BEFORE_SVN_REORG) or something so that we can always checkout by this
label and see everything in the old layout. Then we can move
individual files that weren't handled in the initial phase on a case
by case basis.
Also, this will obviously break all of the builds (including the
nightly builds.) I'll start on the new scripts on Friday and
hopefully we'll have things back up and running within a few days.
I will need lots of help cleaning things up and sorting things out
over the next few days. There is a lot that predates my involvement
in the project and I can only take us so far on my own. I think I
have a handle on the crucial stuff and I did a lot of the work on the
builds so we should be ok as far as the bare minimum stuff.
Let me know what folks think about this plan.
sean
Re: SVN Reorg
Posted by Sean Schofield <se...@gmail.com>.
Thanks for the feedback. I skipped the codegen stuff for the initial
pass. We can (and will) deal with it eventually. Some of it appears
to be necessary for the WAP stuff (which belongs in tomahawk) so I
have to think on that a bit.
sean
On 6/21/05, Bruno Aranda <br...@gmail.com> wrote:
> Impressive. Thanks Sean for taking the time and neuron processing time
> to reorganize the SVN. I've just done a checkout of the current
> without problems. At first sight, it looks very clear and intuitive.
> This is, indeed, a more natural organization of the project. The
> svn:externals system is really good and works like a charm.
>
> I am eager to see all this working ;-)
>
> By the way, for the code generation stuff I would use a root called
> tools, as you propose in an earlier post (tools/codegen,tools/xdoclet,
> tools/wml).
>
> Regards,
>
> Bruno
>
> 2005/6/21, Sean Schofield <se...@gmail.com>:
> > I finished up a test run of the reorg. There are several outstanding
> > issues (no lib directory etc.) but there is enough there for you to
> > get the picture.
> >
> > You can browse it at: http://svn.apache.org/repos/test/myfaces/
> >
> > To get the latest do a checkout of:
> > http://svn.apache.org/repos/test/myfaces/current and you will see the
> > svn:externals in action!
> >
> > As I mentioned, we will have the latest code (just before the move)
> > tagged so that the old structure and files will be available. I
> > didn't do that in the test server but you can see what I mean if you
> > check out the last tagged version of the code:
> >
> > http://svn.apache.org/repos/test/myfaces/core/tags/rel_1_0_9/
> >
> > sean
> >
>
Re: SVN Reorg
Posted by Bruno Aranda <br...@gmail.com>.
Impressive. Thanks Sean for taking the time and neuron processing time
to reorganize the SVN. I've just done a checkout of the current
without problems. At first sight, it looks very clear and intuitive.
This is, indeed, a more natural organization of the project. The
svn:externals system is really good and works like a charm.
I am eager to see all this working ;-)
By the way, for the code generation stuff I would use a root called
tools, as you propose in an earlier post (tools/codegen,tools/xdoclet,
tools/wml).
Regards,
Bruno
2005/6/21, Sean Schofield <se...@gmail.com>:
> I finished up a test run of the reorg. There are several outstanding
> issues (no lib directory etc.) but there is enough there for you to
> get the picture.
>
> You can browse it at: http://svn.apache.org/repos/test/myfaces/
>
> To get the latest do a checkout of:
> http://svn.apache.org/repos/test/myfaces/current and you will see the
> svn:externals in action!
>
> As I mentioned, we will have the latest code (just before the move)
> tagged so that the old structure and files will be available. I
> didn't do that in the test server but you can see what I mean if you
> check out the last tagged version of the code:
>
> http://svn.apache.org/repos/test/myfaces/core/tags/rel_1_0_9/
>
> sean
>
Re: SVN Reorg
Posted by Sean Schofield <se...@gmail.com>.
Mike,
You were correct at the time of your posting but the location has moved
(https://svn.apache.org/repos/asf/myfaces/core/tags/before_svn_reorg.)
Out of curiosity, why do you need the old source code? The new code
should suffice. The build process is almost complete but for now you
can certainly compile in any IDE.
sean
On 6/27/05, Mike Kienenberger <mk...@gmail.com> wrote:
> On 6/21/05, Sean Schofield <se...@gmail.com> wrote:
> > Before the move I will label the current repository as
> > (BEFORE_SVN_REORG) or something so that we can always checkout by this
> > label and see everything in the old layout. Then we can move
> > individual files that weren't handled in the initial phase on a case
> > by case basis.
>
> On 6/21/05, Sean Schofield <se...@gmail.com> wrote:
> > As I mentioned, we will have the latest code (just before the move)
> > tagged so that the old structure and files will be available. I
> > didn't do that in the test server but you can see what I mean if you
> > check out the last tagged version of the code:
> >
> > http://svn.apache.org/repos/test/myfaces/core/tags/rel_1_0_9/
>
> For anyone out there who need a copy of the pre-svn-reorg and is a svn
> novice like myself, the path (painfully-discovered) to the
> pre-svn-reorg source appears to be:
>
> https://svn.apache.org/repos/asf/myfaces/impl/tags/before_svn_reorg
>
Re: SVN Reorg
Posted by Mike Kienenberger <mk...@gmail.com>.
On 6/21/05, Sean Schofield <se...@gmail.com> wrote:
> Before the move I will label the current repository as
> (BEFORE_SVN_REORG) or something so that we can always checkout by this
> label and see everything in the old layout. Then we can move
> individual files that weren't handled in the initial phase on a case
> by case basis.
On 6/21/05, Sean Schofield <se...@gmail.com> wrote:
> As I mentioned, we will have the latest code (just before the move)
> tagged so that the old structure and files will be available. I
> didn't do that in the test server but you can see what I mean if you
> check out the last tagged version of the code:
>
> http://svn.apache.org/repos/test/myfaces/core/tags/rel_1_0_9/
For anyone out there who need a copy of the pre-svn-reorg and is a svn
novice like myself, the path (painfully-discovered) to the
pre-svn-reorg source appears to be:
https://svn.apache.org/repos/asf/myfaces/impl/tags/before_svn_reorg
Re: SVN Reorg
Posted by Sean Schofield <se...@gmail.com>.
I finished up a test run of the reorg. There are several outstanding
issues (no lib directory etc.) but there is enough there for you to
get the picture.
You can browse it at: http://svn.apache.org/repos/test/myfaces/
To get the latest do a checkout of:
http://svn.apache.org/repos/test/myfaces/current and you will see the
svn:externals in action!
As I mentioned, we will have the latest code (just before the move)
tagged so that the old structure and files will be available. I
didn't do that in the test server but you can see what I mean if you
check out the last tagged version of the code:
http://svn.apache.org/repos/test/myfaces/core/tags/rel_1_0_9/
sean
Re: SVN Reorg
Posted by Martin Marinschek <ma...@gmail.com>.
Poor Matze!
the ISP can now put on their homepage that they have healed an
internet addict ;)
regards,
Martin
On 6/23/05, Matthias Wessendorf <mw...@gmail.com> wrote:
> Sean,
>
> thanks for taking care on that. I just browsed through the new
> structure and it looks very clean. I hope to come back soon...
>
> btw. I just sent my German "isp" a denouncement, since I am waiting
> three month and nothing has done... I never!!! choose a *cheap* isp
> again. They (mostly) suck!
>
> -Matthias
>
> On 6/22/05, Manfred Geiler <ma...@gmail.com> wrote:
> > Sean, thanks for the hard work.
> > Unfortunately at the moment I'm under great preasure at my company
> > and fear that I cannot be of much help. I will try of course. On
> > Saturday morning I will be on the plane to SF for JavaOne. Of course
> > we will stay in contact next week, but I cannot promise that I will be
> > able to do more than read/answer emails.
> >
> > -Manfred
> >
> >
> > 2005/6/21, Sean Schofield <se...@gmail.com>:
> > > I'd like to start doing the SVN reorg this Thursday. I propose that
> > > on Thursday AM, Manfred temporarily disable SVN commit access to all
> > > but Manfred and myself. I'll also request that SVN emails be turned
> > > off temporarily while we move things. I'll then do the SVN reorg on
> > > Thursday and we can reactivate SVN commit and the emails.
> > >
> > > I've worked everything out in a test SVN repository and the new
> > > structure is nearly identical to what was discussed in my earlier
> > > thread. Ultimately I think we should just go ahead and move it and
> > > see if we are all happy with the results. We can make minor changes
> > > to the structure without any problems.
> > >
> > > There are a few things that will have to be sorted out after the
> > > initial phase. One example is unit tests which are kind of scattered.
> > > Things like this which are not totally essential will not be moved.
> > > Before the move I will label the current repository as
> > > (BEFORE_SVN_REORG) or something so that we can always checkout by this
> > > label and see everything in the old layout. Then we can move
> > > individual files that weren't handled in the initial phase on a case
> > > by case basis.
> > >
> > > Also, this will obviously break all of the builds (including the
> > > nightly builds.) I'll start on the new scripts on Friday and
> > > hopefully we'll have things back up and running within a few days.
> > >
> > > I will need lots of help cleaning things up and sorting things out
> > > over the next few days. There is a lot that predates my involvement
> > > in the project and I can only take us so far on my own. I think I
> > > have a handle on the crucial stuff and I did a lot of the work on the
> > > builds so we should be ok as far as the bare minimum stuff.
> > >
> > > Let me know what folks think about this plan.
> > >
> > > sean
> > >
> >
>
>
> --
> Matthias Wessendorf
>
Re: SVN Reorg
Posted by Matthias Wessendorf <mw...@gmail.com>.
Sean,
thanks for taking care on that. I just browsed through the new
structure and it looks very clean. I hope to come back soon...
btw. I just sent my German "isp" a denouncement, since I am waiting
three month and nothing has done... I never!!! choose a *cheap* isp
again. They (mostly) suck!
-Matthias
On 6/22/05, Manfred Geiler <ma...@gmail.com> wrote:
> Sean, thanks for the hard work.
> Unfortunately at the moment I'm under great preasure at my company
> and fear that I cannot be of much help. I will try of course. On
> Saturday morning I will be on the plane to SF for JavaOne. Of course
> we will stay in contact next week, but I cannot promise that I will be
> able to do more than read/answer emails.
>
> -Manfred
>
>
> 2005/6/21, Sean Schofield <se...@gmail.com>:
> > I'd like to start doing the SVN reorg this Thursday. I propose that
> > on Thursday AM, Manfred temporarily disable SVN commit access to all
> > but Manfred and myself. I'll also request that SVN emails be turned
> > off temporarily while we move things. I'll then do the SVN reorg on
> > Thursday and we can reactivate SVN commit and the emails.
> >
> > I've worked everything out in a test SVN repository and the new
> > structure is nearly identical to what was discussed in my earlier
> > thread. Ultimately I think we should just go ahead and move it and
> > see if we are all happy with the results. We can make minor changes
> > to the structure without any problems.
> >
> > There are a few things that will have to be sorted out after the
> > initial phase. One example is unit tests which are kind of scattered.
> > Things like this which are not totally essential will not be moved.
> > Before the move I will label the current repository as
> > (BEFORE_SVN_REORG) or something so that we can always checkout by this
> > label and see everything in the old layout. Then we can move
> > individual files that weren't handled in the initial phase on a case
> > by case basis.
> >
> > Also, this will obviously break all of the builds (including the
> > nightly builds.) I'll start on the new scripts on Friday and
> > hopefully we'll have things back up and running within a few days.
> >
> > I will need lots of help cleaning things up and sorting things out
> > over the next few days. There is a lot that predates my involvement
> > in the project and I can only take us so far on my own. I think I
> > have a handle on the crucial stuff and I did a lot of the work on the
> > builds so we should be ok as far as the bare minimum stuff.
> >
> > Let me know what folks think about this plan.
> >
> > sean
> >
>
--
Matthias Wessendorf
Re: SVN Reorg
Posted by Manfred Geiler <ma...@gmail.com>.
Sean, thanks for the hard work.
Unfortunately at the moment I'm under great preasure at my company
and fear that I cannot be of much help. I will try of course. On
Saturday morning I will be on the plane to SF for JavaOne. Of course
we will stay in contact next week, but I cannot promise that I will be
able to do more than read/answer emails.
-Manfred
2005/6/21, Sean Schofield <se...@gmail.com>:
> I'd like to start doing the SVN reorg this Thursday. I propose that
> on Thursday AM, Manfred temporarily disable SVN commit access to all
> but Manfred and myself. I'll also request that SVN emails be turned
> off temporarily while we move things. I'll then do the SVN reorg on
> Thursday and we can reactivate SVN commit and the emails.
>
> I've worked everything out in a test SVN repository and the new
> structure is nearly identical to what was discussed in my earlier
> thread. Ultimately I think we should just go ahead and move it and
> see if we are all happy with the results. We can make minor changes
> to the structure without any problems.
>
> There are a few things that will have to be sorted out after the
> initial phase. One example is unit tests which are kind of scattered.
> Things like this which are not totally essential will not be moved.
> Before the move I will label the current repository as
> (BEFORE_SVN_REORG) or something so that we can always checkout by this
> label and see everything in the old layout. Then we can move
> individual files that weren't handled in the initial phase on a case
> by case basis.
>
> Also, this will obviously break all of the builds (including the
> nightly builds.) I'll start on the new scripts on Friday and
> hopefully we'll have things back up and running within a few days.
>
> I will need lots of help cleaning things up and sorting things out
> over the next few days. There is a lot that predates my involvement
> in the project and I can only take us so far on my own. I think I
> have a handle on the crucial stuff and I did a lot of the work on the
> builds so we should be ok as far as the bare minimum stuff.
>
> Let me know what folks think about this plan.
>
> sean
>