Bug 1900374
| Summary: | M2E plugin stop works after upgrade | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel <danielsun3164> | ||||||||
| Component: | eclipse-m2e-core | Assignee: | Orphan Owner <extras-orphan> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 33 | CC: | eclipse-sig, esnel, fedora, mat.booth, mizdebsk | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | --- | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-11-30 19:04:48 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1732102 [details]
.metadata/.log in existing workspace
You might be able to resolve this issue using the following command, where "~/workspace" is the Eclipse workspace directory: rm -r ~/workspace/.metadata/.plugins/org.eclipse.m2e.* This worked on an fc33 installation that uses exactly the dependencies and versions described in this issue. Thank you very much for your contact.
Unfortunately, the
rm -r ~/workspace/.metadata/.plugins/org.eclipse.m2e.*
command didn't work for me.
There still an "An internal error occurred during: "Updating Maven Dependencies".
org/eclipse/m2e/core/internal/embedder/MavenExecutionContext" error after the eclipse starts.
Created attachment 1732488 [details]
difference of jar files from eclipse and fedora
I compared difference of jar files provided by eclipse 202009(left side) and fedora(right side). It seems that fedora is using different version of jar files.
Sorry, this seems to be my local environment problem. I deleted ~/.eclipse folder and start eclipse again, the error disappeared and everything works fine until now. Please close this bug, thank you very much. Thanks again for everything. This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 1732101 [details] .metadata/.log in new workspace Description of problem: I upgraded several eclipse packages today and M2E plugin stopped works. Version-Release number of selected component (if applicable): $ rpm -q eclipse-platform eclipse-m2e-core lucene eclipse-platform-4.17-3.fc33.x86_64 eclipse-m2e-core-1.16.2-1.fc33.noarch lucene-8.6.3-1.fc33.noarch How reproducible: Everytime Steps to Reproduce: 1. Open eclipse in a new workspace 2. Create a new Maven Project Actual results: A dialog as following was displayed: title: Multiple problems have occurred Message: The selected wizard could not be started. Problem Opening Wizard (Details: The selected wizard could not be started. Plug-in org.eclipse.m2e.core.ui was unable to load class org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard. An error occurred while automatically activating bundle org.eclipse.m2e.core.ui (5821).) Updaing Maven Dependencies (Details: An internal error occurred during: "Updating Maven Dependencies". org/eclipse/m2e/core/internal/embedder/MavenExecutionContext) Expected results: M2E plugin should works without errors. Additional info: Openning an existing workspace with maven project got the same "Updaing Maven Dependencies" error.