NOTICE/LICENSE file issues

[Felix Meschberger <fm...@gmail.com>]

Hi all,

Once again, we had a mid-air collision while working on NOTICE files: I
prepared the metatype service release, while Richard was updating the
copyright years of included OSGi packages ...

The question was raised, whether the management of the NOTICE and
LICENSE files could be automated with the uses of the Maven Remote
Resources plugin ?

What do the Maven and Release specialist out there think of this approach ?

Thanks and Regards
Felix

PS: For the Metatype service release, I think this is not really very
important since the release was built with old dependencies and the
ServiceTracker included comes from these old dependencies (R4.0
librarires IIRC).

Re: NOTICE/LICENSE file issues

["Richard S. Hall" <he...@ungoverned.org>]

On 7/31/09 10:06 AM, Felix Meschberger wrote:
> Hi all,
>
> Once again, we had a mid-air collision while working on NOTICE files: I
> prepared the metatype service release, while Richard was updating the
> copyright years of included OSGi packages ...
>
> The question was raised, whether the management of the NOTICE and
> LICENSE files could be automated with the uses of the Maven Remote
> Resources plugin ?
>
> What do the Maven and Release specialist out there think of this approach ?
>    

At a minimum, it would be nice if we could somehow simply have a 
property that we put in our NOTICE file, like ${OSGiR4}, ${OSGiR4.1}, 
${OSGiR4.2}, ${KXML2}, etc. Then we could just mention which ones we use 
and make sure they get the correct text. Obviously, it would be even 
better if it could pick this up from the dependencies and do it 
automatically. The tricky part would be to get it to know if it should 
be 'included' or 'used'.

> PS: For the Metatype service release, I think this is not really very
> important since the release was built with old dependencies and the
> ServiceTracker included comes from these old dependencies (R4.0
> librarires IIRC).
>    

Yeah, I didn't realize you were in the middle of a release, sorry. Nor 
did I see that you didn't update the dependency, so I just reverted my 
change.

-> richard