is ClassLoader.loadClass() supposed to work on module-info classes?

Ali Ebrahimi ali.ebrahimi1781 at
Sat Dec 5 10:39:46 UTC 2015


On Sat, Dec 5, 2015 at 1:39 PM, Alan Bateman <Alan.Bateman at>

> On 05/12/2015 07:00, Ali Ebrahimi wrote:
>> :
>> module FOO.aop{
>>       implements FOO.api;
>> }
>> In other word, consumer module doesn't know any think about implementing
>> module since here we have contract and that is API module. think of
>> today's
>> interface.
>> In the distant past, this was known here as aliasing or substitution, and
> "provides FOO.api" in the module declaration. It essentially allowed a
> module to have several names. It was complicated at the time because of
> versioning. It's not in the current proposal, I don't know if the JSR will
> go there.

I think since there is no versioning in play so we don't have (all) your
past problems. But in end we have clean design for supporting best
practices (Contract based modular programming).


Best Regards,
Ali Ebrahimi

More information about the jigsaw-dev mailing list