Use of Archaius2 in Spring applications is hampered by the clash between their @Configuration annotation, which marks classes that contain bean definitions, and ours, which marks interfaces that can be instantiated as configuration proxies.
Since Spring has a larger use base, we should adapt and provide a new annotation for this purpose that avoids the name clash. An option would be to adopt the name they use for a similar purpose, @ConfigurationSource. If we choose that path, we should support classes that carry their annotation, in addition to ours.
We must also remain backward compatible with our existing name for at least one more major-version release (ie, we would not retire support for our @Configuration annotation before a hypothetical Archaius 4 release).
Use of Archaius2 in Spring applications is hampered by the clash between their
@Configurationannotation, which marks classes that contain bean definitions, and ours, which marks interfaces that can be instantiated as configuration proxies.Since Spring has a larger use base, we should adapt and provide a new annotation for this purpose that avoids the name clash. An option would be to adopt the name they use for a similar purpose,
@ConfigurationSource. If we choose that path, we should support classes that carry their annotation, in addition to ours.We must also remain backward compatible with our existing name for at least one more major-version release (ie, we would not retire support for our
@Configurationannotation before a hypothetical Archaius 4 release).