Community
Participate
Working Groups
Following Discovery framework rewriting, thsi bugs summarizes some implementation problems on 14 "oem.java.*" components. - Some oem.java.* components should not have any dependency to ui component. e.g. oem.java.discoverer should not have reference to org.eclipse.ui neither to org.eclipse.gmt.modisco.infra.common.ui. Using "Find unused dependencies" should help to clean. - Some Java classes still have a lot of "Discouraged access" warnings. e.g. oem.java.composition should be x-friends for kdm.source.extension.
I removed UI dependencies from these plug-ins: org.eclipse.modisco.java.discoverer org.eclipse.modisco.java.discoverer.cdo But UI dependencies cannot be removed from these plug-ins: org.eclipse.modisco.java.composition.discoverer org.eclipse.modisco.java.composition.discoverer.benchmark org.eclipse.modisco.jee.ejbjar.discoverer org.eclipse.modisco.jee.jsp.discoverer org.eclipse.modisco.jee.webapp.discoverer because they still contain compatibility versions of discoverers, which depend on org.eclipse.gmt.modisco.infra.discoverymanager, which has UI dependencies (org.eclipse.ui, org.eclipse.debug.ui, org.eclipse.ui.ide).
I fixed the warnings in the discovery projects.
You are right about ui dependencies. There are still jdt undocumented warnings (some coming from old code). I will work on it now.
Fix on warnings have been commited (serveral revisions up to 4344) No one of the 15 oem.java.* project contains jdt or checkstyle warning anymore.
Refactoring done.