cvs commit: ws-site LICENSE.txt
tetsuya 2003/09/05 21:42:48 Modified:.LICENSE.txt Log: CRCRLF (\x0D\x0D\x0A) - CRLF (\x0D\x0A) Revision ChangesPath 1.2 +48 -48ws-site/LICENSE.txt Index: LICENSE.txt === RCS file: /home/cvs/ws-site/LICENSE.txt,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- LICENSE.txt 22 Jan 2003 22:51:15 - 1.1 +++ LICENSE.txt 6 Sep 2003 04:42:48 - 1.2 @@ -1,48 +1,48 @@ -/* - * The Apache Software License, Version 1.1 - * - * - * Copyright (c) 2003 The Apache Software Foundation. All rights - * reserved. - * - * Redistribution and use in source and binary forms, with or without - * modification, are permitted provided that the following conditions - * are met: - * - * 1. Redistributions of source code must retain the above copyright - *notice, this list of conditions and the following disclaimer. - * - * 2. Redistributions in binary form must reproduce the above copyright - *notice, this list of conditions and the following disclaimer in - *the documentation and/or other materials provided with the - *distribution. - * - * 3. The end-user documentation included with the redistribution, - *if any, must include the following acknowledgment: - * This product includes software developed by the - *Apache Software Foundation (http://www.apache.org/). - *Alternately, this acknowledgment may appear in the software itself, - *if and wherever such third-party acknowledgments normally appear. - * - * 4. The name Apache Software Foundation must - *not be used to endorse or promote products derived from this - *software without prior written permission. For written - *permission, please contact [EMAIL PROTECTED] - * - * 5. Products derived from this software may not be called Apache, - *nor may Apache appear in their name, without prior written - *permission of the Apache Software Foundation. - * - * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED - * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES - * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE - * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR - * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, - * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT - * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF - * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND - * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, - * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT - * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF - * SUCH DAMAGE. - */ +/* + * The Apache Software License, Version 1.1 + * + * + * Copyright (c) 2002-2003 The Apache Software Foundation. All rights + * reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * + * 1. Redistributions of source code must retain the above copyright + *notice, this list of conditions and the following disclaimer. + * + * 2. Redistributions in binary form must reproduce the above copyright + *notice, this list of conditions and the following disclaimer in + *the documentation and/or other materials provided with the + *distribution. + * + * 3. The end-user documentation included with the redistribution, + *if any, must include the following acknowledgment: + * This product includes software developed by the + *Apache Software Foundation (http://www.apache.org/). + *Alternately, this acknowledgment may appear in the software itself, + *if and wherever such third-party acknowledgments normally appear. + * + * 4. The name Apache Software Foundation must + *not be used to endorse or promote products derived from this + *software without prior written permission. For written + *permission, please contact [EMAIL PROTECTED] + * + * 5. Products derived from this software may not be called Apache, + *nor may Apache appear in their name, without prior written + *permission of the Apache Software Foundation. + * + * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED + * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE + * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR + * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, + * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT + * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
cvs commit: ws-site/src/documentation skinconf.xml
tetsuya 2003/09/05 21:48:56 Modified:src/documentation skinconf.xml Log: copyright statement: 2002 - 2002-2003 Revision ChangesPath 1.3 +1 -1 ws-site/src/documentation/skinconf.xml Index: skinconf.xml === RCS file: /home/cvs/ws-site/src/documentation/skinconf.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- skinconf.xml 24 Jan 2003 16:39:27 - 1.2 +++ skinconf.xml 6 Sep 2003 04:48:56 - 1.3 @@ -69,7 +69,7 @@ host-logo/host-logo !-- The following are used to construct a copyright statement -- - year2002/year + year2002-2003/year vendorThe Apache Software Foundation./vendor !-- Some skins use this to form a 'breadcrumb trail' of links. If you don't
cvs commit: ws-site/targets/axis toc.html
tetsuya 2003/09/05 21:46:16 Modified:targets/axis toc.html Log: copyright statement: 1999-2001- 1999-2003 -- and added (double quote) Revision ChangesPath 1.7 +2 -2 ws-site/targets/axis/toc.html Index: toc.html === RCS file: /home/cvs/ws-site/targets/axis/toc.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- toc.html 31 Aug 2003 05:01:49 - 1.6 +++ toc.html 6 Sep 2003 04:46:16 - 1.7 @@ -43,8 +43,8 @@ br br br -ifont size=-2 -Copyright © 1999-2001 +ifont size=-2 +Copyright #169; 1999-2003 br Apache Software Foundation /font/i
now and in next year ... [Re: Change CVS module names (Next week)]
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 w eek)]
I agree with Alek, if we can do this in stages that will make life a lot easier for many people. --Glen 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: Change CVS module names (Next week)
Davanum Srinivas wrote: xml-rpc== ws-rpc That particular one should either be ws-xmlrpc or ws-xml-rpc. - Sam Ruby
Re: now and in next year ... [Re: Change CVS module names (Next week)]
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:[EMAIL PROTECTED]:/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
Re: now and in next year ... [Re: Change CVS module names (Next week)]
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:[EMAIL PROTECTED]:/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)]
cvsed is a perl script. Perl is available on windows :) --- Aleksander Slominski [EMAIL PROTECTED] 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:[EMAIL PROTECTED]:/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: Change CVS module names (Next week)
+1. --- Daniel Rall [EMAIL PROTECTED] wrote: Sam Ruby wrote: Davanum Srinivas wrote: xml-rpc== ws-rpc That particular one should either be ws-xmlrpc or ws-xml-rpc. Considering the canonical URL namespace (http://ws.apache.org/xmlrpc/) and the mailing list names ([EMAIL PROTECTED]), ws-xmlrpc would be more consistent. - Dan = Davanum Srinivas - http://webservices.apache.org/~dims/
Re: now and in next year ... [Re: Change CVS module names (Next week)]
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)]
+10 :) -- dims --- Sam Ruby [EMAIL PROTECTED] 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)]
Davanum Srinivas wrote: +10 :) 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 [EMAIL PROTECTED] 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: cvs commit ws-site/src/documentation/content/xdocs cvs.xml
On Sat, 06 Sep 2003 12:41:21 -0700 (Subject: Re: cvs commit: ws-site/src/documentation/content/xdocs cvs.xml) Daniel Rall [EMAIL PROTECTED] wrote: xml-rpc needs to retain the xml -- it's part of the technology's name. We could add a ws- prefix, making it ws-xml-rpc, but should use a symlink for a deprecation period to allow people time to switch over. - Dan Quite. Agree with you. ws-xmlrpc might make sense. I am not a PMC member of ws, however, what about asking some graduated projects from xml/jakarta ... i mean, james/cocoon/ant/avalon etc... about how to switch over the repository ?? It seems that the ASF lacks a bit the inheritance of experience and knowledge from the others. -- Tetsuya. ([EMAIL PROTECTED])
Re: cvs commit: ws-site/targets/skin/images printer.gif
I've forgot to mention: On 6 Sep 2003 14:15:06 - (Subject: cvs commit: ws-site/targets/skin/images printer.gif) [EMAIL PROTECTED] wrote: tetsuya 2003/09/06 07:15:06 Modified:targets contact.html contact.pdf cvs.html cvs.pdf index.html index.pdf legal.html legal.pdf library.html library.pdf mail.html mail.pdf mirrors.html news.html news.pdf overview.html overview.pdf todo.html todo.pdf targets/skin breadcrumbs.js targets/skin/images printer.gif Log: Publish: Copyright Notice Change etc. snip/ -a href=mirrors.cgiDownloads/a +a href=mirrors.htmlDownloads/a I re-wrote the .htaccess file in order to redirect from http://ws.apache.org/mirrors.html to http://ws.apache.org/mirrors.cgi Just FYI: -- Tetsuya. ([EMAIL PROTECTED])
Re: cvs commit ws-site/targets/skin/images printer.gif
Thanks dims. I often use forrest site not ant when building perticular sites. :) By the way, it seems that the Forrest Team will announce the release of Forrest 0.5 within a few days. As I wrote @ forrest-dev mailing list, personally I like the krysalis-site skin of Forrest 0.4, however, it seems that I can not ant using Forrest 0.4 correctly. What do you think about the upgrade of Apache Forrest? -- Tetsuya. ([EMAIL PROTECTED]) On 7 Sep 2003 02:35:06 - (Subject: cvs commit: ws-site/targets/skin/images printer.gif) [EMAIL PROTECTED] wrote: dims2003/09/06 19:35:06 Modified:targets contact.html cvs.html index.html legal.html library.html mail.html mirrors.html news.html overview.html todo.html contact.pdf targets/skin/images printer.gif Log: run ant from the ws-site directory (fixes mirrors.html) snip/
