Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] [Bug 249959] [discussion] How to treat copyright headers for checked-in generated sources?

https://bugs.eclipse.org/bugs/show_bug.cgi?id=249959  
Product/Component: Community / Architecture Council




--- Comment #9 from Dave Carver <d_a_carver@xxxxxxxxx>  2008-10-09 09:01:21 -0400 ---
(In reply to comment #8)
> Personally I'd make every effort to include a copyright header that asserted
> the appropriate copyright based on the input to the generator.  I'd do that
> even if the the goal was only to add tags like $Id$ so that the source when
> extracted from CVS would be more traceable to a specific version.  It really
> wouldn't be that all that difficult to write simple SED script that replaces
> all the text before the initial package declaration with a reasonable
> copyright.
> 
> For example, if you have cygwin or are on Linux, use this to visit all the
> *.java files
> 
> for i in $(find src -name "*.java"); do sed -f insert-copyright $i > $i.new; mv
> $i.new $i; done
> 
> The script would look like this:
> 
> 1i\
> /**\
>  * My Copyright\
>  * $Id$\
>  */
> /^package/,$!d
> 
> Given the infrequency of the regeneration, that seems little burden...

Actually even better in this case is just to add that information to the XSD
annotation, or as part of the XJC code injection in the appinfo section.

http://weblogs.java.net/blog/kohsuke/archive/2005/06/

I do agree that something from Legal on what needs to be included from code
generators in the way of copyright statements is a good thing.





-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


Back to the top