GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/1164
NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in
lib
NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in
lib and updating projects to include them as provided where needed.
Not sure of the best direction to take this, but the general thought
process were to treat bcprov and bcpkix as "framework level" dependencies and
include them in lib. This allowed these common, foundational libraries to be
shared by the entirety of the extension space.
I am not a fan of having to add these every place the BC items are
transitively used but did not also want to make a specified dependency in a
parent pom across the entirety of the project.
Before patch:
```
drwxr-xr-x 3 apiri staff 102 Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 608M Oct 27 15:09 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 608M Oct 27 15:08 nifi-1.1.0-SNAPSHOT-bin.zip
```
After patch:
```
drwxr-xr-x 3 apiri staff 102 Oct 27 15:17 nifi-1.1.0-SNAPSHOT-bin
-rw-r--r-- 1 apiri staff 778M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.tar.gz
-rw-r--r-- 1 apiri staff 779M Oct 27 15:18 nifi-1.1.0-SNAPSHOT-bin.zip
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apiri/incubator-nifi nifi-2954
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1164.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 #1164
----
commit bc4b358b477df0cc113b14af02b5f89d0b1b38e5
Author: Aldrin Piri <[email protected]>
Date: 2016-10-27T19:12:39Z
NIFI-2954 - Treating bcprov and bcpkix dependencies as provided by nifi in
lib and updating projects to include them as provided where needed.
----
---
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.
---
