[
https://issues.apache.org/jira/browse/NIFI-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233691#comment-15233691
]
ASF GitHub Bot commented on NIFI-1747:
--------------------------------------
GitHub user jdye64 opened a pull request:
https://github.com/apache/nifi/pull/340
NIFI-1747 add maven-war-plugin to create jar as part of the existing …
…nifi-web-api build process
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jdye64/nifi NIFI-1747
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/340.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 #340
----
commit 77047b53707cabbc6797397e39557eebf5958e32
Author: Jeremy Dyer <[email protected]>
Date: 2016-04-09T19:24:54Z
NIFI-1747 add maven-war-plugin to create jar as part of the existing
nifi-web-api build process
----
> Build nifi-web-api resource to jar for external use
> ---------------------------------------------------
>
> Key: NIFI-1747
> URL: https://issues.apache.org/jira/browse/NIFI-1747
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Labels: build, maven
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> nifi-web-api classes are built inside of the .war file only. There are
> several instances where these resources would be useful to have available in
> an externally available jar file as well so that other applications can use
> them. I propose adding a maven-war-plugin to the nifi-web-api pom.xml build
> to allow this to happen as part of the existing build process
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
