nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/pom.xml

61 lines
2.7 KiB
XML
Raw Normal View History

2014-12-08 15:22:14 -05:00
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
2014-12-08 15:22:14 -05:00
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.nifi</groupId>
<artifactId>nifi-framework-bundle</artifactId>
<version>1.13.0-SNAPSHOT</version>
2014-12-08 15:22:14 -05:00
</parent>
<artifactId>nifi-framework</artifactId>
2014-12-08 15:22:14 -05:00
<packaging>pom</packaging>
<modules>
<module>nifi-framework-core-api</module>
<module>nifi-client-dto</module>
<module>nifi-nar-utils</module>
<module>nifi-runtime</module>
<module>nifi-site-to-site</module>
<module>nifi-repository-models</module>
<module>nifi-flowfile-repo-serialization</module>
<module>nifi-framework-components</module>
<module>nifi-framework-core</module>
<module>nifi-framework-cluster-protocol</module>
<module>nifi-framework-cluster</module>
<module>nifi-framework-nar-utils</module>
<module>nifi-framework-nar-loading-utils</module>
NIFI-6380: Introduced the notion of Parameters and Parameter Contexts to the code base. - Added nifi-parameter module - Added Parameter to nifi-api - Added ParameterContext and ParameterLookup - Updated EL to support Parameters - Updated backend so that any property can make use of Parameters - Added web endpoint for Parameter Contexts - Updated Templates to make use of Parameter Contexts - Updated Versioned Flows to make use of Parameter Contexts - Updated Stateless NiFi to support Parameters and take Parameters as part of the configuration, not Variables. NIFI-6380: Addressed review feedback and fixed bugs; added additional unit and integration tests to verify NIFI-6380: Added Description to Parameter Context NIFI-6380: Fixed checkstyle violations NIFI-6380: Fixed bug that caused updating a Parameter Context to fail if the name is provided and unchanged NIFI-6380: If parameter is being deleted, don't worry about its sensitivity flag. This addresses a bug where the deletion of a Sensitive Parameter would require that the Parameter be submitted with a value of null and a sensitivity flag of true; else it would provide an error indicating that the parameter can't be changed from sensitive to non-sensitive. Now, the sensitivity flag is ignored. NIFI-6380: Fixed bug around unsetting Process Group's Parameter Context NIFI-6380: Moved lastRefreshed timestamp from ParameterContextDTO to ParameterContextsEntity and renamed to currentTime to match the pattern of ControllerServicesEntity rather than FlowHistory. Added parameterContextId to ProcessGroupFlowDTO NIFI-6380: Added additional integration tests around escaped parameter references NIFI-6380: Additional tests and bug fix for referencing EL from within another EL Expression NIFI-6380: Created ParameterEntity to house a 'canWrite' flag for parameters and updated ParameterContext to use it. Updated ParameterContextUpdateRequestDTO to include a Set<AffectedComponentEntity> indicating the components that are affected by the update NIFI-6380: Addressed review feedback NIFI-6380: Addressed additional review feedback, mostly around code cleanup NIFI-6380: Bug fix NIFI-6380: Addressed more review feedback; fixed a couple of minor bugs encountered when testing NIFI-6380: Bug fix around Parameter escaping for properties that support Expression Language. Fixed inconcsistency in Authorization hierarchy between /parameter-contexts/1234 and /parameter-contexts to ensure that the parent of /parameter-contexts is /controller, regardless of how we arrive at the /parameter-contexts resource NIFI-6380: Fixed but around using ProcessContext#newPropertyValue(String) that previously resulted in causing the Parameters to be evaluated a second time, thereby ignoring escape characters. Updated Integration Test to verify behavior. Also fixed bug in LoadBalanceQueueIT as it was a one-liner and noticed it while running tests to verify other behavior NIFI-6380: Ensure that if Processor or Controller Services references or de-references a Parameter that user making the change has READ policy on the Parameter Context NIFI-6380: Verify permissions on Parameter Context when creating processor/controller service and when moving between groups, insantiating template, reverting/change flow version NIFI-6380: Addressed problem that resulted from rebasing against master; fixed bug in showing the Affected Components for a particular Parameter Context Update NIFI-6380: Fixed NPE that occurs when attempting to update controller-level Controller Service NIFI-6380: Updated validation error text when referencing parameter from controller-level controller service or reporting task NIFI-6380: Ensuring permissions for copy/paste when components reference parameters. NIFI-6380: Do not require READ policy on Parameter Context in order to un-reference a parameter, only to reference one. NIFI-6380: Restricted parameter names to match those in the Feature Proposal. Fixed bug that allowed copy & paste of a PG for which user does not have READ policy for a child/descendant PG's parameter context This closes #3536
2019-05-02 11:33:10 -04:00
<module>nifi-user-actions</module>
<module>nifi-framework-authorization</module>
<module>nifi-framework-authorization-providers</module>
<module>nifi-file-authorizer</module>
<module>nifi-administration</module>
<module>nifi-web</module>
<module>nifi-resources</module>
<module>nifi-documentation</module>
<module>nifi-authorizer</module>
<module>nifi-properties-loader</module>
NIFI-3380 Bumping NAR plugin to 1.2.0-SNAPSHOT development to leverage changes from master, adding buildnumber-maven-plugin to nifi-nar-bundles to properly set build info in MANIFEST of NARs - Refactoring NarDetails to include all info from MANIFEST - Adding the concept of a Bundle and refactoring NarClassLoaders to pass Bundles to ExtensionManager - Adding logic to fail start-up when multiple NARs with same coordinates exist, moving Bundle classes to framework API - Refactoring bundle API to classes and creating BundleCoordinate - Updating FlowController to use BundleCoordinate - Updating the UI and DTO model to support showing bundle details that loaded an extension type. - Adding bundle details for processor canvas node, processor dialogs, controller service dialogs, and reporting task dialogs. - Updating the formating of the bundle coordinates. - Addressing text overflow in the configuration/details dialog. - Fixing self referencing functions. - Updating extension UI mapping to incorporate bundle coordinates. - Discovering custom UIs through the supplied bundles. - Adding verification methods for creating extensions through the rest api. - Only returning extensions that are common amongst all nodes. - Rendering the ghost processors using a dotted border. - Adding bundle details to the flow.xml. - Loading NiFi build and version details from the framework NAR. - Removing properties for build and version details. - Wiring together front end and back end changes. - Including bundle coordinates in the component data model. - Wiring together component data model and flow.xml. - Addressing issue when resolve unvesioned dependent NARs. Updating unit tests to pass based on framework changes - Fixing logging of extension types during start up - Allowing the application to start if there is a compatible bundle found. - Reporting missing bundle when the a compatible bundle is not found. - Fixing table height in new component dialogs. Fixing chechstyle error and increasing test timeout for TestStandardControllerServiceProvider - Adding ability to change processor type at runtime - Adding backend code to change type for controller services - Cleaning up instance classloaders for temp components. - Creating a dialog for changing the version of a component. - Updating the formatting of the component type and bundle throughout. - Updating the new component dialogs to support selecting source group. - Cleaning up new component dialogs. - Cleaning up documentation in the cluster node endpoint. Adding missing include in nifi-web-ui pom compressor plugin - Refactoring so ConfigurableComponent provides getLogger() and so the nodes provide the ConfigurableComponent - Creating LoggableComponent to pass around the component, logger, and coordinate with in the framework - Finishing clean up following rebase. Calling lifecycle methods for add and remove when changing versions of a component - Introducing verifyCanUpdateBundle(coordinate) to ConfiguredComponent, and adding unit tests - Ensuring documentation is available for all components. Including those of the same type that are loaded from different bundles. Adding lookup from ClassLoader to Bundle, adding fix for instance class loading to include all parent NARs, and adding additional unit tests for FlowController - Adding validation to ensure referenced controller services implement the required API - Fixing template instantiation to look up compatible bundle - Requiring services/reporting tasks to be disabled/stopped. - Only supporting a change version option when the item has multiple versions available. - Limiting the possible new controller services to the applicable API version. - Showing the implemented API versions for Controller Services. - Updating the property descriptor tooltip to indicate the required service requirements. - Introducing version based sorting in the new component dialog, change version dialog, and new controller service dialog. - Addressing remainder of the issues from recent rebase. Ensuring bundles have been added to the flow before proposing a flow, and incorporating bundle information into flow fingerprinting - Refactoring the way missing bundles work to retain the desired bundle if available - Fixing logger.isDebugEnabled to be logger.isTraceEnabled - Auditing when user changes the bundle. - Ensuring bundle details are present in templates. Moving standard prioritizers to framework NAR and refactoring ExtensionManager logic to handle cases where an extension is in a JAR directly in the lib directory - Ensuring all nodes attempt to instantiate the same template instance when the available bundles may differ. - Fixing the auditing of copy/paste and template instantiation. - Running addtional verification methods when running standalone. Refactoring controller service invocation handler to allow updating the node used by the invocation handler - Ensuring the bundles in a proposed flow are compatible with the current instance when the current instance has no flow is going to accept the proposed flow - Merging whether multiple versions of the component are available - Setting NAR plugin back to current released version - Cleaning up DocGenerator to not process multiple times Addressing incorrect usage of nf.Common. - Using formatType in the new component type dialogs. Improving error messages when looking for bundles Addressing comments from PR. - Fixing references to global nf namespace. - Fixing injection of nfProcessGroupConfiguration in nfComponentVersion. - Fixing web api integration tests. Not rendering unversioned in help documentation. - Ensuring the isExtentionMissing flag is correct after changing the component type. Adding synchronization in node classes to ensure changing component can't occur when component is running, introducing MissingBundleException for better reporting when a node can't join cluster due to a missing bundle, and bumping NAR plugin to released version 1.2.0 Adding concept of missing components to fingerprinting to ensure nodes agree on missing components when joining a cluster NIFI-3380: NIFI-3520: - Fixing hive nar dependency. - Marking DBCPService as provided. - Skipping services that require instance classloading and are cobundled with their service API. - Skipping components that require instance classloading and reference service APIs that are cobundled. - Addressing UI issues in the new component dialogs when re-opening with a filter applied. Fixing checkstyles issue and adding back assume checks to distributed cache server test Ensuring new component types are sorted correctly when shown initially. This closes #1585.
2017-01-23 10:33:12 -05:00
<module>nifi-standard-prioritizers</module>
<module>nifi-mock-authorizer</module>
<module>nifi-shell-authorizer</module>
<module>nifi-headless-server</module>
2014-12-08 15:22:14 -05:00
</modules>
<dependencies>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</dependency>
</dependencies>
</project>