[
https://issues.apache.org/jira/browse/NIFI-13354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853260#comment-17853260
]
ASF subversion and git services commented on NIFI-13354:
--------------------------------------------------------
Commit 406dbced3bcc72de8e417bac70b9d86ccdf0fbee in nifi's branch
refs/heads/main from Matt Gilman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=406dbced3b ]
NIFI-13354: (#8936)
- Moving NiFi front end source into a top level maven module. This prepares for
the introduction of other UIs that NiFi offers (like Custom UIs, Data Viewers,
etc) to be colocated and share common components, styles, and dependencies.
- The nifi-web-frontend module which produces the war that is included in the
server nar now no longer contains any source. It simply depends on the new
nifi-frontend artifact that bundles all built UIs and unpacks its contents into
the resulting war.
- Renaming nifi-web-frontend to nifi-ui. Now nifi-frontend at the top level
will hold all frontend apps. In this commit the nifi app in nifi-frontend is
bundled into a war called nifi-ui.
This closes #8936
> Prepare frontend codebase for co-location with other UIs
> --------------------------------------------------------
>
> Key: NIFI-13354
> URL: https://issues.apache.org/jira/browse/NIFI-13354
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> NiFi is comprised of numerous UIs. These UIs exist within different maven
> modules because of they live in different parts of the codebase and they are
> packaged in different NARs. This is makes it difficult to reuse shared
> components, styles, dependencies, etc.
> This Jira is tracking the migration of the recently rewritten NiFi UI to a
> top level maven module. This will establish a place where subsequent UIs
> (custom UIs, documentation, data viewers, etc) can be added. Once all the UIs
> have been updated, we will be left with a single maven module that produces a
> single artifact of all built UIs. The existing WARs which currently package
> the UIs will be responsible for unpacking the front end artifact and copying
> the applications into the WAR staging directory.
> In the end, we'll have a single place for all UIs to be colocated where they
> can easily share reusable components and styles. Further it will be a single
> place for front end dependencies to be managed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
