Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.9.0.14) Gecko/2009082707 Firefox/3.0.14 GTB5 (.NET CLR 3.5.30729) Build Identifier: MTJ 1.0.1 there are two small issues that were introduced on MTJ 1.0.1 API. Both issues are that there are new methods on the API that return non-API interfaces. Those methods are: /org.eclipse.mtj.core/src/org/eclipse/mtj/core/MTJCore:getDeviceMatchCache /org.eclipse.mtj.ui/src/org/eclipse/mtj/ui/editors/jad/JADPropertiesEditorPage:createStringFieldEditor the interfaces org.eclipse.mtj.internal.core.sdk.device.IDeviceMatchCache org.eclipse.mtj.internal.ui.preferencesExtendedStringFieldEditor are currently internal should be public. if we want to fix those issues we will need to move MTJ to a 2.0 release. Reproducible: Always
The problem with the JADPropertiesEditorPage#createStringFieldEditor is fixed as part of the bug 287959. The only remaining issue is with the deprecated MTJCore.getDeviceMatchCache API.