Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » This element neither has attached source nor attached Javadoc and hence no information could be foun
This element neither has attached source nor attached Javadoc and hence no information could be foun [message #238833] Tue, 12 December 2006 18:02 Go to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

I get "This element neither has attached source nor attached Javadoc and
hence no information could be found." when I hover over common objects
like SWT shells and buttons. I also don't have object completion.

I just reinstalled Eclipse 3.2 on the weekend, in case that has anything
to do with it.

Is this a JDT issue or an SWT issue ?

Thanks
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238843 is a reply to message #238833] Wed, 13 December 2006 03:40 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>I get "This element neither has attached source nor attached Javadoc and
> hence no information could be found." when I hover over common objects
> like SWT shells and buttons.
>
You probably meant source elements in the Java editor and not "objects"
in some other editor - right?

>I also don't have object completion.
>
>I just reinstalled Eclipse 3.2 on the weekend, in case that has anything
>to do with it.
>
>Is this a JDT issue or an SWT issue ?
>
>
None of these. It's a problem with your workspace. You probably didn't
correctly import the SWT project and hence neither source nor Javadoc is
attached.

Dani

>Thanks
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238888 is a reply to message #238843] Thu, 14 December 2006 17:17 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

Thanks for replying. Comments and questions below.

On Wed, 13 Dec 2006 09:40:12 +0100, Daniel Megert wrote:
>>I get "This element neither has attached source nor attached Javadoc and
>> hence no information could be found." when I hover over common objects
>> like SWT shells and buttons.
>>
> You probably meant source elements in the Java editor and not "objects"
> in some other editor - right?

Right, I think. What do you mean by "some other editor" ? Like the CDT
editor ?

>>I also don't have object completion.
>>
>>I just reinstalled Eclipse 3.2 on the weekend, in case that has anything
>>to do with it.
>>
>>Is this a JDT issue or an SWT issue ?
>>
>>
> None of these. It's a problem with your workspace.

OK.

You probably didn't
> correctly import the SWT project and hence neither source nor Javadoc is
> attached.

What do you mean by "import the SWT project" ? I didn't knowingly import
anything. Everything worked fine before the re install.

There is more to the story. My PC quit a few times. I thought it was an
Eclipse issue so I re installed. Stupid, I know, but it was hard to
troubleshoot. The problem had nothing to do with Eclipse. Now I have the
source/Javadoc problem.

Any further information on rectifying this ?

Thanks
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238897 is a reply to message #238888] Fri, 15 December 2006 03:39 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>Thanks for replying. Comments and questions below.
>
>On Wed, 13 Dec 2006 09:40:12 +0100, Daniel Megert wrote:
>
>
>>>I get "This element neither has attached source nor attached Javadoc and
>>>hence no information could be found." when I hover over common objects
>>>like SWT shells and buttons.
>>>
>>>
>>>
>>You probably meant source elements in the Java editor and not "objects"
>>in some other editor - right?
>>
>>
>
>Right, I think. What do you mean by "some other editor" ? Like the CDT
>editor ?
>
>
>
>>>I also don't have object completion.
>>>
>>>I just reinstalled Eclipse 3.2 on the weekend, in case that has anything
>>>to do with it.
>>>
>>>Is this a JDT issue or an SWT issue ?
>>>
>>>
>>>
>>>
>>None of these. It's a problem with your workspace.
>>
>>
>
>OK.
>
>You probably didn't
>
>
>>correctly import the SWT project and hence neither source nor Javadoc is
>>attached.
>>
>>
>
>What do you mean by "import the SWT project" ? I didn't knowingly import
>anything. Everything worked fine before the re install.
>
>There is more to the story. My PC quit a few times. I thought it was an
>Eclipse issue so I re installed. Stupid, I know, but it was hard to
>troubleshoot. The problem had nothing to do with Eclipse. Now I have the
>source/Javadoc problem.
>
>Any further information on rectifying this ?
>
>
If you open an SWT class does it show the source? If not import the SWT
plug-in using File > Import... > Plug-ins and Fragments.

Dani

>Thanks
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238934 is a reply to message #238897] Sat, 16 December 2006 22:52 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

>>Any further information on rectifying this ?
>>
>>
> If you open an SWT class does it show the source? If not import the SWT
> plug-in using File > Import... > Plug-ins and Fragments.

You were right, it did not show the source code. So I imported
org.eclipse.swt. and org.eclipse.swt.gtk.linux.x86. It made them projects
in my workspace which they were never before.

Completion and holdover info still don't work.

What am I missing ?
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238939 is a reply to message #238897] Sat, 16 December 2006 23:08 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

Here is another tidbit... I was working on an application that had to run
with su privileges, so I temporarily ran Eclipse as su.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238944 is a reply to message #238934] Sun, 17 December 2006 03:27 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

Does this have something to do with CLASSPATH ?

I just renamed the .eclipse folder in my home directory and the .metafile
in my workspace directory and I have the same result, no field assist, etc.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238949 is a reply to message #238934] Sun, 17 December 2006 04:26 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>>>Any further information on rectifying this ?
>>>
>>>
>>>
>>>
>>If you open an SWT class does it show the source? If not import the SWT
>>plug-in using File > Import... > Plug-ins and Fragments.
>>
>>
>
>You were right, it did not show the source code. So I imported
>org.eclipse.swt. and org.eclipse.swt.gtk.linux.x86. It made them projects
>in my workspace which they were never before.
>
>Completion and holdover info still don't work.
>
>What am I missing ?
>
>
It looks as it cannot find the source which comes with a different
plug-in. I suggest you download and install Eclipse again into a fresh
folder and then try again to import SWT and check whether it has source.

Also verify that your project is a plug-in (PDE) project: if the
project's PDE Tools context menu only contains 'Convert Projects to
Plug-in Projects... menu then execute it to convert your project. Then
make sure that in MANIFEST.MF SWT is declared as required project of
your project.

HTH
Dani
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238958 is a reply to message #238949] Sun, 17 December 2006 11:47 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Sun, 17 Dec 2006 10:26:47 +0100, Daniel Megert wrote:

> me2 wrote:
>
>>>>Any further information on rectifying this ?
>>>>
>>>>
>>>>
>>>>
>>>If you open an SWT class does it show the source? If not import the SWT
>>>plug-in using File > Import... > Plug-ins and Fragments.
>>>
>>>
>>>
>>You were right, it did not show the source code. So I imported
>>org.eclipse.swt. and org.eclipse.swt.gtk.linux.x86. It made them
>>projects in my workspace which they were never before.
>>
>>Completion and holdover info still don't work.
>>
>>What am I missing ?
>>
>>
> It looks as it cannot find the source which comes with a different
> plug-in. I suggest you download and install Eclipse again into a fresh
> folder and then try again to import SWT and check whether it has source.

OK.

I renamed my old eclipse executable directory. I removed the .eclipse
folder from my home directory. I renamed my current workspace directory
so that it wouldn't be used.

Then I reinstalled eclipse by unpacking the archive. Then I added ve and
emf and the other plug ins I needed.

I started eclipse. I created a new java project. In the java project I
created a new visual class of type SWT using a shell. I've done this a
dozens of times before.

And then I holdover an SWT widget object, I get "This element neither has
attached source nor attached Javadoc and hence no information could be
found."

> Also verify that your project is a plug-in (PDE) project: if the
> project's PDE Tools context menu only contains 'Convert Projects to
> Plug-in Projects... menu then execute it to convert your project.

Why does it have to be a PDE ? I am using SWT for developing an app that
runs outside of eclipse. So right now my project is just a java project.
I didn't touch the project settings when this started happening. And it
happened for all my swt java projects.

I am totally stumped. Does eclipse have a configuration or meta file
somewhere that I am not aware of ?

Btw, when I add features to my eclipse installation (ve, emf, etc) I don't
see swt, which makes sense because swt is part of eclipse itself. But is
it possible that I got an archive that is missing something or corrupt ?
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238974 is a reply to message #238958] Mon, 18 December 2006 03:17 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>On Sun, 17 Dec 2006 10:26:47 +0100, Daniel Megert wrote:
>
>
>
>>me2 wrote:
>>
>>
>>
>>>>>Any further information on rectifying this ?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>If you open an SWT class does it show the source? If not import the SWT
>>>>plug-in using File > Import... > Plug-ins and Fragments.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>You were right, it did not show the source code. So I imported
>>>org.eclipse.swt. and org.eclipse.swt.gtk.linux.x86. It made them
>>>projects in my workspace which they were never before.
>>>
>>>Completion and holdover info still don't work.
>>>
>>>What am I missing ?
>>>
>>>
>>>
>>>
>>It looks as it cannot find the source which comes with a different
>>plug-in. I suggest you download and install Eclipse again into a fresh
>>folder and then try again to import SWT and check whether it has source.
>>
>>
>
>OK.
>
>I renamed my old eclipse executable directory. I removed the .eclipse
>folder from my home directory. I renamed my current workspace directory
>so that it wouldn't be used.
>
>Then I reinstalled eclipse by unpacking the archive. Then I added ve and
>emf and the other plug ins I needed.
>
>I started eclipse. I created a new java project. In the java project I
>created a new visual class of type SWT using a shell.
>
How is the Shell found? Did you manually add SWT to the Java build path?

Dani

> I've done this a
>dozens of times before.
>
>And then I holdover an SWT widget object, I get "This element neither has
>attached source nor attached Javadoc and hence no information could be
>found."
>
>
>
>>Also verify that your project is a plug-in (PDE) project: if the
>>project's PDE Tools context menu only contains 'Convert Projects to
>>Plug-in Projects... menu then execute it to convert your project.
>>
>>
>
>Why does it have to be a PDE ? I am using SWT for developing an app that
>runs outside of eclipse. So right now my project is just a java project.
>I didn't touch the project settings when this started happening. And it
>happened for all my swt java projects.
>
>I am totally stumped. Does eclipse have a configuration or meta file
>somewhere that I am not aware of ?
>
>Btw, when I add features to my eclipse installation (ve, emf, etc) I don't
>see swt, which makes sense because swt is part of eclipse itself. But is
>it possible that I got an archive that is missing something or corrupt ?
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #238993 is a reply to message #238974] Mon, 18 December 2006 15:31 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Mon, 18 Dec 2006 09:17:17 +0100, Daniel Megert wrote:

> How is the Shell found? Did you manually add SWT to the Java build path?
>
> Dani


What do you mean by "found" ? The application runs fine, so Java must
know where to find the swt class. I have set no paths manually.
Everything is default or empty. Yet the content completion and stuff
doesn't work. It gives me the javadoc or source not available message.

This is really weird.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239002 is a reply to message #238974] Mon, 18 December 2006 17:13 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

Where does Eclipse automatically look for source and Javadoc ? Where does
it expect it to be ?
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239017 is a reply to message #238833] Mon, 18 December 2006 21:41 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: wayne.beaton._NOSPAM_eclipse.org

me2 wrote:
> I get "This element neither has attached source nor attached Javadoc and
> hence no information could be found." when I hover over common objects
> like SWT shells and buttons. I also don't have object completion.
>
> I just reinstalled Eclipse 3.2 on the weekend, in case that has anything
> to do with it.
>
> Is this a JDT issue or an SWT issue ?
>
> Thanks

Sorry, I'm coming into this one late...

If I read things correctly, you're using SWT as part of a plain-old-Java
program, and not as part of an Eclipse application.

I'm thinking that your project may have lost the Java source attachment
(assuming that this is what you did in the first place).

Your project should list the SWT JAR (something like
"org.eclipse.swt.gtk.something-or-other") Right click on that to open
the properties. Then set the Java Source Attachment to point to
" /ECLIPSE_HOME/plugins/org.eclipse.rcp.source.gtk.whatever/sr c/org.eclipse.swt.gtk.whatever/src.zip "

(the "whatever" parts will be specific to the version of Eclipse that
you're running). Note that I'm using a classpath variable; you can also
use an absolute path (less portable).

If you were building an Eclipse application, this should all happy
automagically (assuming that you're starting from the SDK). No so for
plain-old-Java+SWT applications.

HTH,

Wayne
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239022 is a reply to message #238993] Tue, 19 December 2006 04:29 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>On Mon, 18 Dec 2006 09:17:17 +0100, Daniel Megert wrote:
>
>
>
>>How is the Shell found? Did you manually add SWT to the Java build path?
>>
>>Dani
>>
>>
>
>
>What do you mean by "found" ?
>
I wanted to ask how you have setup your Java project. You can only use
SWT classes if SWT is found on the Java build path. I suppose you have
set this up manually. If you, you also have to attach Javadoc and/or the
source manually. See the answer to your other question on how to find
source.

Dani

>The application runs fine, so Java must
>know where to find the swt class. I have set no paths manually.
>Everything is default or empty. Yet the content completion and stuff
>doesn't work. It gives me the javadoc or source not available message.
>
>This is really weird.
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239026 is a reply to message #239002] Tue, 19 December 2006 05:28 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>Where does Eclipse automatically look for source and Javadoc ? Where does
>it expect it to be ?
>
>
It depends on which package you downloaded (SWT only, Platform SDK, RCP
SDK or Eclipse SDK). If you only downloaded SWT package then the source
is inside the same directory as the JAR and adding the JAR should detect
the src.zip automatically (there is no Javadoc with this package). If
you downloaded an SDK then both source
(org.eclipse.rcp.source.win32.win32.x86_3.3.0.<version stamp here>) and
Javadoc are in separate plug-ins and it is assumed you are also writing
a plug-in (project) and only then finds the source automatically.
However, you can manually attach the source to your SWT JAR.

Dani
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239054 is a reply to message #239017] Tue, 19 December 2006 14:42 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Mon, 18 Dec 2006 21:41:23 -0500, Wayne Beaton wrote:

> Sorry, I'm coming into this one late...

No problem. Better late than never.

> If I read things correctly, you're using SWT as part of a plain-old-Java
> program, and not as part of an Eclipse application.

What do you mean by plain old Java app ? I'm building an app that runs
outside of Eclipse, yes.

> I'm thinking that your project may have lost the Java source attachment
> (assuming that this is what you did in the first place).

Except that this happens for all projects, even new ones and I've never
before fiddled with this as a manual setting. Nevertheless, I will
explore what you are saying.

> Your project should list the SWT JAR (something like
> "org.eclipse.swt.gtk.something-or-other")

It does.

Right click on that to open
> the properties. Then set the Java Source Attachment to point to
> " /ECLIPSE_HOME/plugins/org.eclipse.rcp.source.gtk.whatever/sr c/org.eclipse.swt.gtk.whatever/src.zip "

OK... When I look at Java Source Attachment in the properties, It says..

"JAR belongs to the container "Standard Widget Toolkit (SWT). To
configure the source attachment, go directly to the corresponding
configuration page (For example for JRSs go to 'Installed JREs' page in
the preferences)."

So I go to Windows->Preferences->Java and I don't see anything about
attaching javadoc to SWT.

> If you were building an Eclipse application, this should all happy
> automagically (assuming that you're starting from the SDK). No so for
> plain-old-Java+SWT applications.

I never had a problem prior to this and all my apps are regular apps, that
run outside Eclipse.

Thanks.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239059 is a reply to message #239026] Tue, 19 December 2006 14:46 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Tue, 19 Dec 2006 11:28:56 +0100, Daniel Megert wrote:

> me2 wrote:
>
>>Where does Eclipse automatically look for source and Javadoc ? Where does
>>it expect it to be ?
>>
>>
> It depends on which package you downloaded (SWT only, Platform SDK, RCP
> SDK or Eclipse SDK). If you only downloaded SWT package then the source
> is inside the same directory as the JAR and adding the JAR should detect
> the src.zip automatically (there is no Javadoc with this package). If
> you downloaded an SDK then both source
> (org.eclipse.rcp.source.win32.win32.x86_3.3.0.<version stamp here>) and
> Javadoc are in separate plug-ins and it is assumed you are also writing
> a plug-in (project) and only then finds the source automatically.
> However, you can manually attach the source to your SWT JAR.


Thanks for staying with me on this, Dani. I downloaded and am running
the Eclipse SDK.

"If
> you downloaded an SDK then both source
> (org.eclipse.rcp.source.win32.win32.x86_3.3.0.<version stamp here>) and
> Javadoc are in separate plug-ins and it is assumed you are also writing
> a plug-in (project) and only then finds the source automatically.
> However, you can manually attach the source to your SWT JAR."

Could you lead me through doing this, just to make sure I have it right ?

Thanks
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239064 is a reply to message #239026] Tue, 19 December 2006 15:04 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

OK, here is something interesting.

I started a new project, with a visual class. And the class is based on
an SWT Shell, so the SWT object is installed in the project. So far so
good.

Now if I right click the SWT object and select configure, I get an "Edit
Library" window.

It gives me 3 options for "Jar and Library Source Location"

1) IDE Platform- which lists 3.2.2.v3235a.
2) PDE Target- which lists 3.2.2.v3235h
3) Custom location. The Custom location lists
..../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v32 35a.jar. And if
I select that option, it tells me "Invalid Directory Path" even though...

ls .../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v323 5a.jar
..../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v32 35a.jar

So it is obviously NOT an invalid path.

But, if I browse to that file and double click it, ark opens it. It has
all the classes in it, but I don't see source anywhere. I don't know
enough about Java to know if the source should be here or not.

Thanks.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239075 is a reply to message #239059] Wed, 20 December 2006 02:21 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>On Tue, 19 Dec 2006 11:28:56 +0100, Daniel Megert wrote:
>
>
>
>>me2 wrote:
>>
>>
>>
>>>Where does Eclipse automatically look for source and Javadoc ? Where does
>>>it expect it to be ?
>>>
>>>
>>>
>>>
>>It depends on which package you downloaded (SWT only, Platform SDK, RCP
>>SDK or Eclipse SDK). If you only downloaded SWT package then the source
>>is inside the same directory as the JAR and adding the JAR should detect
>>the src.zip automatically (there is no Javadoc with this package). If
>>you downloaded an SDK then both source
>>(org.eclipse.rcp.source.win32.win32.x86_3.3.0.<version stamp here>) and
>>Javadoc are in separate plug-ins and it is assumed you are also writing
>>a plug-in (project) and only then finds the source automatically.
>>However, you can manually attach the source to your SWT JAR.
>>
>>
>
>
>Thanks for staying with me on this, Dani.
>
np.

> I downloaded and am running
>the Eclipse SDK.
>
>
Since you have the Eclipse SDK downloaded let's do it the easy way:

1. start your workspace
2. File > Import... > Plug-ins and Fragments
3. click 'Next'
4. verify that the top most checkbox is checked and that the location
points to your Eclipse installation
if not: got to the PDE Target preference page and reset the settings
5. select 'Binary project'
6. click 'Next'
7. on the left side select org.eclipse.swt
8. click 'Add'
9. click 'Required Plug-ins'
10. click 'Finish'
11. now check that these steps worked:
use Ctrl+Shift+T to open an SWT type (e.g. Display) and verify
that source is shown in the editor
12. open your Java project's build path property page
13. make sure there is NO swt.jar under 'Libraries'
14. on the 'Projects' tab add all the org.eclipse.swt* projects that you
imported under step 10.
15. click 'OK'

You should now be setup correctly. In the future if you need to switch
to a new SWT version simply install the new version and repeat steps 1 -10.

HTH
Dani

>"If
>
>
>>you downloaded an SDK then both source
>>(org.eclipse.rcp.source.win32.win32.x86_3.3.0.<version stamp here>) and
>>Javadoc are in separate plug-ins and it is assumed you are also writing
>>a plug-in (project) and only then finds the source automatically.
>>However, you can manually attach the source to your SWT JAR."
>>
>>
>
>Could you lead me through doing this, just to make sure I have it right ?
>
>Thanks
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239079 is a reply to message #239064] Wed, 20 December 2006 02:21 Go to previous messageGo to next message
Eclipse UserFriend
me2 wrote:

>OK, here is something interesting.
>
>I started a new project, with a visual class. And the class is based on
>an SWT Shell, so the SWT object is installed in the project. So far so
>good.
>
>Now if I right click the SWT object and select configure, I get an "Edit
>Library" window.
>
>It gives me 3 options for "Jar and Library Source Location"
>
>1) IDE Platform- which lists 3.2.2.v3235a.
>2) PDE Target- which lists 3.2.2.v3235h
>3) Custom location. The Custom location lists
> .../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v323 5a.jar. And if
>I select that option, it tells me "Invalid Directory Path" even though...
>
>
Might a problem with long paths. Please file a bug report against JDT UI.

Dani

>ls .../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v323 5a.jar
> .../eclipse/plugins/org.eclipse.swt.gtk.linux.x86_3.2.2.v323 5a.jar
>
>So it is obviously NOT an invalid path.
>
>But, if I browse to that file and double click it, ark opens it. It has
>all the classes in it, but I don't see source anywhere. I don't know
>enough about Java to know if the source should be here or not.
>
>Thanks.
>
>
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239104 is a reply to message #239075] Wed, 20 December 2006 21:53 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Wed, 20 Dec 2006 08:21:16 +0100, Daniel Megert wrote:
I followed your instructions... feedback below.

> Since you have the Eclipse SDK downloaded let's do it the easy way:
>
> 1. start your workspace
> 2. File > Import... > Plug-ins and Fragments
> 3. click 'Next'
> 4. verify that the top most checkbox is checked and that the location
> points to your Eclipse installation

It did. No problems so far.

> if not: got to the PDE Target preference page and reset the settings
> 5. select 'Binary project'
> 6. click 'Next'
> 7. on the left side select org.eclipse.swt
> 8. click 'Add'
> 9. click 'Required Plug-ins'
> 10. click 'Finish'
> 11. now check that these steps worked:
> use Ctrl+Shift+T to open an SWT type (e.g. Display) and verify
> that source is shown in the editor

This does not work. If I highlight Display, I get:

The source attachment does not contain the source for the file
Display.class. You can change the source attachment by clicking Change
Attached Source below.

> 12. open your Java project's build path property page

Project->Properties-> Java Build Path

> 13. make sure there is NO swt.jar under 'Libraries'

SWT is there and under it is org.eclipse.swt.gtk.linux.x86. And under
Native library location it has.../workspace/org.eclipse.swt.gtk.linux.x86/
- non modifiable.

> 14. on the 'Projects' tab add all the org.eclipse.swt* projects that you
> imported under step 10.

"Build path contains duplicate entry: 'org.eclipse.swt.gtk.linux.x86' for
project test" So I removed it here.

> 15. click 'OK'
>
> You should now be setup correctly. In the future if you need to switch
> to a new SWT version simply install the new version and repeat steps 1 -10.

It works now.

FWIW, I have never had to manually add anything to do with SWT to my
projects before.

Thanks for your help.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239120 is a reply to message #239104] Wed, 20 December 2006 22:30 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Thu, 21 Dec 2006 02:53:51 +0000, me2 wrote:

>
> It works now.
>
> FWIW, I have never had to manually add anything to do with SWT to my
> projects before.
>
> Thanks for your help.

I spoke too soon. It quit again !

I'm logging it as a bug.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239125 is a reply to message #239104] Wed, 20 December 2006 22:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

On Thu, 21 Dec 2006 02:53:51 +0000, me2 wrote:

> It works now.
>
> FWIW, I have never had to manually add anything to do with SWT to my
> projects before.
>
> Thanks for your help.

I am getting an error message now:

Create remote VM for Visual Editor for Java (Time of error:...)
org.eclipse.swt does not exist
org.eclipse.swt does not exist
org.eclipse.swt does not exist
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #239128 is a reply to message #239125] Thu, 21 December 2006 00:34 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: me.somewhere.com

I got it to work. I think there is a bug in the install features plugin.

When I was reinstalling before, I was installing the SDK by downloading the
archive from eclipse.org. Then I was installing all my features by
selecting various components. VE, EMF, JDT, CDT, etc. For whatever
reason, I think that SWT was getting installed without source or something
was wrong with the SWT installation.

This time when I reinstalled, I selected everything. And now it works.

I noticed a couple other hickups with installing that way. One was a
dependency with VE, whereby it wanted a package and you'd select the
package and it would still want it. But if you deleted VE and then added
it again, the dependency was fine.

Anyway, it works.

Thanks for your help, Dani.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #240739 is a reply to message #239128] Wed, 14 February 2007 17:01 Go to previous messageGo to next message
Eclipse UserFriend
I have the same problem with SWT (but not with other libs in my proj),
after trying the various cures mentioned in this thread...

In particular, importing plugins and fragments as suggested shows only
an old swt-...3235.jar, which is a leftover from previous upgrades: the
current version 3326 is duly installed, but does not appear in that
list, nor is the latest jar in the plugins dir.

If I delete SWT from my project buildpath and then reattach (add
library, SWT library), only the previous version is shown as default
with IDE plattform.

So, it looks that when I imported SWT from CVS (after deleting it,
together with swt.win32.win32.x86) into the workspace, I am still using
references to a previous version.

Any ideas? TIA

me2 wrote:
> I got it to work. I think there is a bug in the install features plugin.
>
> When I was reinstalling before, I was installing the SDK by downloading the
> archive from eclipse.org. Then I was installing all my features by
> selecting various components. VE, EMF, JDT, CDT, etc. For whatever
> reason, I think that SWT was getting installed without source or something
> was wrong with the SWT installation.
>
> This time when I reinstalled, I selected everything. And now it works.
>
> I noticed a couple other hickups with installing that way. One was a
> dependency with VE, whereby it wanted a package and you'd select the
> package and it would still want it. But if you deleted VE and then added
> it again, the dependency was fine.
>
> Anyway, it works.
>
> Thanks for your help, Dani.
Re: This element neither has attached source nor attached Javadoc and hence no information could be [message #240754 is a reply to message #240739] Thu, 15 February 2007 03:27 Go to previous message
Eclipse UserFriend
I lost track how this began to happen (SWT javadoc tooltips were OK a
few days back), but I fixed it:

1) Remove SWT from build path (it was added to project using Build Path
-> Add Library -> Std Widget TK (SWT))

2) Configure Build Path -> add project org.eclipse.swt (or, as I did,
just quick fix over import org.eclipse.swt.xxx, then choosing import
project org.eclipse.swt)

The plugins directory is still full of whatever leftovers, but now my
projs are referencing the right SWT inside my workspace...

MaxDiaz wrote:
> I have the same problem with SWT (but not with other libs in my proj),
> after trying the various cures mentioned in this thread...
>
> In particular, importing plugins and fragments as suggested shows only
> an old swt-...3235.jar, which is a leftover from previous upgrades: the
> current version 3326 is duly installed, but does not appear in that
> list, nor is the latest jar in the plugins dir.
>
> If I delete SWT from my project buildpath and then reattach (add
> library, SWT library), only the previous version is shown as default
> with IDE plattform.
>
> So, it looks that when I imported SWT from CVS (after deleting it,
> together with swt.win32.win32.x86) into the workspace, I am still using
> references to a previous version.
>
> Any ideas? TIA
>
> me2 wrote:
>> I got it to work. I think there is a bug in the install features plugin.
>>
>> When I was reinstalling before, I was installing the SDK by
>> downloading the
>> archive from eclipse.org. Then I was installing all my features by
>> selecting various components. VE, EMF, JDT, CDT, etc. For whatever
>> reason, I think that SWT was getting installed without source or
>> something
>> was wrong with the SWT installation.
>>
>> This time when I reinstalled, I selected everything. And now it works.
>> I noticed a couple other hickups with installing that way. One was a
>> dependency with VE, whereby it wanted a package and you'd select the
>> package and it would still want it. But if you deleted VE and then added
>> it again, the dependency was fine.
>>
>> Anyway, it works.
>> Thanks for your help, Dani.
Previous Topic:Migrating a plugin that uses org.eclipse.jdt.internal.*
Next Topic:need some projects with junit test cases
Goto Forum:
  


Current Time: Tue Nov 04 08:47:00 EST 2025

Powered by FUDForum. Page generated in 0.14932 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top