OK, that's good to know. But I still think we might be going overboard with
this. These files are generated by an IDE. Are we really obligated to attach a
copyright to these files? Are we even legally allowed to do so? We, ourselves,
did not produce the content in those files - Eclipse did. I think this might be
misguided.
On Friday, May 29, 2009, at 09:53AM, "Todd Volkert" <[email protected]> wrote:
>I verified that Eclipse handles them just fine, so there's really no
>harm in including the headers. We have to check in any changes to
>those files when they change, so when we do, it'll be our
>responsibility to keep the license header in there just as we do with
>our source files...
>
>On Fri, May 29, 2009 at 9:47 AM, Greg Brown <[email protected]> wrote:
>> I understand the thinking behind this change, but I'm wondering if it is a)
>> necessary and b) workable. Those files are generated and managed by Eclipse
>> - there's no guarantee that they won't be completely regenerated, minus
>> comments, the next time they change.
>>
>> Mentors - are we going overboard by trying to include headers in absolutely
>> everything (such as IDE-generated configuration files)? To me, this seems a
>> bit excessive.
>>
>>
>>
>>
>
>
