aeonbits-owner 1.0.12+ds-3 source package in Ubuntu

Changelog

aeonbits-owner (1.0.12+ds-3) unstable; urgency=medium

  * Skipping mockito checks on Properties in PropertiesInvocationHandlerTest
    (Closes: #1026659)
  * Adding a Lintian override for the bad-jar-name tag

  [ Andreas Tille ]
  * d/watch: Sensible filename for upstream download
  * Standards-Version: 4.6.2 (routine-update)
  * Apply multi-arch hints. + libaeonbits-owner-java: Add Multi-Arch: foreign.

 -- Pierre Gruet <email address hidden>  Fri, 23 Dec 2022 23:03:38 +0100

Upload details

Uploaded by:
Debian Med
Uploaded to:
Sid
Original maintainer:
Debian Med
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc
Noble release universe misc
Mantic release universe misc
Lunar release universe misc

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
aeonbits-owner_1.0.12+ds-3.dsc 2.2 KiB 9b0faafda1fdc95cc4d95d4760415cd9e3c6c2f65c041df09c6da6e2e5e0482e
aeonbits-owner_1.0.12+ds.orig.tar.xz 225.8 KiB 71326527ba9ee2b6a897833d0ffecc7d58743c07c703cee4fb3940a42718ddf6
aeonbits-owner_1.0.12+ds-3.debian.tar.xz 5.2 KiB dde8655b36b0339661b823bfa7e5f15f7f6c10ec08abb3695654ed8cece6404f

Available diffs

No changes file available.

Binary packages built by this source

libaeonbits-owner-java: API to handle application configuration through Java properties file

 OWNER was written because the code dealing with the configuration is
 frequently repetitive, redundant, it’s made of static classes, singletons,
 long list of methods just doing conversion from a string property to a named
 method returning a Java primitive or a basic Java object.
 .
 OWNER solves the problem providing an interface object that
  - is easy to mock, easy to pass to other objects (via dependency injection);
  - declaratively maps the configuration without any redundancy;
  - can easily expand the loading logic in order to have multiple configuration
  files, multiple level of overriding (global configuration, user-level,
  defaults, etc);
  - doesn’t need to have an actual properties file backing the configuration,
  if one uses @DefaultValue.
  - provides a lot of features, like hot reloading, variables expansion, etc;
  - leaves one free to do everything one is already doing with
  java.util.Properties;
  - does support a super powerful type conversion, which includes arrays,
  collections, many standard Java objects, and even the possibility to plug
  one's own conversion logic.