Those APIs that are going to be needed by other
products need to increase their stability in
future release at least to "under development".
This is a future TCR.
No time for this in 4.1.
In 4.1 it was not a goal to make the APIs work for other products,
they were only for use within enterprise1 cluster so I do not consider
this to be a defect. In promo F it will probably be needed.
TM 5.0 -> TBD
Nowadays j2ee apis are used *not only* within enterprise cluster (see the thread
on nbdev), so this should be a defect now. (I'm not sure about a priority, so
feel free to change it)
Will try to stabilize at least some of the APIs for 6.0.
Setting target milestone to future.
Not planned for 7.0
Changing to TASK.