Description David Audel 2007-07-11 04:34:31 EDT

from bug 188876

package proposals are always fully qualified and could be unqualified.

If the following class is existing

package p1.p2.p3;
public class Foo {}

1) the completion of

import p1| // complete at |

propose the completion strings
'p1.*;'
'p1.p2.*;'
'p1.p2.p3.*;'

2) the completion of

import p1.p2| // complete at |

propose the completion strings
'p1.p2.*;'
'p1.p2.p3.*;'

we could propose instead the completion strings
'p2.*;'
'p2.p3.*;'

3) the completion of

void foo() {
  p1| // complete at |
}

propose the completion strings
'p1'
'p1.p2'
'p1.p2.p3'

4) the completion of

void foo() {
  p1.p2| // complete at |
}

propose the completion strings
'p1.p2'
'p1.p2.p3'

we could propose instead the completion strings
'p2'
'p2.p3'


The completion of package has some specificity 
- package and subpackage are proposed
- jdt/text use completion string as label in the proposals list.
  jdt/text could use instead CompletionProposal#getDeclaringSignature() outside an import statement but inside an import statement only the completion string contains the on demand character '*'. 

So if we want to propose unqualified package (eg 'p2.p3;*;') 
- jdt/text should display unqualified package as label 'p2.p3.*;'
or
- jdt/core should add API to identify on demand imports to allow jdt/text to build the fully qualifed label