[
https://issues.apache.org/jira/browse/NIFI-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255143#comment-15255143
]
ASF GitHub Bot commented on NIFI-1747:
--------------------------------------
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/340#issuecomment-213666528
Hey @jdye64! This certainly seems to make sense, but not sure I am a fan
of the classifiers route. Would specifying a separate execution for the build,
such as:
``` xml
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<id>create-jar</id>
<phase>compile</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
```
This would be easier to rely on from a dependency standpoint in lieu of
having to do additionally specify a classifier in the pom descriptor.
> 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)
