Community
Participate
Working Groups
We are using the following apis. org.eclipse.jem.internal.beaninfo.BeanDecorator; org.eclipse.jem.internal.beaninfo.MethodDecorator; org.eclipse.jem.internal.beaninfo.PropertyDecorator; org.eclipse.jem.internal.beaninfo.ParameterDecorator; org.eclipse.jem.internal.beaninfo.IndexedPropertyDecorator; org.eclipse.jem.internal.beaninfo.core.Utilities; org.eclipse.jem.internal.beaninfo.MethodProxy; org.eclipse.jem.internal.beaninfo.BeaninfoFactory; org.eclipse.jem.internal.beaninfo.BeaninfoPackage; org.eclipse.jem.internal.beaninfo.adapters.BeaninfoNature; We heard that their package names have 'internal', but they are the public apis. So we would like to refactor them not to have 'internal' to make it clear that they aren't internal apis. .
That will eventually be done. But it won't be for now. We will slowly be moving things to API when we are sure they won't be changing.
Most all of this is still "internal" in VE 1.2M2. Any update on when things will be moved to non-internal packages?
Fro now they will remain internal. We are not doing any enhancements at this time. However, they are stable and will be around for at least the next release, if not longer.
Please consider for Ganymede
As part of some general bugzilla cleanup, I am marking all old JEM bugs as "won't fix" simply because JEM is in maintenance mode, and there are no plans to fix these old bugs. If I have mistaken marked something that is still a current problem in the latests releases from WTP, please re-open.
Mving back to VE.