Hi all,
I would like to contribute the Java 9 support. Is there already an issue
for this?
Oliver
Am 29.04.18 um 23:22 schrieb Anatole Tresch:
Hi all
it is definitively time to focus on a next release. So I would ask the
following questions:
1. who will be helping us with the next release? Also new contributors
are very welcome?
2. What should be in the release?
3. until when should be published/ready for vote?
*To 1) *
I definitively can do some work, since the JSR branch is basically ready,
but should be reviewed also by someone else. But I would appreciate also
somebody else to do some coding stuff as well.
*To 2)*
- I would basically remove the configjsr module from the current
sandbox, since we have to JSR brunch fully supporting the JSR as a first
citizen.
- In the JSR branch I experimented with a* meta-attributes module,*
which defines a small SPI to define how meta-entries (entries that allow
adding attributes to entries) are managed. The default convention until now
was to use *_KEY.attr=xyz* for adding an attribute *attr *to the entry
*KEY.* I could move that into the main branch.
- There will be a couple of* features that the JSR will not support*.
Especially the *ConversionContext *for converters and the *FilterContext
*for filters (if filters are supported at all). We could *adapt the
Tamaya API *towards the new API design, deprecating the former
filter/converter methods and adding the new simpler ones. With Java 8
support the new methods can be default delegate to the old methods, e.g.
using a thread shared Conversion/Filter context. This is also the solution
that has been implemented in the JSR branch, which could be easily applied
to the current release as well.
- Finally we can *build *the modules as *multirelease jars*, also *adding
full Java9 module support.* By compiling them first with Java9 and in a
subsequent compiler run with Java8 target (excluded the descriptor file),
we get a Java 8 compatible code base with a full fledged Java 9 module
descriptor. This can be done by adding the descriptors and changing the
maven build configuration. This also requires retesting things especially
for OSGI, but this should be doable.
*To 3)*
*This depends on how much contributors with what skills can help, so lets
focus on 2 first.*
*Happy to hear your feedback!*
*J Anatole*
