Skip to content
This repository has been archived by the owner on Feb 8, 2019. It is now read-only.

[PIRK-53] - Fix LICENSE and NOTICE Files for Release Compliance #65

Closed
wants to merge 18 commits into from

Conversation

ellisonanne
Copy link
Contributor

No description provided.

@smarthi
Copy link
Member

smarthi commented Aug 16, 2016

Looks ok to me, but I am no expert in legalese; I would defer to others to comment on this.

@ellisonanne
Copy link
Contributor Author

If you run mvn license:add-third-party you will see the dependencies above - if it appeared in the output, I accounted for it in the files...

subcomponents is subject to the terms and conditions of the following
licenses.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just so there is no misunderstanding here, these LICENSE and NOTICE file changes are only to be included in the exe JAR, that bundles all the 3rd-party dependencies together as a convenience for the end user.

In our single project source JAR (apache-pirk-x.x.x-incubating-sources.jar), and Pirk-only binary (apache-pirk-x.x.x-incubating.jar), these LICENSE/NOTICE modifications must not appear. There will be different LICENSE and NOTICE files for the source and binary artefacts.

Ref: http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused - how do we create different LICENSE and NOTICE files for the different jars when they are built via the release plugin?

@ellisonanne
Copy link
Contributor Author

Just added the licenses directory with the appropriate licenses. Please check. Thanks!

@tellison
Copy link
Member

Where did the licenses/ directory go?

@ellisonanne
Copy link
Contributor Author

Strange... it's back now.

@smarthi
Copy link
Member

smarthi commented Aug 17, 2016

+1 looks good

@ellisonanne
Copy link
Contributor Author

Just updated pom to exclude licenses during RAT checks

@smarthi
Copy link
Member

smarthi commented Aug 17, 2016

+1 Lgtm

@ellisonanne ellisonanne changed the title [PIRK-53] - Fix LICENSE and NOTICE Files for Release Compliance [PIRK-53] [WIP] - Fix LICENSE and NOTICE Files for Release Compliance Aug 17, 2016
@@ -350,6 +350,9 @@
<exclude>docs/*</exclude> <!-- Exclude docs -->
<exclude>logs/*</exclude> <!-- Exclude logs -->
<exclude>**/m2.conf</exclude> <!-- Exclude Maven conf which gets installed on travis and fails RAT check -->
<exclude>src/main/resources/META-INF/bin-license-notice/licenses/*</exclude> <!-- Exclude licenses files -->
<exclude>src/main/resources/META-INF/bin-license-notice/*</exclude>
<exclude>src/main/resources/META-INF/*</exclude>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace these 3 lines by a single line
<exclude>src/main/resources/META-INF/**</exclude>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will do now

@smarthi
Copy link
Member

smarthi commented Aug 18, 2016

+1 to merge, given that most of the feedback has been addressed now.

@ellisonanne ellisonanne changed the title [PIRK-53] [WIP] - Fix LICENSE and NOTICE Files for Release Compliance [PIRK-53] - Fix LICENSE and NOTICE Files for Release Compliance Aug 19, 2016
@asfgit asfgit closed this in 236c23f Aug 21, 2016
@ellisonanne ellisonanne deleted the pirk-53 branch September 7, 2016 16:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants