[Bug 1488224] New: After latest updates, jgit and maven no longer work properly in eclipse bundled with Fedora
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1488224
Bug ID: 1488224
Summary: After latest updates, jgit and maven no longer work
properly in eclipse bundled with Fedora
Product: Fedora
Version: 26
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: marc.boorshtein(a)tremolosecurity.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
dbhole(a)redhat.com, ebaron(a)fedoraproject.org,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jjohnstn(a)redhat.com,
krzysztof.daniel(a)gmail.com, lef(a)fedoraproject.org,
oliver(a)linux-kernel.at, rgrunber(a)redhat.com
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:
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 11 months
[Bug 1500802] New: eclipse fails to start after update
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1500802
Bug ID: 1500802
Summary: eclipse fails to start after update
Product: Fedora
Version: 26
Component: eclipse-cdt
Assignee: jjohnstn(a)redhat.com
Reporter: rclark(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
jjohnstn(a)redhat.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com,
TicoTimo(a)gmail.com
Created attachment 1337260
--> https://bugzilla.redhat.com/attachment.cgi?id=1337260&action=edit
eclipse .log file
Description of problem:
After 'dnf update', eclipse fails to start. See attached .log.
(Note sure if this should be assigned to 'eclipse' or 'eclipse-cdt'..)
Version-Release number of selected component (if applicable):
Installed Packages
eclipse-abrt.noarch 0.0.3-2.fc26
@@commandline
eclipse-cdt.x86_64 1:9.3.2-2.fc26
@updates
eclipse-cdt-native.x86_64 1:9.3.2-2.fc26
@updates
eclipse-cdt-parsers.x86_64 1:9.3.2-2.fc26
@updates
eclipse-color-theme.noarch 1.0.0-6.fc26
@@commandline
eclipse-dltk.noarch 5.8.1-1.fc26
@updates
eclipse-dltk-sh.noarch 5.8.1-1.fc26
@updates
eclipse-dtp.noarch 1.14.0-1.fc26
@updates
eclipse-ecf-core.noarch 3.13.8-1.fc26
@updates
eclipse-egit.noarch 4.8.0-2.fc26
@updates
eclipse-emf-core.noarch 1:2.13.0-2.fc26
@updates
eclipse-emf-runtime.noarch 2.13.0-2.fc26
@updates
eclipse-epp-logging.noarch 2.0.6-1.fc26
@updates
eclipse-equinox-osgi.x86_64 1:4.7.1-4.fc26
@updates
eclipse-filesystem.noarch 1.0-9.fc26
@updates
eclipse-gef.noarch 3.11.0-3.fc26
@updates
eclipse-jdt.noarch 1:4.7.1-4.fc26
@updates
eclipse-jgit.noarch 4.8.0-2.fc26
@updates
eclipse-launchbar.noarch 1:2.1.2-2.fc26
@updates
eclipse-linuxtools.noarch 6.1.1-2.fc26
@updates
eclipse-linuxtools-changelog.noarch 2:6.1.1-2.fc26
@updates
eclipse-linuxtools-libhover.noarch 6.1.1-2.fc26
@updates
eclipse-linuxtools-manpage.noarch 6.1.1-2.fc26
@updates
eclipse-linuxtools-rpm-editor.noarch 6.1.1-2.fc26
@updates
eclipse-m2e-core.noarch 1.8.1-1.fc26
@updates
eclipse-m2e-workspace.noarch 0.4.0-5.fc26
@fedora
eclipse-mylyn.noarch 3.23.1-6.fc26
@updates
eclipse-mylyn-context-cdt.noarch 3.23.1-6.fc26
@updates
eclipse-mylyn-docs-wikitext.noarch 3.23.1-6.fc26
@updates
eclipse-mylyn-tasks-bugzilla.noarch 3.23.1-6.fc26
@updates
eclipse-mylyn-versions.noarch 3.23.1-6.fc26
@updates
eclipse-p2-discovery.noarch 1:4.7.1-4.fc26
@updates
eclipse-pde.x86_64 1:4.7.1-4.fc26
@updates
eclipse-platform.x86_64 1:4.7.1-4.fc26
@updates
eclipse-ptp.x86_64 9.1.3-1.fc26
@updates
eclipse-recommenders.noarch 2.4.9-2.fc26
@updates
eclipse-remote.noarch 3.0.0-0.1.git96f33c6.fc26
@updates
eclipse-rse.noarch 3.7.3-1.fc26
@updates
eclipse-swt.x86_64 1:4.7.1-4.fc26
@updates
eclipse-tm-terminal.noarch 4.3.0-0.2.gitfa298da.fc26
@updates
eclipse-tm-terminal-connectors.noarch 4.3.0-0.2.gitfa298da.fc26
@updates
eclipse-usage.noarch 4.5.0-1.fc26
@updates
eclipse-webtools-common.noarch 3.9.0-1.fc26
@updates
eclipse-webtools-javaee.noarch 3.9.0-1.fc26
@updates
eclipse-webtools-servertools.noarch 3.9.0-1.fc26
@updates
eclipse-webtools-sourceediting.noarch 3.9.0-1.fc26
@updates
eclipse-xsd.noarch 2.12.0-2.fc26
@@commandline
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 12 months
[Bug 1331470] New: swt hello world tutorial does not work
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1331470
Bug ID: 1331470
Summary: swt hello world tutorial does not work
Product: Fedora
Version: 23
Component: eclipse
Severity: medium
Assignee: akurtako(a)redhat.com
Reporter: rtc(a)helen.plasma.xg8.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Description of problem:
The "Create a Hello World SWT application" fails to work as described; widget
classes are inaccessible.
Version-Release number of selected component (if applicable):
eclipse-platform-4.5.2-10.fc23.i686
How reproducible:
always
Steps to Reproduce:
1. run eclipse
2. On the welcome tutorial screen, select "Create a Hello World SWT
application"
3. do as instructed
Actual results:
"Organize imports" has no effect, which leads to the following compile errors:
Display cannot be resolved to a type
Display cannot be resolved to a type
Shell cannot be resolved to a type
Shell cannot be resolved to a type
Expected results:
imports for Display and Shell are added by the "Organize imports" command.
Additional info:
1. manually adding the necessary imports, like
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
has no effect; the compile errors about missing Display and Shell are still
present.
2. The workspace explorer shows some strange files in
org.eclipse.swt.gtk.linux.x86, like org/eclipse/swt/widges/*.orig and
library/*.orig. Should these files really be there? They look like leftover
files from a patch that was applied.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 12 months
[Bug 1333922] New: Eclipse Neon (4.6.0): Many Gtk+ warnings due to broken GUI code
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1333922
Bug ID: 1333922
Summary: Eclipse Neon (4.6.0): Many Gtk+ warnings due to broken
GUI code
Product: Fedora
Version: 24
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: rhbz(a)genodeftest.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Description of problem:
Massive G
Version-Release number of selected component (if applicable):
eclipse-swt-4.6.0-0.5.git201604261105.fc24.x86_64
How reproducible:
always, just start eclipse on Fedora 24 with wayland backend
Steps to Reproduce:
1. start eclipse on a gnome+wayland session
2. have a look at syslog or stdout/stderr
Actual results:
many warnings, most of them caused by improper usage of Gtk+ API:
$ eclipse -clean -data /tmp/test-workspace
CompilerOracle: exclude
org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
CompilerOracle: exclude
org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init>
CompilerOracle: exclude
org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate
CompilerOracle: exclude
org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding
CompilerOracle: exclude
org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile
CompilerOracle: exclude
org/eclipse/tycho/core/osgitools/EquinoxResolver.newState
xkbcommon: ERROR: Key "<LFSH>" added to modifier map for multiple modifiers;
Using Lock, ignoring Shift
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Allocating size to GtkBox 0x7fd3b1d86cf0
without calling gtk_widget_get_preferred_width/height(). How does the code know
the size to allocate?
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -3 (allocation 1,
extents 2x2) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content height -9 (allocation 1,
extents 5x5) while allocating gadget (node button, owner GtkButton)
xkbcommon: ERROR: Key "<LFSH>" added to modifier map for multiple modifiers;
Using Lock, ignoring Shift
(Eclipse:5282): Gtk-WARNING **: Allocating size to GtkBox 0x7fd3b1d86cf0
without calling gtk_widget_get_preferred_width/height(). How does the code know
the size to allocate?
(Eclipse:5282): Gtk-WARNING **: Negative content width -6 (allocation 1,
extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -1 (allocation 1,
extents 1x1) while allocating gadget (node trough, owner GtkProgressBar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -1 (allocation 1,
extents 1x1) while allocating gadget (node trough, owner GtkProgressBar)
(Eclipse:5282): Gtk-WARNING **: Negative content width -13 (allocation 5,
extents 9x9) while allocating gadget (node entry, owner GtkEntry)
Gdk-Message: Window 0x7fd3b1f08e60 is a temporary window without parent,
application will not be able to position it on screen.
Gdk-Message: Window 0x7fd3b1f08e60 is a temporary window without parent,
application will not be able to position it on screen.
Gdk-Message: Window 0x7fd3b1f08e60 is a temporary window without parent,
application will not be able to position it on screen.
Gdk-Message: Window 0x7fd3b1f08e60 is a temporary window without parent,
application will not be able to position it on screen.
(Eclipse:5282): Gdk-WARNING **: gdkcursor-wayland.c:170: Unable to load
x_cursor from the cursor theme
Expected results:
just a few warnings or – at best – no warnings at all.
Additional info:
These warnings were introduced in Gtk+ 3.20 and were not present in Gtk+ 3.18.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 12 months
[Bug 1475521] New: [Wayland] Notification windows are misplaced
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1475521
Bug ID: 1475521
Summary: [Wayland] Notification windows are misplaced
Product: Fedora
Version: 26
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: rhbz2(a)genodeftest.de
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Version-Release number of selected component (if applicable):
eclipse-swt-4.7.0-2.fc26.x86_64
libwayland-client-1.13.0-1.fc26.x86_64
gnome-shell-3.24.3-1.fc26.x86_64
mutter-3.24.4-1.fc26.x86_64
gtk3-3.22.17-2.fc26.x86_64
How reproducible:
Steps to Reproduce:
1. Open eclipse on wayland (with GDK_BACKEND=wayland, which is the default
behavior in a gnome/wayland session.
2. wait for a notification to happen (or trigger an eclipse bug to do so).
Actual results:
Notification is displayed on screen, about 200px from top left corner
Expected results:
Notification should be displayed in bottom right corner.
Additional info:
wayland does not support global window positioning, see
https://developer.gnome.org/gtk3/stable/GtkWindow.html#gtk-window-get-pos...
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 12 months
[Bug 1333480] New: Eclipse won't start a fresh workspace
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1333480
Bug ID: 1333480
Summary: Eclipse won't start a fresh workspace
Product: Fedora
Version: 24
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: pedro.lamarao(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Created attachment 1154254
--> https://bugzilla.redhat.com/attachment.cgi?id=1154254&action=edit
Log file generated in the .metadata directory
Description of problem:
Eclipse won't start a fresh workspace.
Version-Release number of selected component (if applicable):
eclipse-pde-4.6.0-0.5.git201604261105.fc24.x86_64
eclipse-jdt-4.6.0-0.5.git201604261105.fc24.noarch
How reproducible:
Every time Eclipse is opened.
Steps to Reproduce:
1. Open Eclipse from GNOME Shell
2. Select an empty location -- to create a new workspace
Actual results:
Eclipse shows the splash screen then fails to start.
Expected results:
Eclipse shows splash screen then shows de IDE window.
Additional info:
The workspace location is generated with the .metadata directory
containing a .log file. This file is attached to the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 2 months
[Bug 1479433] New: Eclipse acts as a filesystem bomb
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1479433
Bug ID: 1479433
Summary: Eclipse acts as a filesystem bomb
Product: Fedora
Version: rawhide
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: pierreblavy(a)yahoo.fr
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
Description of problem:
When many eclipse plug-ins are installed, it mess-up the file-system until the
computer is unable to boot. At boot, you get few lines on the screen (i.e., the
usual ones I presume), for less than one second, then everything crashed to a
black screen. Cannot launch linux, cannot read the lines on the screen.
How reproducible:
Not always, you have to use eclipse for a while and install a lot of plug ins
to make this crash happen. It doesn't crash after install, we have to use
eclipse to mess up the file system.
Steps to Reproduce:
1. install eclipse
2. install a lot of plug ins (here CDT, PHP plugin, texlipse)
3. use it until it mess up the file system. It can takes a while and a lot of
projects.
Actual results:
- Booting in console only mode (by adding 3 to the grub line) doesn't fix the
problem.
- Fixing the btrfs partition linux is installed on doesn't fix the problem
either. Fix tool says everything is OK.
btrfs check --repair --check-data-csum --progress /dev/sddXXX
btrfs rescue zero-log /dev/sddXXX
btrfs super-recover /dev/sddXXX
btrfs chunk-recover /dev/sddXXX
- The btrfs partition IS readable from a live CD. But we cannot boot on it
while the system is installed on this partition.
- Deleting the eclipse folder FIXES the problem.
I do have this problem now, with eclipse on a btrfs partition. Previously I had
zfs mess when eclipse was on a ZFS partition.
Expected results:
1) Linux should boot, even when the filesystem is messed up by a ton of files
(NOTE the partition is readable from a live CD).
2) BTRFS should do something to prevent file bombing, I prefer an eclipse crash
than a non bootable system, or a messed up partition.
3) ZFS has trouble too. zfs-fuse crashes when eclipse is installed on a zfs
partition, and deleting the eclipse folder is far less complicated on zfs than
on btrfs. zfs-fuse should be patched too to be robust to file bombing.
4) Maybe, if the stars are aligned, you can explain to eclipse developers
what's a database, introduce them to sqlite, and explain them how easier and
better it is to use it instead of file-bombing the file-system. But as far as I
know eclipse, if something can be dirty, it will be dirty.
Additional info : WORKAROUNDS (save your data/os)
--- ZFS ---
Previously I had trouble when eclipse was installed on a ZFS disk. It took me a
while to get access to my data partition as eclipse realy messed up the file
system a lot. Deleting the eclipse folder fixed the problem, but I had a hard
time deleting it, as zfs-fuse crashed and as the messy filesystem has the side
effect of freezing linux.
This is the recipe that worked for me
- try to delete the eclipse folder (zfs may crash)
- if zfs crash : try to delete a few file at a time
- if rm or ls crash: try to delete a few file at a time with guesses like rm -r
a*; rm -r b*; rm -r c* and etc.
Note that the partition remains valid so zfs scrub will NOT fix the problem.
--- BTRFS ---
From my experience, BTRFS leads to less trouble, as long as eclipse IS NOT on
the system partition. When things gets wrong, you can simply boot on live CD,
mount the BTRFS, and to a rm -r eclipse.
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 2 months
[Bug 1469356] New: aether-ant-tasks: Port to XMvn 3.0.0
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1469356
Bug ID: 1469356
Summary: aether-ant-tasks: Port to XMvn 3.0.0
Product: Fedora
Version: rawhide
Component: aether-ant-tasks
Assignee: mizdebsk(a)redhat.com
Reporter: mizdebsk(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eclipse-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msimacek(a)redhat.com
aether-ant-tasks needs porting to XMvn 3.0.0 (or retiring).
aether-ant-tasks has broken dependencies in the rawhide tree:
aether-ant-tasks-1.0.1-6.fc26.noarch requires xmvn-launcher
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 3 months
[Bug 1309687] New: Undeclared uses constraints of Apache HttpComponent bundle cause linkage error at runtime
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1309687
Bug ID: 1309687
Summary: Undeclared uses constraints of Apache HttpComponent
bundle cause linkage error at runtime
Product: Fedora
Version: 23
Component: eclipse
Assignee: akurtako(a)redhat.com
Reporter: andreas.sewe(a)codetrails.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, andjrobins(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, krzysztof.daniel(a)gmail.com,
mat.booth(a)redhat.com, rgrunber(a)redhat.com
External Bug ID: Eclipse Project 488006
Description of problem:
Version-Release number of selected component (if applicable):
1:4.5.1-1.fc23
How reproducible:
Always.
Steps to Reproduce:
1. Install "Eclipse" (version 1:4.5.1-1.fc23) from "Software"
2. Start Eclipse
3. Help > Install New Software "Code Recommenders for Java Developers" from
pre-configured update site <http://download.eclipse.org/releases/mars>
4. Restart Eclipse
5. Try to open Code Recommenders "Model Repositories" view (it is not there, as
bundles for Code Recommenders" are not resolved. This is the *first* problem
6. Start Eclipse with "-clean" option
7. Try to open Code Recommenders "Model Repositories" view again
Actual results:
An error dialog appear: loader constraint violation in interface itable
initialization: when resolving method
"org.apache.http.message.AbstractHttpMessage.getHeaders(Ljava/lang/String;)[Lorg/apache/http/Header;"
the class loader (instance of
org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
org/apache/http/client/methods/AbstractExecutionAwareRequest, and the class
loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for
interface org/apache/http/HttpMessage have different Class objects for the type
[Lorg/apache/http/Header; used in the signature
Expected results:
The "Model Repositories" view opens and (in the background) a download of the
model repository index for is started. Once finished, the view shows 4.5.76
known coordinates for the "mars" model repository.
Additional info:
More details on what the OSGi bundle headers look like can be found in the bug
I filled with the Eclipse Orbit project [1], although they are not the ones who
distribute bundles with faulty Export-Package headers (i.e., headers without
uses constraints).
FWIW, the symptoms seem to be very similar to those of Bug 807044.
[1] <https://bugs.eclipse.org/bugs/show_bug.cgi?id=488006>
--
You are receiving this mail because:
You are on the CC list for the bug.
6 years, 3 months