Community
Participate
Working Groups
For a "wild card" import, e.g. import com.xyz.*; if the package com.xyz does not exist AND it is not used in the class, it is flagged merely as "not used". Would be better if it was flagged as error "not found", since other compilers will fail when it is indeed not found. I list as minor, since user preferences can be set to flag "not used" as error, instead of warning, but ... that isn't quite the same.
Moving to Core
import com.xyz.*; is properly reported as non-resolved import for me using R2.1 as I would expect. Can you provide more steps to reproduce it ? Are you sure that such a package exists on your filesystem ?
Yes, I think you're right. I originally had, say, two packages, com.xyz; and com.xyz.abc; (and wasn't using either, but had a left over import com.xyz.*;). Then I deleted com.xyz; but left com.xyz.abc; I think maybe it was the other compiler that was in error in telling me that com.xyz.*; could not be resolved, since com.xyz.abc; did still exist. Or maybe its one of those spec ambiguities. Thanks for looking at it.
We indeed will treat empty folder as packages where others will only do so when it contains a first unit. But this is a separate issue for which we already have a bug report. I think our behavior makes more sense though. Closing
