Remove CSS code JIRA: TSC-111 Change-Id: Ib74c1d3dfc029c2472b8834ae55ce05c8231d225 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Adjust to yangtools-2.0.0 changes Change-Id: Ib86747e5ed19c0c00bb46b8d7e4936f4d90c4364 Signed-off-by: Robert Varga <robert.varga@pantheon.tech> Signed-off-by: Stephen Kitt <skitt@redhat.com>
config-util: use lambdas This series of patches uses lambdas instead of anonymous classes for functional interfaces when possible. Lambdas are replaced with method references when appropriate. Change-Id: Iac5970f81ff50b5b9358eecfc1529d8102f1b22e Signed-off-by: Stephen Kitt <skitt@redhat.com>
config-util: final parameters This automatically-generated patch flags all appropriate parameters as final (including caught exceptions). Change-Id: Ic60c96d83aa19cd7e5adeaf9a7422d26713b326f Signed-off-by: Stephen Kitt <skitt@redhat.com>
Bug 7180 - error-severity and error-type values should be lowercase Add String value fields to ErrorSeverity and ErrorType enums that contain lowercase names of enums. Enums' string value getter methods return these lowercase values. Change-Id: I1509a7bbae4811025a5bbba11e9b2f0c0cc75b50 Signed-off-by: Jakub Morvay <jmorvay@cisco.com>
Refactor DocumentedException class Deprecate ErrorType and ErrorSeverity getTagValue methods. Add new replacement getTypeValue and getSeverityValue methods respectively. Change-Id: If7915c65e72a26bfd6c676bb17c94c896cc0c5e2 Signed-off-by: Jakub Morvay <jmorvay@cisco.com>
Revert "Clean-up pom.xml layout" Since this got merged, I'm facing issue building the project correctly, it's failing in samples/toaster-it and runtime is broken because of mess-up classpath. If others are facing the same issue, this should be merged. I'll rework the overall patch later. This reverts commit 8a637013c102c11323230dae08fa4407863945d6. Change-Id: I61aae87439736d0163e6b4c49d8753052b28bac0 Signed-off-by: Alexis de Talhouët <adetalhouet@inocybe.com>
Bug 6918: Edit ErrorSeverity and ErrorType from() method to accept lowercase strings Change-Id: Ifbf4e3447ccd65bf476df3477e63c95748d52493 Signed-off-by: Andrej Mak <andrej.mak@pantheon.tech>
Fix sonar warnings in config-util. Mostly renaming enum constants. Change-Id: I24a3afe1281a070550ef3c8424b35ed58d3691f6 Signed-off-by: Dana Kutenicsova <dana.kutenics@gmail.com>
Mechanical code cleanup (config) * Remove unnecessary type specifiers (use Java 7 <>) * Remove unnecessary "extends Object" declarations * Remove unnecessary semi-colons * Merge identical catch blocks * Remove redundant modifiers: - enum constructors are private by default - interface properties are public static final by default - interface methods are public abstract by default - interfaces are abstract by default - inner interfaces are static by default - inner classes in interfaces are public static by default Change-Id: Iefd8363a5eb120fdd43a4632b9e3db0e7e347dba Signed-off-by: Stephen Kitt <skitt@redhat.com>
Switch to StandardCharsets Guava's Charsets should not be used when StandardCharsets are available. Change-Id: I7c52bd3070bb48857cbba82e8d4bc5993d7aea9d Signed-off-by: Robert Varga <rovarga@cisco.com>
Add config system API to recreate a module instance For the blueprint work, I need to be able to restart/recreate a config module, ie close the previous instance and create a new instance, when the corresponding service instance is recreated/re-advertised via blueprint container restart. The ConfigSubsystemFacade has no API to restart a config module. One can push a new configuration but there has to be an actual change in order for a new instance to be created otherwise it reuses the prior instance. Therefore I added a new EditStrategyType enum, recreate, with a corresponding EditConfigStrategy class that forces re-creation of a config module instance. This strategy calls a new method, reCreateModule, on the ConfigTransactionController interface. The decision logic to reuse or create a new instance is in the AbstractModule class and generated derived classes. Therefore the reCreateModule method sets a canReuseInstance flag on the real AbstractModule instance. This is probably not the cleanest approach but I wanted to avoid changing the Module interface as that looked to be too invasive. The AbstractModule getInstance and canReuse methods check the canReuseInstance override flag to determine if the old module/instance can be reused. Change-Id: I8cfb8408bae0127331676dcf32519b176f0a8844 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>