The enum attribute and the deprecation can definitely go in EAP 6.3. All the deprecation does is add some read-resource-description metadata; it doesn't prevent people using it. It doesn't have to go in EAP 6.3 though.

But not 6.2.x -- we don't change management APIs in EAP micro releases without a dire need.

Doing that stuff is not a requirement of getting this PR in; I was just agreeing with your comment about a better long term fix and giving some more detail. I haven't merged this only because I haven't been merging for a couple days.