internal: use scala 2.12 (but cross compile to 2.11 too) and upgrade some dependencies

v0.8.4

0.8.4: internal: use scala 2.12 (but cross compile to 2.11 too) and u…

generate configuration template

https://github.com/carueda/tscfg/wiki/template-generation

replace deprecated class in Scala generated code

v0.8.1

0.8.1 - use JavaConverters (instead of deprecated JavaConversions) in…

size-in-bytes now supported

resolve #23 "support size-in-bytes type"

fix and code cleanup

• fix issue #22 "literal duration captured as string"
• code cleanup: generate code as part of test phase

some more adjustments

Some minor bug fixes; simplified generated code and additional tests

implementation rewrite and simplification

Code simplified, more consistent and better organized. All tests reviewed and coverage further increased (to 95%).

Some minor adjustments post 0.5.0 ; )

including some internal code cleanup

Now with support for lists, optional objects, lists; improved implementation

This is almost a complete rewrite of the tool! Thanks to that, now supporting lists, optional objects (sections), and hopeful making easier to further extend the tool later on.

• resolve #16 "rewrite code"
• resolve #15 "support list"
• resolve #10 "annotations" -- basically only the #@optional one
• NOTE: toString not generated anymore

some fixes and additions

• fix #13 "scala: double definition"
  add build auxiliary method to avoid type erasure issue in case of optional member
• --noToString now processed for scala
• add options --toPropString and --noToString (only processed for java):
  • --toPropString to generate toPropString method (not generated by default)
  • --noToString to not generate toString method (generated by default)
• fix #12 "incorrect reference with standard types in path fragments"
• java: factor out access to Config parameter for sub-section in static method __$config at the root class
• in java's toString, no need for conditional for string field if required or with default (non-null) value
• allow missing sections in given input configuration.
  This helps with sections whose all members are optional.
  Still to be done is proper handling of optional sections in general. Besides an explicit annotation
  to indicate that a section is optional, note that a section can also be implicitly optional
  if all its members are optional.
• fix #11 "name collision with no-arg methods in scope"