You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/12 16:56:00 UTC

[jira] [Commented] (NIFI-5859) Update NAR maven plugin to include information about Extensions

    [ https://issues.apache.org/jira/browse/NIFI-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766238#comment-16766238 ] 

ASF subversion and git services commented on NIFI-5859:
-------------------------------------------------------

Commit 7278a3970d0a397564dd08dd89c770d6d14820ae in nifi's branch refs/heads/master from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7278a39 ]

NIFI-5859 Add nifi-api dependency to nifi-jetty-bundle pom so the NAR Maven plugin will know the api version

Signed-off-by: Kevin Doran <kd...@apache.org>

This closes #3291.


> Update NAR maven plugin to include information about Extensions
> ---------------------------------------------------------------
>
>                 Key: NIFI-5859
>                 URL: https://issues.apache.org/jira/browse/NIFI-5859
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Tools and Build
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> In order to have the NiFi Registry host any extensions, the registry will need a way to know what extensions exist in a given NAR. Currently, that information is not available directly.
> The NAR maven plugin should be updated to provide a list of extensions and for each one, provide at least the following minimal information:
>  * Extension Type
>  * Extension Name
>  * Capability Description
>  * Whether or not the component is Restricted, "sub-restrictions" it has, and explanations of both
>  * Any Tags that the component has
>  * If the component is a Controller Service, any Controller Service API's that it provides
> Additionally, it would be ideal to provide all documentation for the component within the NAR. It is best, though, not to write the documentation in HTML as is done now but rather in XML or some sort of form that provides the information in a structured way without any styling. This would allow the documentation to be rendered consistently, even if the styling changes from 1 version to the next.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)