Skip to content

jpms / modular dagger #2636

@h908714124

Description

@h908714124

I've noticed jlink doesn't work unless every dependency has a module info.
I've tried and got this far:

Error: automatic module cannot be used with jlink

It seems dagger doesn't even set Automatic-Module-Name in the MANIFEST.
Are there any plans to release a dagger version with module-info.java included?

Because currently it seems like code that uses dagger can't be fully modular, and it looks like that means you won't be able use jlink, to make a custom jdk image of it.
Likewise, any library code that uses the dagger annotations will also become a roadblock to modularization.
This seems pretty bad. I've just finished adding dagger to my pet command line parser.
Will I have to rip it out again? Ugh.
Custom runtime images are going to be very important for command line applications, imho.
Please respond.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions