Tab completion on import with extended/custom classpath

[ShinyaYoshida]

Hi Patrick and Robert,

Thank you for reporting the issue.

I've already filed the same issue:
https://bugs.openjdk.java.net/browse/JDK-8177650

Can I mark either as duplicated?

Regards,
Shinya Yoshida

2017-04-22 3:40 GMT+09:00 Robert Field <robert.field at oracle.com>:

> Thanks Patrick,
>
> Yes, this is the right place.
>
> I've created:
>
>     https://bugs.openjdk.java.net/browse/JDK-8179090
>
> Too late to address this for JDK 9, but I have it targeted for JDK 10.
>
> -Robert
>
>
>
> On 04/20/17 03:49, Patrick Wright wrote:
>
>> Hi
>>
>> first of all - is this the right place to report problems/requests for
>> JShell, in the version being packaged and deployed with JDK 9 releases?
>>
>> If so - a quick note and possible request. This is with
>> java version "9-ea"
>> Java(TM) SE Runtime Environment (build 9-ea+165)
>> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+165, mixed mode)
>>
>> on OS X.
>>
>> I noticed that if I extend the JShell classpath using the --class-path
>> startup argument, I can import from packages in the JAR, but do not get
>> auto-completion for the import package names.
>>
>> For example, using
>> jshell --class-path
>> ~/.m2/repository/com/google/guava/guava/19.0/guava-19.0.jar
>>
>> if I type
>> import com.<TAB>
>>
>> I get
>> apple oracle sun
>>
>> but I can type
>> import com.google.common.base.*
>>
>> so, "google" is not an auto-complete option following "com."
>>
>> Glad to report this elsewhere if you prefer.
>>
>> Thanks in advance,
>> Patrick
>>
>
>