You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the only supported format for configuration files handled by owner api is java Properties. It would be nice to have a plugin based architecture that adds support for different file formats.
While Java properties can be provided out of the box, without dependencies, it would be good to implements "plugins" depending on commons configuration to add the supported file formats transparently, keeping all other features unvaried.
In my opinion it is important to not add transitive dependencies in the current apache module; so I would implement the additional file formats inside different maven module(s).
The text was updated successfully, but these errors were encountered:
YAML as it is a complex file format and also not fully mappable to a Java Properties Object, and for the moment this is kept out from the next releases scope, as full YAML support will need internal data structure redesign.
This is not actually a file format, but it is more a matter to support those objects (and j2ee objects) to allow and ease support for those kind of configuration parameters. The parser can be inspired on Apache commons configuration. This may require a new maven module, that depends on J2EE libs.
At the moment, the only supported format for configuration files handled by owner api is java Properties. It would be nice to have a plugin based architecture that adds support for different file formats.
Apache commons configuration provides support for several file formats.
While Java properties can be provided out of the box, without dependencies, it would be good to implements "plugins" depending on commons configuration to add the supported file formats transparently, keeping all other features unvaried.
In my opinion it is important to not add transitive dependencies in the current apache module; so I would implement the additional file formats inside different maven module(s).
The text was updated successfully, but these errors were encountered: