| [riena-dev] Removing @Deprecated Extension points and code |
Hi Rienars,
Now after 3.0 we plan to remove deprecated “code” from Riena.
In the beginning we had introduced a couple of extension points which were badly named. After we realized this we duplicated those extension points and gave them better names. And so it was possible to use both – the bad and the good – because their structure was identical. But now we will dispose the old extension points:
org.eclipse.riena.communication.core.proxyselector
org.eclipse.riena.communication.core.factory
org.eclipse.riena.communication.hessian.AbstractSerializerFactory
org.eclipse.riena.core.exception.handlers
org.eclipse.riena.core.logging.catchers
org.eclipse.riena.core.logging.listeners
org.eclipse.riena.monitor.clientinfoprovider
org.eclipse.riena.monitor
org.eclipse.riena.monitor.sender
org.eclipse.riena.monitor.store
org.eclipse.riena.ui.swt.statusline
org.riena.ui.core.uiprocess
org.eclipse.riena.filter.ruleMapper
org.eclipse.riena.filter.uiFilter
org.eclipse.riena.ui.ridgets.correspondinglabel.config
org.eclipse.riena.ui.ridgets.labelfinderstrategy
org.eclipse.riena.ui.ridgets.swt.processdetail
org.eclipse.riena.ui.swt.imagepath
org.eclipse.riena.ui.swt.lnfrenderer
If you are using one of these you should already see that they are deprecated and which one is the replacement. This should be very easy and trouble-free.
We also try to get rid of @deprecated Java code. Yes, this also means get rid of code which is API!
This is so much that it does not make sense to list it here.
So, we are asking you to watch out for uses of deprecated “code” in your Riena applications and use the recommended replacement.
If you are experiencing problems with that drop us a line and let us know what your problem is!
Tschüß,
Stefan