@@ -23,12 +23,12 @@ Maven:
23
23
<dependency >
24
24
<groupId >com.oracle.labs.olcut</groupId >
25
25
<artifactId >olcut-core</artifactId >
26
- <version >5.1.6 </version >
26
+ <version >5.2.0 </version >
27
27
</dependency >
28
28
```
29
29
or from Gradle:
30
30
``` groovy
31
- implementation 'com.oracle.labs.olcut:olcut-core:5.1.6 '
31
+ implementation 'com.oracle.labs.olcut:olcut-core:5.2.0 '
32
32
```
33
33
34
34
The ` olcut-extras ` artifact is designed as a small tool for developers, as such you should compile the appropriate
@@ -37,12 +37,13 @@ version based on your needs.
37
37
## Configuration System
38
38
39
39
The OLCUT [ Configuration System] ( README-Configuration.md ) uses runtime
40
- dependency-injection to instantiate configurable components on the fly based on
41
- the contents of your configuration file. It allows you to both specify the parameters
42
- ("properties") that should be given to the components at initialization time as well
43
- as which types of objects should actually be instantiated for each component. It
44
- uses an XML file to describe the configuration. OLCUT uses Java Annotations extensively
45
- to facilitate code integration.
40
+ dependency-injection to instantiate configurable components on the fly based on
41
+ the contents of your configuration file. It allows you to both specify the
42
+ parameters ("properties") that should be given to the components at
43
+ initialization time as well as which types of objects should actually be
44
+ instantiated for each component. By default it uses an XML file to describe the
45
+ configuration, though edn, json and protobuf formats are available. OLCUT uses
46
+ Java Annotations extensively to facilitate code integration.
46
47
47
48
``` xml
48
49
<config >
@@ -90,7 +91,7 @@ the appropriate fields.
90
91
91
92
This is just a small sample of what the Configuration system can do. It
92
93
supports ** inheritance** , many configurable types, ** command line overrides** , self-description,
93
- and multiple file formats including ** JSON** .
94
+ and multiple file formats including ** JSON** , ** edn ** , and ** protobuf ** .
94
95
95
96
Read all about the [ Configuration System] ( README-Configuration.md ) .
96
97
@@ -196,12 +197,12 @@ Read more about the [Command Interpreter](README-Commands.md).
196
197
197
198
## Provenance
198
199
199
- OLCUT provides a system for extracting the state of configurable objects into
200
- immutable Provenance objects used to record the state of a computation. It's heavily
201
- used in [ Tribuo] ( https://tribuo.org ) to record a trainer and dataset configuration.
202
- It can optionally include
203
- non-configurable state. It supports conversion to a marshalled format which can be
204
- easily serialised and deserialised from JSON or protobuf.
200
+ OLCUT provides a system for extracting the state of configurable objects into
201
+ immutable Provenance objects used to record the state of a computation. It's
202
+ heavily used in [ Tribuo] ( https://tribuo.org ) to record a trainer and dataset
203
+ configuration. It can optionally include non-configurable state. It supports
204
+ conversion to a marshalled format which can be easily serialised and
205
+ deserialised from JSON, xml or protobuf.
205
206
206
207
Provenance objects can be converted back into a list of configurations, which can be
207
208
used to recreate the config file that generated that provenance. This can be used
0 commit comments