Hi Fabian

Tanks for your comment.

I was unaware of this possibility to automatically generate NOTICE
files. I think thanks to this we could remove most of them. For now
I'll check if things work if I just rename the from NOTICE.txt but
leaving them in the current place.

Cheers,
Reto

On Fri, Jan 6, 2012 at 1:22 PM, Fabian Christ
<[email protected]> wrote:
> Hi Reto,
>
> I assume that you want to add additional information to the generated
> NOTICE file. An example how to do this using the apache-release plugin
> can be found here
>
> https://svn.apache.org/repos/asf/incubator/stanbol/trunk/owl
>
> You will find the following file:
>
> src/main/appended-resources/META-INF/NOTICE
>
> The content of this file is automatically appended (by apache-release)
> to the generated NOTICE file. This way you can customize the NOTICE
> files for each module. I think this is a generic mechanism that allows
> you to append additional information to any file in META-INF but I
> have not tested it with other files than NOTICE.
>
> Best,
>  - Fabian
>
> Am 6. Januar 2012 12:04 schrieb Reto Bachmann-Gmür <[email protected]>:
>> On Wed, Jan 4, 2012 at 8:01 PM, Daniel Spicar <[email protected]> wrote:
>>> On 3 January 2012 16:57, Reto Bachmann-Gmür <[email protected]> wrote:
>>>
>>>> >
>>>> > 2) At the root, both NOTICE and NOTICE.txt are present, only one
>>>> > should be there.
>>>> @daniel do you have any idea were the first comes from?
>>>>
>>>
>>> No, I don't even see both of them in the current trunk. Did you change
>>> something to resolve this issue?
>>
>> It seems that NOTICE.txt is added because its in our source tree and
>> NOTICE as per the source assembly descriptor inherited from the
>> parent.
>>
>> Any suggestion on how to fix this? I know little about the assembly
>> plugin. An easy fix would be to remove NOTICE.txt or rename it to
>> NOTICE.
>>
>> Cheers,
>> Reto
>
>
>
> --
> Fabian
> http://twitter.com/fctwitt

Reply via email to