Bug 1488224 - After latest updates, jgit and maven no longer work properly in eclipse bundled with Fedora
Summary: After latest updates, jgit and maven no longer work properly in eclipse bundl...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Mat Booth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-04 18:05 UTC by Marc Boorshtein
Modified: 2026-03-05 00:04 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:24:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marc Boorshtein 2017-09-04 18:05:15 UTC
Description of problem:


After updating the OS I get the following error when Eclipse starts:

Errors occurred during the build.
Error instantiating builder 'org.eclipse.m2e.core.maven2Builder'.
Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder.
An error occurred while automatically activating bundle org.eclipse.m2e.core (387).
Plug-in org.eclipse.m2e.core was unable to load class org.eclipse.m2e.core.internal.builder.MavenBuilder.
An error occurred while automatically activating bundle org.eclipse.m2e.core (387).


Version-Release number of selected component (if applicable):

Fedora 26
Eclipse Oxygen
Latest builds from Fedora repos

How reproducible:

Open existing workspace with maven projects

Steps to Reproduce:
1.
2.
3.

Actual results:

above error

Expected results:

Eclipse should build the project

Additional info:

Comment 1 Mat Booth 2017-09-05 08:57:56 UTC
Hi,

Can you attach your workspace log to this bug please? There may be more information in there.

By default you can find it in: ~/workspace/.metadata/.log

Also, can you try running Eclipse like this?

$ eclipse -clean

This forces Eclipse to clear its OSGi bundle cache. Your workspace will not be affected.

Comment 2 Fedora End Of Life 2018-05-03 07:59:59 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Comment 3 Fedora End Of Life 2018-05-29 11:24:48 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


Note You need to log in before you can comment on or make changes to this bug.