Hi, on the recent deprecation vote I saw this vote (from Ralph):
> * JNDI-related features: -1 Unfortunately, JEE users require this. I am surprised we still have JNDI in the code at all, but this made me curious: why do JEE users need JNDI features for logging? Why can't they just use the normal log mechanism? To me, JNDI is a burned word in Logging. No matter what we say about it, nobody will ever believe we will have this under control. I am a strong +1 on removing this, even for 2.x. Users can have a separate module they can add to their pom, if they really need it. I am aware of versioning and this could be considered a breaking change, but after all, the APIs are intact, and only the pom changes. That being said, I would like to understand better what "jndi related" features in our code base are actually solving, because from marketing perspective, they are super GAU. Kind regards, Christian
