As there was no reply I treat this as lazy consensus and will move
forward to remove the old blueprint annotations from trunk. We can still
produce fixes if there is need
by branching from a release tag.
Please speak up if you want the annotations modules to remain.
Christian
On 03.01.2017 12:26, Christian Schneider wrote:
In Aries blueprint we have some custom annotations that can be used
instead of the xml configs.
As far as I know these annotations are rarely used. In fact I do not
know anyone using them in production. I also have not seen any
questions about them recently.
As a replacement there is the blueprint-maven-plugin. It support
standard JEE annotations as well as spring annotations and creates
blueprint xml from annotations at build time.
Dominik has put quite some effort into this annotations support
recently and I know they are used by quite a few people in production.
Since the newest release there is even support for extensions. So
users can now define their own custom annotations and map them to xml.
So I think we could safely deprecate the old annotations and remove
them from the current trunk.
What do you think?
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
