[ 
https://issues.apache.org/jira/browse/QPID-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-5677:
---------------------------------

    Status: Reviewable  (was: In Progress)

> [Java] update the LICENSE and NOTICE files in various release artifacts
> -----------------------------------------------------------------------
>
>                 Key: QPID-5677
>                 URL: https://issues.apache.org/jira/browse/QPID-5677
>             Project: Qpid
>          Issue Type: Task
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Blocker
>             Fix For: 0.28
>
>
> We currently ship a number of different artifacts for the Java components, 
> such as the project-wide source release, a 'java release' binary, and 
> individual binary archives for e.g. the clients and broker. These all contain 
> LICENSE and NOTICE files. The jar files in those binary archives also count 
> as distributions that themselves contain LICENSE and NOTICE files. This was 
> all further complicated by us previously having jar files in the repository 
> as part of the build process for some time (though removed a while ago).
> During the work on QPID-5048 and updating how the various artifacts are 
> created, and a lot of re-reading 
> https://www.apache.org/dev/licensing-howto.html, it has become apparent that 
> a number of the current artifacts contain extraneous information 
> (particularly the source release and jar files, which often speak to things 
> they do not contain), and some don't contain everything they should.
> This JIRA will serve to add additional distribution-specific LICENSE and 
> NOTICE files, as well as use those already added in QPID-5048, and update the 
> way we package ensure the appropriate information is included in each package 
> depending on its particular contents.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to