Bug 1331470

Sopot, please investigate.

(In reply to Peter Backes from comment #0)
> 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 right, these files should not be there are left overs from a patch that is not cleanly applied (there was fuzz) but this likely to be a red herring and not the cause of your problem.

Fortunately, our SWT patches go away with the update to Neon. :-)

(In reply to Peter Backes from comment #0)
> 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.
> 

I confirm it is not working. We're thinking it may have something to do with the way we package the org.eclipse.swt.gtk.linux.x86_64 project in fedora as it is working fine with upstream eclipse.

Created attachment 1152185 [details]
Screenshot

The issue is narrowed down to two jars not being present in org.eclipse.swt.gtk.linux.x86_64. See attachment for a comparison of fedora and upstream versions (left-fedora and right-upstream). They are in the upstream version but they're not in the fedora case. Also deleting the jars in upstream project gives same erroneous behavior (imports not resolved).

Hmm, having the jars embedded that way looks wrong in the upstream version. And all the class files should be there already so I would say the example/whatever is run by the hyperlink needs fixing to setup the project proper.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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

I assume this is still a problem.

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Using Fedora 26, I solved by downloading and installing jdk from http://www.oracle.com/technetwork/java/javase/downloads/index.html

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.

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.