[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208603#comment-13208603
 ] 

Patrick Hunt commented on BOOKKEEPER-145:
-----------------------------------------

You don't want to do this. At least not like this patch.

I'm assuming you will have 1 source artifact plus 0 or more binary artifacts. 
You'll have the same issue, but in reverse - you don't want your source 
artifact to have a notice/license for things that are not included. On the 
other hand you do want your binary license/notice to include this.

two options I can see:

1) see how whirr does this, http://svn.apache.org/viewvc/whirr/trunk/

it has two notice files, one for bin one for source. this should work fine as 
long as you have homogeneous binaries. Although I would think you want a 
stripped down NOTICE.TXT/license and NOTICE-bin.txt/LICENSE-bin.txt instead of 
src. Then you pull the right file into the archive during the packaging.

2) generate the notice/license on the fly. 

see this:
https://issues.apache.org/jira/browse/OPENJPA-880

or this:
https://wiki.jasig.org/display/LIC/maven-notice-plugin 

(probably other options as well).

I'm not very familiar with 2, but I'd suggest you go this route - it will make 
your life easier in the long run.

                
> Put notice and license file for distributed binaries in SVN
> -----------------------------------------------------------
>
>                 Key: BOOKKEEPER-145
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-145
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-145.diff
>
>
> During the 4.0.0 I manually put these in the binary tarballs. This is awkward 
> though. It's easier just to have them in the source tree.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to