Bugzilla – Full Text Bug Listing
| Summary: | User libraries - jars not found upon save | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | kfranic | ||||
| Component: | Core | Assignee: | Jay Arthanareeswaran <jarthana> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | amj87.iitr, markus.kell.r | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
kfranic
Jay, please investigate. Thanks! I am unable to reproduce this bug with eclipse 3.6. I would like to ask few questions: 1. Do you notice anything common about the affected JAR files at all? Like they all are in a particular folder, they are different from the good one in a particular way etc.? 2. Are the same JAR files failing and OK Jars working fine all the time? 3. Is it possible to try this with Eclipse 3.6 release? And finally, is it possible to attach the project with the affected JAR files (one or two will do)? Created attachment 174437 [details]
Video of complete process, project
Video of complete process
Project
>1. Do you notice anything common about the affected JAR files at all? Like they >all are in a particular folder, they are different from the good one in a >particular way etc.? Nothing in particular. >2. Are the same JAR files failing and OK Jars working fine all the time? I have not seen a pattern. >3. Is it possible to try this with Eclipse 3.6 release? Yep. Same behaviour. >And finally, is it possible to attach the project with the affected JAR files >(one or two will do)? Attached+some more. Thanks for all the details. Can I ask you to try one more thing - can you try having the jar files from a location outside the workspace and see if that makes a difference? My guess is that it will. Markus, the issue seems to be around the backslashes instead '/' when a resource is selected from within the workspace and this seem to happen only in Windows 7. Have you come across this kind of problem earlier? (In reply to comment #5) > Thanks for all the details. Can I ask you to try one more thing - can you try > having the jar files from a location outside the workspace and see if that > makes a difference? My guess is that it will. > > Markus, the issue seems to be around the backslashes instead '/' when a > resource is selected from within the workspace and this seem to happen only in > Windows 7. Have you come across this kind of problem earlier? Firstly, this does not happen only on Windows 7, I can see it also on my PC at work which has Windows XP. Secondly, I do not see this problem when jars are referenced with absolute paths. (In reply to comment #6) > Firstly, this does not happen only on Windows 7, I can see it also on my PC at > work which has Windows XP. > > Secondly, I do not see this problem when jars are referenced with absolute > paths. Ah, I assumed it was a Windows 7 only problem because I was not able to reproduce the bug on Windows XP - even with the projects/libraries you gave me. The immediate thing I noticed on my machine was the forward slashes instead of the backward ones. I will give it one more shot and if I can't reproduce the problem, you might have to help me with more questions or perhaps access to the machine where the bug occurs. But we will keep that as a last resort. (In reply to comment #7) > Ah, I assumed it was a Windows 7 only problem because I was not able to > reproduce the bug on Windows XP - even with the projects/libraries you gave me. > The immediate thing I noticed on my machine was the forward slashes instead of > the backward ones. I will give it one more shot and if I can't reproduce the > problem, you might have to help me with more questions or perhaps access to the > machine where the bug occurs. But we will keep that as a last resort. I'm open to questions. But the access, I'm not sure, but we can talk options. Finally, I am able to reproduce the bug. From the video, I observe that the nested folders are created, jar is copied (note that all this inside the project) and immediately the user library is created using the newly added Jar. When the jar is added to the library, there is no error in the dialog. However, when we close the dialog and reopen again, we see the error. When the project is refreshed, the error goes away. Investigating further. On further investigation, this appears to be a non-bug. After fix to bug 133191, whenever possible, user libraries paths are stored as relative to the workspace. And because we just added a resource (JAR) and yet to refresh the workspace, the workspace tree doesn't yet contain the JAR - i.e. ElementTree.includes(IPath) returns false. But once a refresh is done, everything is normal. Markus can confirm this and then I will close this bug. (In reply to comment #10) > On further investigation, this appears to be a non-bug. After fix to bug > 133191, whenever possible, user libraries paths are stored as relative to the > workspace. And because we just added a resource (JAR) and yet to refresh the > workspace, the workspace tree doesn't yet contain the JAR - i.e. > ElementTree.includes(IPath) returns false. But once a refresh is done, > everything is normal. > > Markus can confirm this and then I will close this bug. I can confirm that when I refresh folder holding jars, it works in my case also. But IMHO this is a bug, it may be minor bug, but inconvenient one. If you add something via dialog and Eclipse includes it with relative path, it should be available, this way, as I see it, one of the functionality is partially broken.... This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |