Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [External] : Re: module-info tests

On 10/6/21 11:05 PM, Scott Stark wrote:
Ok, thanks, could be useful.

sounds like one option. The other can be to update TCKs to allow using/loading API jar to test from the module path. In the end it does not matter whether the implementation comes from class path or module path, it is expected that the API jar is able to locate an implementation in both places


As long as the api jar in your implementation passes the signature tests, internal dependencies should not matter.

On Oct 6, 2021 at 3:29:49 PM, Thiago Henrique Hupner <thihup@xxxxxxxxx <mailto:thihup@xxxxxxxxx>> wrote:


    It is possible to read a module using the
    ModuleDescriptor::read (
    Maybe that is useful.

    One thing that might be tricky to answer is:
    Can API modules depend on other libraries?

    I have a use case: My library JoEL is a Expression Language
    implementation. Currently, I'm using the JDK.Dynalink module in the
    API, as an implementation detail, as most of the API requires to
    provide an implementation of it in the same class (like
    jakarta.el.BeanELResolver). However, if a user wants to use it,
    their JDK has to contain the JDK.Dynalink module.

    In this case, it is a module that comes with the Standard JDK, but
    it is not an official module, but I guess the same rules would apply
    for 3rd party dependencies.

    What do you think?

jakartaee-platform-dev mailing list
To unsubscribe from this list, visit;!!ACWV5N9M2RV99hQ!desZh5fSh19A0ojjVI-ZY1B8-wIOWubSIzj-LjJp9F5TPAbta_Ukh22m_fWPW6G85-o$

Back to the top