Home » Language IDEs » Java Development Tools (JDT) » This element neither has attached source nor attached Javadoc and hence no information could be foun 
 |   |   |   |   |   |   |   |   |   |   |   |   |   |   |  
| 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    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
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 #239128 is a reply to message #239125] | 
Thu, 21 December 2006 00:34    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
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    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
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   | 
 
Eclipse User  | 
 | 
 | 
   | 
 
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.
 |  
 |  
  |   
Goto Forum:
 
 Current Time: Tue Nov 04 08:47:00 EST 2025 
 Powered by  FUDForum. Page generated in 0.14932 seconds  
 |