[
https://issues.apache.org/jira/browse/NIFI-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016832#comment-16016832
]
ASF GitHub Bot commented on NIFI-3940:
--------------------------------------
GitHub user joewitt opened a pull request:
https://github.com/apache/nifi/pull/1827
NIFI-3940 upgraded to latest jruby which resolves an apparent lgpl bu…
…nding issue
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joewitt/incubator-nifi NIFI-3940
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1827.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 #1827
----
commit a7432f257ad09d73b724e69ed520ab8627935d9c
Author: joewitt <[email protected]>
Date: 2017-05-19T02:57:49Z
NIFI-3940 upgraded to latest jruby which resolves an apparent lgpl bunding
issue
----
> older jruby-complete artifacts contained LGPL code
> --------------------------------------------------
>
> Key: NIFI-3940
> URL: https://issues.apache.org/jira/browse/NIFI-3940
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.2.0
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Priority: Blocker
> Fix For: 1.3.0
>
>
> From Mike Drob's report to legal
> Legal,
> I recently got done working with the JRuby dev team on an issue where they
> were inadvertently including LGPL code in the jruby-complete jar for versions
> 9.0.0.0 - 9.1.8.0.
> I'm not sure if we have a good mechanism for tracking which projects are
> using/bundling JRuby, but it would be good to let them know that they should
> consider updating for license reasons.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
