now and in next year ... [Re: Change CVS module names (Next week)]

[Aleksander Slominski <as...@cs.indiana.edu>]

Davanum Srinivas wrote:

>Folks,
>
>Is everyone ok with these names? It's high time the CVS modules reflect that they belong to the
>webservices project.
>
>xml-axis       ==> ws-axis
>xml-soap       ==> ws-soap
>xml-axis-wsif  ==> ws-wsif
>xml-axis-wsil  ==> ws-wsil
>xml-rpc        ==> ws-rpc
>
>Is there are no objections, we can make the move next week (wed/thu)
>
>Thanks,
>dims
>  
>

hi,

that is a BIG change for lot of people using AXIS and having CVS checked 
out. is it possible to transition this change into two steps:
1. new modules are created but aliases for old modules are still present
2. after _few_ months (next year?) and and multiple announcements that 
include how to convert local CVS module name old modules names are removed.

thanks,

alek

-- 
If everything seems under control, you're just not going fast enough. —Mario Andretti

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Aleksander Slominski <as...@cs.indiana.edu>]

Davanum Srinivas wrote:

>+100000 :)
>  
>
fine with me.

i think we talked about this changes few months ago so it is good that 
it finally happens.

i would like to put a "Whats New" section in http://ws.apache.org/ with 
a pointer to detailed description of what was changed and include as 
much as possible info on how to make changes on windows (without using 
perl ...)

anyway i guess i am too forgiving.

thanks,

alek

>-- dims
>
>--- Sam Ruby <ru...@apache.org> wrote:
>  
>
>>Aleksander Slominski wrote:
>>    
>>
>>>so there are migration paths but still i see no reason to not leave lot 
>>>of time for people to make this change ...
>>>      
>>>
>>My experience with this:
>>
>>1) It actually is real easy to do.  Even on windows (my primary 
>>development platform).
>>
>>2) Those that are prone to whine, will wait until the last minute.
>>
>>3) At which point, they will whine anyway.  Just as loud.
>>
>>My recommendation, for what it is worth:
>>
>>1) rename the cvs trees on the server immediately.  It is one command. 
>>(Actually, two as you want to provide a cvs link for cvspub)
>>
>>2) establish a symbolic link for the old name at the same time (this 
>>time it really is only one command).
>>
>>3) tell people that they symbolic link will stick around for *one week*.
>>
>>4) delete the symbolic link in two weeks.
>>
>>- Sam Ruby
>>
>>
>>
>>
>>    
>>
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
>  
>


-- 
If everything seems under control, you're just not going fast enough. —Mario Andretti

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Davanum Srinivas <di...@yahoo.com>]

+100000 :)

-- dims

--- Sam Ruby <ru...@apache.org> wrote:
> Aleksander Slominski wrote:
> > 
> > so there are migration paths but still i see no reason to not leave lot 
> > of time for people to make this change ...
> 
> My experience with this:
> 
> 1) It actually is real easy to do.  Even on windows (my primary 
> development platform).
> 
> 2) Those that are prone to whine, will wait until the last minute.
> 
> 3) At which point, they will whine anyway.  Just as loud.
> 
> My recommendation, for what it is worth:
> 
> 1) rename the cvs trees on the server immediately.  It is one command. 
> (Actually, two as you want to provide a cvs link for cvspub)
> 
> 2) establish a symbolic link for the old name at the same time (this 
> time it really is only one command).
> 
> 3) tell people that they symbolic link will stick around for *one week*.
> 
> 4) delete the symbolic link in two weeks.
> 
> - Sam Ruby
> 
> 
> 
> 


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Sam Ruby <ru...@apache.org>]

Aleksander Slominski wrote:
> 
> so there are migration paths but still i see no reason to not leave lot 
> of time for people to make this change ...

My experience with this:

1) It actually is real easy to do.  Even on windows (my primary 
development platform).

2) Those that are prone to whine, will wait until the last minute.

3) At which point, they will whine anyway.  Just as loud.

My recommendation, for what it is worth:

1) rename the cvs trees on the server immediately.  It is one command. 
(Actually, two as you want to provide a cvs link for cvspub)

2) establish a symbolic link for the old name at the same time (this 
time it really is only one command).

3) tell people that they symbolic link will stick around for *one week*.

4) delete the symbolic link in two weeks.

- Sam Ruby

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Davanum Srinivas <di...@yahoo.com>]

cvsed is a perl script. Perl is available on windows :)

--- Aleksander Slominski <as...@cs.indiana.edu> wrote:
> Sam Ruby wrote:
> 
> > Aleksander Slominski wrote:
> >
> >> that is a BIG change for lot of people using AXIS and having CVS 
> >> checked out. is it possible to transition this change into two steps:
> >> 1. new modules are created but aliases for old modules are still present
> >> 2. after _few_ months (next year?) and and multiple announcements 
> >> that include how to convert local CVS module name old modules names 
> >> are removed.
> >
> > It is *not* that big of a change. All one generally needs to do is 
> > commit all of one's changes and do a fresh checkout.
> >
> > Two things to note:
> >
> > If you have a large number of existing files modified in an existing 
> > checkout and you are not prepared to commit them, all that you need to 
> > do is to update the various CVS/Root files with the new name. I 
> > typically use Perl to do this, but there are existing tools that can 
> > help, for example:
> > http://cvs-tools.sourceforge.net/cvsed.html
> 
> this is easy on UNIX to do but more tricky in windows - it would be 
> really nice to have such functionality to do switching CVS in windows 
> tool (i would be happy to find out if there is alreayd such tool?!)
> 
> > Alternately, if you can commit your changes, but simply want to obtain 
> > a fresh checkout using a directory name other than the one on the 
> > server, use the -d parameter on the cvs checkout command, for example:
> >
> > cvs -d :ext:aslom@cvs.apache.org:/home/cvs checkout -d xml-axis ws-axis
> 
> i did not try to do this but i believe that it will not work as CVS 
> repository location is encoded in CVS/Repository filse and CVS will not 
> allow to overwrite old locally checked out repository with new reranmed?
> 
> > After either of these are done, you can continue to do cvs updates and 
> > commits normally.
> 
> other possibility is to copy files from old location to a freshly 
> checked out project from new CVS/Root and ignore all CVS/* files during 
> copy (using cygwin find and piping through xargs).
> 
> so there are migration paths but still i see no reason to not leave lot 
> of time for people to make this change ...
> 
> thanks,
> 
> alek
> 
> -- 
> If everything seems under control, you're just not going fast enough. �Mario Andretti
> 
> 


=====
Davanum Srinivas - http://webservices.apache.org/~dims/

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Aleksander Slominski <as...@cs.indiana.edu>]

Sam Ruby wrote:

> Aleksander Slominski wrote:
>
>> that is a BIG change for lot of people using AXIS and having CVS 
>> checked out. is it possible to transition this change into two steps:
>> 1. new modules are created but aliases for old modules are still present
>> 2. after _few_ months (next year?) and and multiple announcements 
>> that include how to convert local CVS module name old modules names 
>> are removed.
>
> It is *not* that big of a change. All one generally needs to do is 
> commit all of one's changes and do a fresh checkout.
>
> Two things to note:
>
> If you have a large number of existing files modified in an existing 
> checkout and you are not prepared to commit them, all that you need to 
> do is to update the various CVS/Root files with the new name. I 
> typically use Perl to do this, but there are existing tools that can 
> help, for example:
> http://cvs-tools.sourceforge.net/cvsed.html

this is easy on UNIX to do but more tricky in windows - it would be 
really nice to have such functionality to do switching CVS in windows 
tool (i would be happy to find out if there is alreayd such tool?!)

> Alternately, if you can commit your changes, but simply want to obtain 
> a fresh checkout using a directory name other than the one on the 
> server, use the -d parameter on the cvs checkout command, for example:
>
> cvs -d :ext:aslom@cvs.apache.org:/home/cvs checkout -d xml-axis ws-axis

i did not try to do this but i believe that it will not work as CVS 
repository location is encoded in CVS/Repository filse and CVS will not 
allow to overwrite old locally checked out repository with new reranmed?

> After either of these are done, you can continue to do cvs updates and 
> commits normally.

other possibility is to copy files from old location to a freshly 
checked out project from new CVS/Root and ignore all CVS/* files during 
copy (using cygwin find and piping through xargs).

so there are migration paths but still i see no reason to not leave lot 
of time for people to make this change ...

thanks,

alek

-- 
If everything seems under control, you're just not going fast enough. —Mario Andretti

Re: now and in next year ... [Re: Change CVS module names (Next week)]

[Sam Ruby <ru...@apache.org>]

Aleksander Slominski wrote:
> 
> hi,
> 
> that is a BIG change for lot of people using AXIS and having CVS checked 
> out. is it possible to transition this change into two steps:
> 1. new modules are created but aliases for old modules are still present
> 2. after _few_ months (next year?) and and multiple announcements that 
> include how to convert local CVS module name old modules names are removed.

It is *not* that big of a change.  All one generally needs to do is 
commit all of one's changes and do a fresh checkout.

Two things to note:

If you have a large number of existing files modified in an existing 
checkout and you are not prepared to commit them, all that you need to 
do is to update the various CVS/Root files with the new name.  I 
typically use Perl to do this, but there are existing tools that can 
help, for example:
http://cvs-tools.sourceforge.net/cvsed.html

Alternately, if you can commit your changes, but simply want to obtain a 
fresh checkout using a directory name other than the one on the server, 
use the -d parameter on the cvs checkout command, for example:

cvs -d :ext:aslom@cvs.apache.org:/home/cvs checkout -d xml-axis ws-axis

After either of these are done, you can continue to do cvs updates and 
commits normally.

> thanks,
> 
> alek

- Sam Ruby