Bug 293714 - Adding jar sources generates an error
Summary: Adding jar sources generates an error
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: IAM (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-29 14:30 EDT by Brice Dutheil CLA
Modified: 2012-01-05 13:10 EST (History)
1 user (show)

See Also:


Attachments
maven jface error log (6.57 KB, application/octet-stream)
2009-10-29 14:30 EDT, Brice Dutheil CLA
no flags Details
unhandled event error log (5.72 KB, application/octet-stream)
2009-10-29 14:31 EDT, Brice Dutheil CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brice Dutheil CLA 2009-10-29 14:30:27 EDT
Created attachment 150859 [details]
maven jface error log

While using Eclipse 3.5 and adding a source lookup path.

At runtime (or not), if a class has no sources, Eclipse propose an editor view
with a button labelled "Edit Source Lookup Path...".

So following these actions :
Edit Source Lookup Path > Add > Selecting "Java Library" > OK > Selecting
"Maven Classpath Container Page" > Next

Well nothing happens, expect in the Error Log view : an entry "Unhandled event
loop" is logged

And when double clicking on "Maven Classpath Container Page", i got a error
popop with the following : 
"An error has occurred. See error log for more details.
null argument:Apache Maven Classpath Container has no page control"

The error log entry is "Problems occurred when invoking code from plug-in:
"org.eclipse.jface".", the details are attached in this bug.
Comment 1 Brice Dutheil CLA 2009-10-29 14:31:03 EDT
Created attachment 150860 [details]
unhandled event error log
Comment 2 Brice Dutheil CLA 2009-10-29 14:34:14 EDT
Btw both errors seems to be related to a missing class.
Comment 3 Carlos Sanchez CLA 2009-11-18 19:11:26 EST
> At runtime (or not), if a class has no sources, Eclipse propose an editor view
> with a button labelled "Edit Source Lookup Path...".

Actually what I see is 

Source not found
The JAR of this class file belongs to continer 'Maven Classpath Container' which does not allow modifications to source attachments on its entries.

---

in the end, the Maven container does not support attaching sources, they are automatically fetched from the repository and IAM does not support manual edition
Comment 4 Brice Dutheil CLA 2009-11-19 05:19:11 EST
(In reply to comment #3)
> > At runtime (or not), if a class has no sources, Eclipse propose an editor view
> > with a button labelled "Edit Source Lookup Path...".
> 
> Actually what I see is 
> 
> Source not found
> The JAR of this class file belongs to continer 'Maven Classpath Container'
> which does not allow modifications to source attachments on its entries.

I really don't see that, I'm using Eclipse 3.5 and IAM 0.10.0.20090627
took from this update site : http://q4e.googlecode.com/svn/trunk/updatesite-iam/



The real problem is the sources jar is present in the local repository, when browsing in the Maven Container in the Java Perspective, I can acces jars and see the source if it's present! However, in debug mode, when the application is suspended, the sources for the same jar are not anymore available (or seen by the container).

And we can't add then to the launch configuration, following the above mentionned steps.