Community
Participate
Working Groups
Created attachment 278069 [details] Projects setup to reproduce Hello, Since Eclipse version 4.10, we encounter an issue when importing Maven projects. The issue manifests itself by exhibiting Java compilation errors, when it was working fine with Eclipse 4.9 and prior. The java errors are related to missing packages/classes from projects, although these project are actually present and open in workspace and properly added in MANIFEST.MF dependencies. This issue has been reproduced on Linux (Ubuntu 18.04, Java 8 and 11) and Windows 10 (Java 11), with Eclipse IDE for Eclipse Committers 2018-12 (4.10) and 2019-03 (4.11). I am not sure if it comes from M2E, but when importing the same projects with pre-generated .project files (import "Existing Project into Workspace" instead of "Existing Maven Projects"), there is no compilation errors. However, since we don't store the .project files and rely on M2E for generating them, it is an issue for us. The steps to reproduce the issue are: 1.1- Download, extract Eclipse IDE for Eclipse Committers 4.9 (https://www.eclipse.org/downloads/packages/release/2018-09/r/eclipse-ide-eclipse-committers) and attached demo project zip; 1.2- Launch Eclipse, Import ... / Maven / Existing Maven Projects, select root of extracted project zip. Make sure all nested projects are selected; 1.3- On popup, install M2E connectors (tycho, checkstyle), restart when done; 1.4- Observe build is OK, exit eclipse. 2.1- Download, extract Eclipse IDE for Eclipse Committers 4.11 (https://www.eclipse.org/downloads/packages/release/2019-03/r/eclipse-ide-eclipse-committers) and attached demo project zip (in another folder, to make sure .project files are not present); 2.2- Launch Eclipse, Import ... / Maven / Existing Maven Projects, select root of extracted project zip. Make sure all nested projects are selected 2.3- On popup, install M2E connectors (tycho, checkstyle), restart when done; 2.4- Observe build fails. Note that step 2.1 can be done with Eclipse 4.10. The demo project comes from https://github.com/preesm/preesm/tree/minimalExampleBugImport. We currently have a workaround to have the projects built properly (from https://github.com/preesm/preesm/issues/116): 1- Locate the project org.preesm.commons and Right click / Close project; 2- Wait for the build process to finish, then re-open the project. 3- The build will start again, but this time removing all errors. Best, Antoine.
Directly after importing, workspace resolution doesn't seem to work - None of the Plug-In Dependencies containers contains any other projects. After restarting Eclipse this is correct, and triggering a rebuild fixes the compilation problems. Moving to PDE.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
