[
https://issues.apache.org/jira/browse/NIFI-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245049#comment-16245049
]
ASF GitHub Bot commented on NIFI-4072:
--------------------------------------
GitHub user markobean opened a pull request:
https://github.com/apache/nifi/pull/2258
NIFI-4072 replace keyword RELEASE with actual version number
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:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] 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.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit? single
### For code changes:
- [x] 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?
- [x] 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)?
dependency license is MIT. And this dependency is not new, only version is
specified explicitly now.
- [ ] 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/markobean/nifi NIFI-4072
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2258.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 #2258
----
commit 34fa64ad03d7d3d468c51cc7e5adf735e8a8c390
Author: Mark Bean <[email protected]>
Date: 2017-11-09T01:02:03Z
NIFI-4072 replace keyword RELEASE with actual version number
----
> remove usage of RELEASE from dependency version in pom.xml
> ----------------------------------------------------------
>
> Key: NIFI-4072
> URL: https://issues.apache.org/jira/browse/NIFI-4072
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.3.0
> Reporter: Mark Bean
>
> There are several instances where a dependency version is identified as
> "RELEASE" in the pom.xml. This should be replaced by a specific version for
> reproducible build results. The following pom.xml have been identified as
> containing RELEASE in the current master branch:
> nifi-nar-bundles/nifi-cybersecurity-bundle/nifi-cybersecurity-processors/pom.xml
> nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/pom.xml
> nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/pom.xml
> nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-security/pom.xml
>
> nifi-nar-bundles/nifi-jms-bundle/nifi-jms-processors/pom.xml
> nifi-nar-bundles/nifi-spring/bundle/nifi-spring-processors/pom.xml
> nifi-toolkit/nifi-toolkit-admin/pom.xml
> pom.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
