Created attachment 876759 [details] Jar for reproducing Steps to Reproduce: 1. Add the jar into internal m2 repo 2. Add the jar into project dependencies 3. Add org.test1.A and org.test2.B into import suggestions 4. Build & Deploy the project Actual results: Problems panel shows that imports A and B can not be resolved. Expected results: No items in Problems panel. Additional info: The build deploys ok. A and B can be used in editor. The problem is just that the message is misleading.
Update. Currently the A and B do not need to be added to import suggestions They are automatically picked up from the jar. In the future the goal should be to make import suggestions act as a mask for import options in the editors. Benefits: * If a jar with 1000 classes are added and only few of them are needed, the editor's import tab does not show 1000 items. * The project admin has the control to declare what facts can be used in the guided editors. An user that only has access to guided editor can not break the package by using the wrong Person fact if there are more than one available * This will unify the way imports are done. Currently imports from java.lang.* need to be added using import suggestions, in order for them to show up in guided editors. * In the future we might want to use aliases for the imports. org.test.Person could be masked as "User" or "Persona" if the users are spanish.
This is now done with white list. Import suggestions only works for JRE classes.
Verified with BRMS 6.3.0.ER1.