-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use SmartImport API #47
Comments
Sounds good, but for that, SmartImport first needs to move the Core part to a headless bundle. |
Do we need to know where the project directory is for the smart import to work? People might not open the appropriate folder in VSCode |
yes, you usually need the root directory. AFAIK, there is no mechanism for that in Eclipse Platform at the moment, however, it was considered with very similar goals: https://bugs.eclipse.org/bugs/show_bug.cgi?id=489799 |
@mickaelistria Is there an issue for moving the core SmartImport to a headless bundle? |
@gorkem Yes, SmartImport is API, so we cannot move it anymore at the moment. However, we can "copy" it someplace else and make the current API extend or delegate to the one in a non-UI bundle. |
Signed-off-by: Fred Bricon <fbricon@gmail.com>
Implemented as the new importers. |
Eclipse Platform has a generic way to get started with a project, able to consume existing metadata to generate Eclipse ones, and to whom m2e, builship, jdt can contribute via extensions to detect and configure different kinds of projects.
This could be used instead of Maven-specifi importer.
The text was updated successfully, but these errors were encountered: