basically codi configuration is based on cdi mechanisms.
however, there are artifacts which have to be configured before cdi is up and running.
instead of hardcoding config names,... it should be handled via implementations of ConfiguredValueResolver.
that also allows to introduce custom config approaches e.g. for the project stage.
via the existing @InvocationOrder annotation it should be possible to specify the order and via the ClassDeactivator approach it should be possible to deactivate existing implementations of ConfiguredValueResolver.
optionally it should be possible to aggregate implementations (if it makes sense for the specific artifact)
without custom implementations it should be possible to configure artifacts via:
- system property
- service loader