Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342136

Summary:

Linux Java Build Path/Libraries/Add External Jars dialog does not let me specify full path to jar

Product:

[Eclipse Project] JDT

Reporter:

Miles Daffin <miles.daffin>

Component:

Assignee:

JDT-UI-Inbox <jdt-ui-inbox>

Status:

RESOLVED NOT_ECLIPSE

QA Contact:

Severity:

normal

Priority:

CC:

markus.kell.r

Version:

3.7

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Selection dialog	none

Description Miles Daffin

2011-04-07 06:59:45 EDT

Build Identifier: M20110210-1200

The Linux Java Build Path/Libraries/Add External Jars dialog only allows me to browse for external jars and does not let me do the quicker thing of specifying the full path to the jar I want to add. Where I work most of the jars are on network file shares, so the browsing method of adding them to my build path can take up to 1 hour per jar! Obviously, I can simply add a new entry to the .classpath file, but it would be really nice if the Linux UI has a way of specifying the full path to a jar if known. 

Reproducible: Always

Steps to Reproduce:
1. Open the Java Build Path properties dialog for a java project
2. Goto the Libraries tab and Click Add External Jar
3. When the dialog opens (which can take a while on my system) there is no where to put a path to a jar. I must browse, which is really slow on a network file system.

Comment 1 Markus Keller

2011-04-07 08:39:59 EDT

Created attachment 192726 [details]
Selection dialog

That sounds like a problem of your Linux install. We just use the selection dialog from the OS, and if that is not giving you the option to paste a full path directly, you have to ask for this on the OS level.

As you can see in the attachment, e.g. Gnome has this toggle button to show a Location line where I can paste a full path and then click OK. You can also just paste the path to a folder there and then select multiple files.

And note that if already the selection of a JAR takes so much time, then you won't be happy with that remote JAR anyway, since the compiler frequently accesses these files. Better copy them somewhere on your machine (e.g. into a local project).

Comment 2 Markus Keller

2011-04-07 08:40:07 EDT