Thanks for pointer to maven-license-plugin. I'll look into adding this
to the build.
Jane
Justin Lee wrote:
> this plugin might help:
> http://code.google.com/p/maven-license-plugin/ I know other projects
> (at apache) have used this or something like it to validate the header
> files. I believe it can introduce build failures similar to a
> surefire test failure.
>
> Bill Shannon wrote:
>> Tim Quinn wrote:
>>> Bill Shannon wrote:
>>>> Carla Carlson wrote:
>>>>> developers are responsible for updating their copyright years. You
>>>>> need to update the year when you
>>>>> update a file.
>>>>
>>>> Where "update the year" means changing
>>>>
>>>> Copyright 2008
>>>>
>>>> to
>>>>
>>>> Copyright 2008-2009
>>>>
>>>> The first copyright year always remains and the last copyright year
>>>> is added or updated.
>>> IANAL, but in general isn't the form a comma-separated list whose
>>> elements are either a single year or a range, with a range
>>> indicating that changes were made in every one of the years in that
>>> range?
>>>
>>> So
>>>
>>> Copyright 2004, 2007-2009
>>> means changes occurred in '04, '07, '08, and '09, which has a
>>> different meaning from
>>>
>>> Copyright 2004-2009
>>>
>>> although I have no idea what the real legal implications would be.
>>
>> IANAL but the last time I talked to one about this they were happy
>> with a range of years. The enumerated list is also acceptable, but
>> generally more work than it's worth to maintain.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>