Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [External] : Re: JPMS requirements discussion


On Jun 8, 2021 at 2:08:35 PM, Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:
On 6/8/21 8:19 PM, Jason Greene wrote:


On Tue, Jun 8, 2021 at 11:05 AM Mark Thomas <markt@xxxxxxxxxx
<mailto:markt@xxxxxxxxxx>> wrote:
 > My expectation is that most API JARs will need to provide more metadata
 > than just an automatic module name in the manifest. If that is not the
 > case then the argument for all API JARs being required to provide a
 > module-info.class may not be as strong as I thought it was. That said,
 > my preference would still be to provide module-info.class files.

The biggest difference would be the ability to affect exports.


and opens, thus reflection access - many specs do require it to
access/scan user-defined classes. If vendor neutrality is one of the
goals, one should not be required to use --add-opens <toVendorImpl> on
the command line (or equivalent in his descriptor) but to define opens
xy to specName and let the spec API jar do the right thing - delegate
that particular "opens" to the discovered inmplementation; IF required
and unless there exists another solution..

Right that works too. You can use a qualified open to an automatic module from a standard module (impl opens to spec). You can also do the reverse since automatic modules grant open to everything.



thanks,
--lukas

 Although,
in exchange for significantly reduced visibility and added dependency
management complexity. The export restrictions are insufficient to be an
access control mechanism, so really more of a warning. If you have an
API/impl split as is the case of spec + multi-vender then its
applicability is pretty limited.

 >
 > Mark
 > _______________________________________________
 > jakartaee-platform-dev mailing list
 > jakartaee-platform-dev@xxxxxxxxxxx
<mailto:jakartaee-platform-dev@xxxxxxxxxxx>
 > To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!JAUh_KNF_ZNoShN1LuNEwtJVGD2nmbAMEUf_i8YfW4wm1nNCfLtZY2A-_qednrM7aR8$>

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!JAUh_KNF_ZNoShN1LuNEwtJVGD2nmbAMEUf_i8YfW4wm1nNCfLtZY2A-_qednrM7aR8$


_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top