Bug 1130456
| Summary: | eclipse-m2e; unable to run compile target | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dirk Schnelle-Walka <dirk.schnelle> |
| Component: | eclipse-m2e-core | Assignee: | Gerard Ryan <fedora> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | fedora, mizdebsk |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-30 01:07:27 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: | |||
|
Description
Dirk Schnelle-Walka
2014-08-15 09:39:56 UTC
Hi Dirk, Thanks for the bug report. Sorry about the delayed response, I've been away for a couple of weeks. I'm able to reproduce this, so I'll hopefully be able to get a fix for it soon. Anything new? (In reply to Dirk Schnelle-Walka from comment #2) > Anything new? Hi Dirk, I haven't been able to figure out what's causing it yet unfortunately. It appears to be just missing the logging though -- the build still gets run...we just don't get all the output in Eclipse. In F21, m2e is version 1.5.x where some things have changed and this issue doesn't seem to be present. I'll hopefully be able to find some time soon to look into it in more depth on F20. One of the hard parts is that m2e expects certain versions of its dependencies, and we don't always have the same versions, and in some cases, we have incompatible versions which mean we have to patch m2e to get it to build/work at all. Thanks for your patience! Gerard. Gerard, Maybe, these two links are helpful: http://stackoverflow.com/questions/11916706/slf4j-failed-to-load-class-org-slf4j-impl-staticloggerbinder-error https://bugs.eclipse.org/bugs/show_bug.cgi?id=387064 Just in case that you did not find them yourself and to link the error descriptions. Since maven is pretty common it would be really great to have it fixed. I can understand that this is trickier than initially expected. In the meantime, I will try to try the workaround that is provided in one of the threads. Dirk Unfortunately, none of the provided workarounds worked for me. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |