Re: Updating licenses
Very cool! I did the whole thing manually back when I exchanged the illegal short licence with the long one. But I noticed the following: http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/java/org/apache/fop/area/inline/InlineArea.java?rev=1.2.2.1 It looks like the {YEARS} marker seems not to have worked on some files you checked in yesterday. On 30.01.2004 00:00:46 Peter B. West wrote: Fops, I have committed the perl script bin/lic_to_2 in FOP_0-20-0_Alt-Design. It's function is to substitute license 2.0 for 1.1. It is called as $ lic_to_2 --lic2 {file containing license 2.0 text} {file to modify} The intended usage is something like: $ find . -name '*java'|while read file;\ mv $file $file.orig;\ do lic_to_2 --lic2 {lic2 file} $file.orig $file;\ done I have already committed java and plain text versions of 2.0 to the root directory of FOP_0-20-0_Alt-Design. Note that these license files contain a {YEARS} marker which is replaced from the actual years in the source file copyright notice when the script is run. When we get the OK, I'll use this to update the licenses in alt-design, and, if that works, I can also do the maint and HEAD sources. Jeremias Maerki
Re: Updating licenses
Jeremias Maerki wrote: Very cool! I did the whole thing manually back when I exchanged the illegal short licence with the long one. But I noticed the following: http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/src/java/org/apache/fop/area/inline/InlineArea.java?rev=1.2.2.1 It looks like the {YEARS} marker seems not to have worked on some files you checked in yesterday. Ahem... That's because I cut-and-pasted the 2.0 license file into the pattern Eclipse uses when constructing a new class. I forgot to fix {YEARS}. Those new files haven't been run through the perl filter. Thanks for picking this up, Jeremias. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Updating licenses
Fops, I have committed the perl script bin/lic_to_2 in FOP_0-20-0_Alt-Design. It's function is to substitute license 2.0 for 1.1. It is called as $ lic_to_2 --lic2 {file containing license 2.0 text} {file to modify} The intended usage is something like: $ find . -name '*java'|while read file;\ mv $file $file.orig;\ do lic_to_2 --lic2 {lic2 file} $file.orig $file;\ done I have already committed java and plain text versions of 2.0 to the root directory of FOP_0-20-0_Alt-Design. Note that these license files contain a {YEARS} marker which is replaced from the actual years in the source file copyright notice when the script is run. When we get the OK, I'll use this to update the licenses in alt-design, and, if that works, I can also do the maint and HEAD sources. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Re: Updating licenses
--- Peter B. West [EMAIL PROTECTED] wrote: When we get the OK, I'll use this to update the licenses in alt-design, and, if that works, I can also do the maint and HEAD sources. Sounds quite good. You've made *many* friends today... ;) Glen __ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/
Re: Updating licenses
Glen Mazza wrote: --- Peter B. West [EMAIL PROTECTED] wrote: When we get the OK, I'll use this to update the licenses in alt-design, and, if that works, I can also do the maint and HEAD sources. Sounds quite good. You've made *many* friends today... ;) But Glen, I have *so* many already. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html