[jsr294-modularity-eg] superpackage files
Eugene Vigdorchik
ven at jetbrains.com
Thu Apr 12 04:07:14 EDT 2007
Alex Buckley wrote:
> As for the location itself, you seem to be saying that it
> should be based on the names of member packages, not the name
> of the superpackage itself. Is that right?
Yes, I think it would allow the IDE to determine if the class is visible from certain place without the need to specify where
super-package.java for that class might exist.
While a separate option for super-package.java is perfectly ok for invoking a standalone compiler, having the user configure the
location of all super package files in the IDE
will be too painful.
> If so, what happens when unrelated superpackages each require
> super-package.java to live in the same location?
That would amount to having multiple superpackages declaration in one super-package.java. So super-package.java would be not about
declaring a single superpackage, but rather telling how a package is split into superpackages.
Eugene.
More information about the jsr294-modularity-eg
mailing list