GitHub user dhalperi opened a pull request:
https://github.com/apache/beam/pull/3528
[trivial] pom.xml: add license-maven-plugin and some default license merges
When reviewing the license of third-party dependencies, it's a mess because
the
output is determined by strings people put in their `pom.xml` files rather
than
a standard list.
Use `license-maven-plugin` to clean this up a bit -- each merge defines a
standard name
for the license (the first in the list) followed by a list of variants.
This makes
the output of `mvn license:aggregate-add-third-party` much cleaner.
I was conservative about which licenses I merged - for example, I left
'Apache License'
alone rather than necessarily mapping it to 'The Apache Software License,
Version 2.0',
since there are other versions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dhalperi/beam licensing-fixups
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3528.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3528
----
commit 4560022cd0223cf2ace5df1e278ced4b139ac687
Author: Daniel Halperin <[email protected]>
Date: 2017-07-09T19:02:22Z
pom.xml: add license-maven-plugin and some default license merges
When reviewing the license of third-party dependencies, it's a mess because
the
output is determined by strings people put in their pom.xml files rather
than
a standard list.
Use license-maven-plugin to clean this up a bit -- each merge defines a
standard name
for the license (the first in the list) followed by a list of variants.
This makes
the output of mvn license:aggregate-add-third-party much cleaner.
I was conservatie about which licenses I merged - for example, I left
'Apache License'
alone rather than necessarily mapping it to 'The Apache Software License,
Version 2.0',
since there are other versions.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
