Deprecate old MD-SAL APIs for removal These APIs are slated for removal in Aluminium, make sure our warning is more stern. JIRA: CONTROLLER-1917 Change-Id: Ib4f7dcfd5183b87dd10b9ce2b773a59a548892c9 Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Fix checkstyle/spotbugs violations Enabling checkstyle/spotbugs by default finds these, fix them up. Change-Id: Ib407830f0a15cb4c04492f3c694fb463cdb30bad Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Integrate MRI projects for Neon This patch bumps: - odlparent to 4.0.2 - yangtools to 2.1.2 - mdsal to 3.0.1 It also deals with: - DOMRpcError.getErrors() changing - java.util.Optional being used in MD-SAL - xmlunit upgrade via xmlunit-legacy - any(Class) not matching nulls - lists disappearing and hence requiring at least one item - remove explicit <null/> in blueprints, as that breaks blueprint-core - adjust sal-binding-it to include byte-buddy, which is a mockito dependency - adjust dependencies to account for ietf-{inet,yang}-types movement - moving to tech.pantheon.triemap - mdsal.common.api removals JIRA: CONTROLLER-1860 Change-Id: I31b2d011015846537a99f963ded1d38e7b29d71e Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Remove logback related stuff as discussed on https://lists.opendaylight.org/pipermail/odlparent-dev/2017-July/001262.html ' Change-Id: I09146cd363d1ab706143bc12c8b1e37aa96c8723 Signed-off-by: Michael Vorburger <vorburger@redhat.com>
BUG-7464: use yangtools.triemap Yangtools is moving away from using upstreap Triemap to its internal fork of that codebase. Switch this code, too. Change-Id: I0d60ccc8927505a83a35631333203817484da9e0 Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Fix missing bundle Change-Id: I9b8c0ca660e0101a2459f92dd16e36727f8ab9c3 Signed-off-by: Robert Varga <robert.varga@pantheon.sk>
BUG-2625: fix failures with Java 8-targetted artifacts This patch bumps to use equinox 3.9.1 and removes the use of mockito-all, fixing failures seen with source/target set to Java 8 Change-Id: I6964633e2c6b0de934045522c8f245fdb66901da Signed-off-by: Robert Varga <rovarga@cisco.com>
Deprecate TestHelper This shouldn't be used any more (certainly not for new IT suites). Change-Id: Iaf4a9c71f978303b8daa1f104175618bc2529b8e Signed-off-by: Stephen Kitt <skitt@redhat.com>
Remove antlr4-runtime-osgi-nohead This bundle was removed from yangtools so no longer exists. See: https://git.opendaylight.org/gerrit/28272/ Change-Id: I5871ce5a21f01f8b414df14fbf160708f2b805e8 Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org> Signed-off-by: Stephen Kitt <skitt@redhat.com>
Bug 4202: Migration to use mdsal project Migrated controller to use MD-SAL provided Java Binding instead of YANG-Tools provided JAVA Binding. This migration deals only with compile time and in runtime. Updated following features - features-config - features-config-netty - features-config-persister - features-mdsal - features-extras - features-protocol-framework to use - Java Binding hosted in MD-SAL project - features-parent from odlparent Change-Id: Iba40d74d118e212c9a57fa28711bbbe339fe1bbd Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Bug 4035: Removed sal-common which is unused since Helium. Change-Id: Ia6e15cc1e94fcf5794a56fbf61d260644dcb457b Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Bug 4035: Extract dom-config from core-api and broker-impl This patch introduces two new artefacts sal-dom-config and sal-dom-broker-config which hosts all config subsystem related MD-SAL DOM Broker implementation. This patch is required for MD-SAL split in order to not have cyclic dependency between controller and md-sal project. Change-Id: Ic93c583c07ae3e088dcf0e74cbdaaf627a8e79f6 Signed-off-by: Tony Tkacik <ttkacik@cisco.com>
Decouple config and netconf subsystems. Extract a common mapping for config pusher and config subsystem netconf Add a ConfigPersisterFacade for XML that allows reads/writes from/to config subsystem using XML format Push notifications from YangStoreService to NetconfNotificationManager instead of using custom listeners Migrate netconf features from controller features, untangle features Change-Id: I71e4ca6e0258e0b1f0d6c19119f93eb9d68b7bca Signed-off-by: Tomas Cere <tcere@cisco.com> Signed-off-by: Maros Marsalek <mmarsale@cisco.com> Signed-off-by: Ed Warnicke <hagbard@gmail.com>
BUG 2458: Bump nagasena version to 2.53.0 Change-Id: I77e21237355cee3973a05a37981ab49a05018bf9 Signed-off-by: Tomas Cere <tcere@cisco.com> Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
Make sure to pull trie library This library is no longer embedded in yangtools, so we need to pull it in. Change-Id: I1a6daeae653508f0b177b6ec70e3f7b23c6748ec Signed-off-by: Robert Varga <rovarga@cisco.com>
BUG-2637: migration final - cleanup - remove migrated features (feature-flow, odl-adsal-compatibility) - remove migrated apps (model-flow*, sal-compatibility, sm, im, tp, frm) - remove temporary fix in toaster-it Change-Id: Ida315250f0035e09aa2e2afd0f8df076d9770861 Signed-off-by: Michal Rehak <mirehak@cisco.com>
Revert "BUG-2637: migrate features" This reverts commit 300d247c3c68387bf0bed3fc9dd90558ebe01f3f. 300d247c3c68387bf0bed3fc9dd90558ebe01f3f broke because the flow-features were not migrated properly to openflowplugin. Change-Id: I6502a93b10b4c5ee41d037da216092cdf003d17f Signed-off-by: Ed Warnicke <eaw@cisco.com>
BUG-2637: migrate features - remove migrated features - integration test fix: - commented out dependencies to models affected by migration - adapted sal-binding-it in order not to push those models into pax-exam context - adapted sal-binding-broker-impl to use those models only in test scope - cleaned commented code/config Change-Id: I8e09a7cd9ff9ba0f041abe1bf739be755aed3e8d Signed-off-by: Michal Rehak <mirehak@cisco.com>
BUG-2600 Dynamic schemas in netconf server Netconf server does not preserve snapshots of schema contexts for each netconf session anymore Every netconf session is using current SchemaContext + Use notification manager to notify about capability changes Change-Id: Ie47125e1eb6851b54b09d5e4afe38fee323850de Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
BUG-2288: implement DOMNotificationRouter Implements DOMNotification(Publish)Service using LMAX Disruptor. The disruptor is used internallly to transfer requests from publishers to two-stage notification dispatch, where the frist stage takes care of delivering events to subscribers and the second stage notifies the futures. Change-Id: I654d9d044e80b2a2ff6fd5b05ddceed4e79a4ebc Signed-off-by: Robert Varga <rovarga@cisco.com>