Removing olcut-config-jini.

Author: Craigacp

.gitignore

@@ -20,7 +20,6 @@ manifest.mf
 
 # Subproject files
 olcut-core/target
-olcut-config-jini/target
 olcut-config-json/target
 olcut-config-edn/target
 olcut-extras/target

CONTRIBUTING.md

@@ -3,8 +3,7 @@
 We welcome your contributions! There are several directions that OLCUT could
 be extended in. New config file formats could be added, more classes can be
 added for the `@Config` annotation,  more classes can be supported by the
-`CommandInterpreter`'s `@Command` methods. The remote component discovery based on
-Jini / Apache River could stand to be modernized. Have an idea? Talk to us and
+`CommandInterpreter`'s `@Command` methods.  Have an idea? Talk to us and
 let's make it happen. Just file an Issue to get in touch.
 
 ## Questions, Bugs, and Features

README-Configuration.md

@@ -66,7 +66,7 @@ they are not the right type.  It also checks that only parameters defined in
 the object are included in the configuration file.  Properties may be tagged
 as mandatory or not and may have default values (here, numThreads is given a 
 default value of 1 if it is not included in the configuration file). Properties
-may also be tagged "redact" which will cause their values not to appear in 
+may also be tagged `redact` which will cause their values not to appear in 
 saved configuration files, or provenance objects.
 
 To instantiate the pipeline in your code, you'd put something like the following
@@ -312,33 +312,6 @@ the necessary read locations are program specific. If you need to save an OLCUT
 configuration out then you will also need to add write permissions for the save
 location. 
 
-The remote component loading system requires a further set of permissions which
-we haven't completely captured.
-
-## Remote Components
-
-The configuration system can make use of Jini (a.k.a. Apache River) and RMI to help instantiate a
-distributed system.  Through extensions to the component definition in the
-configuration file, components can be registered as services in Jini.  When
-a component lists another component as a property, that component need not
-be on the same machine.  If it is remote, the configuration system will
-automatically query Jini to find the service and it will return an RMI proxy
-for the object.
-
-Documentation about how to start a class server, run a registry, specify an
-object as remote, provide `ConfigurationEntries`, deal with `RemoteComponentManager`
-and `RemoteMultiComponentManager`, etc will eventually be added here.
-
-Remote loading in general works fine with Java 9+, but we have experienced some weird class 
-loader issues when using serialization in RMI calls with Jini in another project. 
-It's TBD on what the root cause is or how to fix it.
-
-Note: remote components are currently deprecated as they depend on features
-deprecated by the integration of [JEP 385](https://openjdk.java.net/jeps/385)
-in Java 15. We are considering alternative approaches which will keep this 
-functionality, though it will likely be structured differently to the current
-implementation.
-
 ## Other config formats
 
 OLCUT 4.1 and above support json and edn (a Clojure based format) configuration files

README.md

@@ -5,7 +5,7 @@ components with standard and interoperable command line interfaces. It has its r
 the Sphinx 4 speech recognizer but has been significantly extended. These pieces can
 be used in concert or independently:
 
-* The Configuration System provides runtime configuration management (even over RMI) without recompiles
+* The Configuration System provides runtime configuration management without recompiles
 * The Options Processor cleanly processes command-line arguments, including configuration changes
 * The Command Interpreter provides an Annotation-based interactive shell with tab completion
 * Additional Odds & Ends provide helpful utility classes
@@ -31,10 +31,6 @@ or from Gradle:
 implementation 'com.oracle.labs.olcut:olcut-core:5.1.4'
 ```
 
-The Jini-based remote configuration system in `olcut-config-jini` is deprecated as aspects of Jini are deprecated by 
-[JEP 385](https://openjdk.java.net/jeps/385). At the moment we don't have
-a replacement approach which will function after the rmid tool is removed.
-
 The `olcut-extras` artifact is designed as a small tool for developers, as such you should compile the appropriate 
 version based on your needs.
 
@@ -94,8 +90,7 @@ the appropriate fields.
 
 This is just a small sample of what the Configuration system can do. It
 supports **inheritance**, many configurable types, **command line overrides**, self-description,
-a multiple file formats including **JSON**, and even remote implementation of
-components over RMI via Apache River (formerly Jini).
+and multiple file formats including **JSON**.
 
 Read all about the [Configuration System](README-Configuration.md).
 

THIRD_PARTY_LICENSES.txt

@@ -35,262 +35,6 @@ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 OF THE POSSIBILITY OF SUCH DAMAGE.
 
-Apache River 2.2.3
-
-Apache River
-Copyright 2009 The Apache Software Foundation
-
-This product includes software developed at
-The Apache Software Foundation (http://www.apache.org/).
-
-Copyright 2005 Sun Microsystems, Inc.
-This product includes material developed by Sun Microsystems, Inc.
-(http://www.sun.com).
-
-Copyright 2002-2005 Geoffrey Arnold (http://www.geoffreyarnold.com)
-This product contains code derived from the Ant build script contributed 
-to the Jini Community by Geoffrey Arnold (http://www.geoffreyarnold.com).
-
-Copyright 2000-2005 Artima Software, Inc.
-Portions of this software were developed by Bill Venners of Artima, Inc., who
-led the ServiceUI project. The ServiceUI project, which was hosted at jini.org,
-was tasked with defining a "standard" approach to attaching UIs to Jini services.
-The ServiceUI specification and API represent the best amalgamation of the ideas
-contributed by all the people who participated in the serviceui project. 
-
-The original two releases of the ServiceUI API, including specifications
-and code, are available from:
-
-    http://www.artima.com/jini/serviceui/index.html
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed 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.
-
- ASM examples: examples showing how ASM can be used
- Copyright (c) 2000-2005 INRIA, France Telecom
- All rights reserved.
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the above copyright
-    notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
-    notice, this list of conditions and the following disclaimer in the
-    documentation and/or other materials provided with the distribution.
- 3. Neither the name of the copyright holders nor the names of its
-    contributors may be used to endorse or promote products derived from
-    this software without specific prior written permission.
-  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-  AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-  ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
-  LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-  CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
-  SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-  INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
-  CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
-  ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
-  THE POSSIBILITY OF SUCH DAMAGE.
-
 jackson-core, jackson-databind 2.11.2
 
 

docs/Internals.md

@@ -58,7 +58,7 @@ it goes out of scope.
 
 ## Lifetime of a ConfigurationManager processing Options
 
-This summerises the steps executed by a `ConfigurationManager` on construction
+This summarises the steps executed by a `ConfigurationManager` on construction
 when parsing options.
 
 1. A class implementing Options, with fields marked @Option for values that can be read in from the command line is constructed.