Community
Participate
Working Groups
During the import of a new maven project, with a lot of new decenpendies, you have to wait the complete download of all dependencies, before doing everything, also creating a Folder. The download of dependencies should work in background without blocking the UI action. If, like in my case, you are using a mobile internet key, and you have an entire project to download from scratch it, you take a long time before starting to work, and it is very stressful.
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.
I don't get the UI blocked at import. Can you please provide detailed minimal steps to reproduce this issue?
I download the project. Then i start the build. After that i had another project in same workspace, and for example i want to start to edit the pom of the other project and i receive the blocking message, that i have to wait for completion of activities. I cannot edit another pom while i am editing a project. If the build take a while, 5-10 minutes, the ui is blocked for the whole workspace.
(In reply to Luca Preziati from comment #3) > I download the project. Then i start the build. After that i had another > project in same workspace, and for example i want to start to edit the pom > of the other project and i receive the blocking message, that i have to wait > for completion of activities. > I cannot edit another pom while i am editing a project. If the build take a > while, 5-10 minutes, the ui is blocked for the whole workspace. Which project? How do you start the build? How is the UI blocked (a pop-up or a full freeze)?... Please try to be more precise and ideall share some minimal projects and so on to easily reproduce it.
Created attachment 285431 [details] Screenshot This is a new case where the import action of the dependency in maven is blocking action in UI. I imported a new project as maven project, and eclipse start to download the dependency. After that I see a submodule of the project do not have the Java Project Facet. So I try to apply and the ok is blocked by the download of the java dependency.
(In reply to Mickael Istria from comment #4) > (In reply to Luca Preziati from comment #3) > > I download the project. Then i start the build. After that i had another > > project in same workspace, and for example i want to start to edit the pom > > of the other project and i receive the blocking message, that i have to wait > > for completion of activities. > > I cannot edit another pom while i am editing a project. If the build take a > > while, 5-10 minutes, the ui is blocked for the whole workspace. > > Which project? How do you start the build? How is the UI blocked (a pop-up > or a full freeze)?... Please try to be more precise and ideall share some > minimal projects and so on to easily reproduce it. Generally is the pop up, that ask to user to wait the full download of dependency. If you have a lot of dependency to be downloaded by zero it take 3-5 minutes and you cannot also open a file to see the code.
(In reply to Luca Preziati from comment #6) > > Which project? How do you start the build? How is the UI blocked (a pop-up > > or a full freeze)?... Please try to be more precise and ideall share some > > minimal projects and so on to easily reproduce it. > > Generally is the pop up, that ask to user to wait the full download of > dependency. If you have a lot of dependency to be downloaded by zero it take > 3-5 minutes and you cannot also open a file to see the code. This is still not precise enough to be fully helpful. Please provide a small project code to reproduce the issue and detailed step about how to make the issue happen (which pom file is open, which menu entries you're using and so on).
Eclipse m2e is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse-m2e/m2e-core/issues/ instead. If this issue is relevant to you, your action is required. 0. Verify this issue is still happening with latest Eclipse Platform and m2e release if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done if issue is still present when latest release: * Create a new issue at https://github.com/eclipse-m2e/m2e-core/issues/ ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience) ** In the GitHub description, start with a link to this bugzilla ticket ** Optionally add new content to the description if it can helps towards resolution ** Submit GitHub issue * Update bugzilla ticket ** Add to "See also" property (up right column) the link to the newly created GitHub issue ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>" ** Set status as CLOSED MOVED ** Submit All issues that remain open will be automatically closed next week or so. Then the m2e component for m2e will be made read-only.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
