[
https://issues.apache.org/jira/browse/NIFI-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463918#comment-17463918
]
ASF subversion and git services commented on NIFI-9502:
-------------------------------------------------------
Commit d6efc6958536dc2d0bc00de74ecd172e01571aef in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d6efc69 ]
NIFI-9502 Move extension manifest model and parser out of nifi-registry and
into common modules
NIFI-9502 Move ExtensionManifest parser and impl from nifi registry into common
module
NIFI-9502 Add jigsaw profile to nifi-extension-manifest-model in order to build
on Java 11
Add apache license header to test resources
Signed-off-by: Matthew Burgess <[email protected]>
This closes #5619
> Separate extension manifest model from nifi-registry
> ----------------------------------------------------
>
> Key: NIFI-9502
> URL: https://issues.apache.org/jira/browse/NIFI-9502
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In NIFI-9452, there is a new top-level module for nifi-manifest which
> contains sub-modules that produce a C2 RuntimeManifest. We should extract the
> extension manifest model class from nifi-registry-data-model and move them to
> a module under nifi-manifest so they can be shared more easily across nifi
> and nifi-registry. Same thing for the ExtensionManifestParser currently in
> nifi-registry-bundle-utils.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
