lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Haxby (JIRA)" <>
Subject [jira] Commented: (LUCENE-497) update copyright (and licence) prior to release of 1.9
Date Wed, 15 Feb 2006 10:52:09 GMT
    [ ] 

John Haxby commented on LUCENE-497:

It's not as if I'm a lawyer either or what I say is likely to carry much weight, but what
Yonik and Erik say matches what the legal people at my previous employer (HP) said -- don't
change the copyright date unless the file has changed.

The underlying reason, it was explained to me, is that if you blindly claim copyright for
years when you didn't do anything then a judge (if it came down to that) is going to take
the view that your copyright notices don't actually have much value.   It's not, they said,
the actual form of the copyright notice its convincing a judge that you do hold the copyright.
  To that end, I asked, a good copyright notice is a help and a bad copyright notice is a
hindrance.   Yes, came the answer.

> update copyright (and licence) prior to release of 1.9
> ------------------------------------------------------
>          Key: LUCENE-497
>          URL:
>      Project: Lucene - Java
>         Type: New Feature
>     Reporter: Hoss Man
>     Priority: Minor

> As discussed in email earlier today, it wouldn't hurt to update the Copyright on all
of the source files before release 1.9.
> Rather then try to submit a path with all the changes, here's a oneliner that should
work on any unix box to update in mass.  If it sees a Copyright string it recognizes, it preserves
the start year and adds/replaces the end year...
> find -name \*.java | xargs perl -pi -e 's/Copyright (\(c\) )?(200[0-5])(-\d+)? (The )?Apache
Software Foundation/Copyright ${2}-2006 The Apache Software Foundation/;'
> would make sense for someone with commit permissions to run that themselves.
> It also cleans up a few that have a " (c) " in them that doesn't seem standard across
the rest of the files, and makes sure that the ASF is refered to as "The" ASF.
> Even after all that, there are a few that may need cleaned up by hand...
> ./src/test/org/apache/lucene/store/ * Copyright (c) 2001,2004 The Apache
Software Foundation.  All rights
> ./src/test-deprecated/org/apache/lucene/index/ * Copyright 2004.  Center
For Natural Language Processing
> ./contrib/analyzers/src/java/org/apache/lucene/analysis/cn/ * Copyright:
  Copyright (c) 2001
> ./contrib/analyzers/src/java/org/apache/lucene/analysis/cn/ * Copyright:
   Copyright (c) 2001
> ./contrib/analyzers/src/java/org/apache/lucene/analysis/cn/ * Copyright:
  Copyright (c) 2001
> ...the first is just an anoying format, the rest either have non ASF copyrights, or dual
copyrights (!?)
> It also may be a good time to take a look at all the (non-JavaCC generated) java files
that don't mention the Apache License, Version 2.0 ...
> @asimov:~/svn/lucene/java$ find src -name \*.java | xargs grep -L "Generated By:JavaCC"
| xargs grep -L LICENSE-2.0
> src/java/org/apache/lucene/search/
> src/java/org/apache/lucene/search/
> src/test/org/apache/lucene/index/
> src/test/org/apache/lucene/index/
> src/test/org/apache/lucene/index/
> src/test/org/apache/lucene/index/
> src/test/org/apache/lucene/store/
> src/test/org/apache/lucene/store/
> src/test/org/apache/lucene/search/
> src/test/org/apache/lucene/
> src/test/org/apache/lucene/document/
> src/test/org/apache/lucene/analysis/
> src/test-deprecated/org/apache/lucene/index/
> src/test-deprecated/org/apache/lucene/index/store/
> src/test-deprecated/org/apache/lucene/index/
> src/test-deprecated/org/apache/lucene/index/
> src/test-deprecated/org/apache/lucene/index/
> src/test-deprecated/org/apache/lucene/search/

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message