Skip to content

Issue with Akka configuration files #203

@dph10

Description

@dph10

Hello, I am trying to use the jlink-plugin to build an executable of my project, which has a dependency on Akka. As described by their documentation, there needs to be some way to append their text based configuration files for any time of jar bundling operation:

Warning
Akka’s configuration approach relies heavily on the notion of every module/jar having its own reference.conf file. All of these will be discovered by the configuration and loaded. Unfortunately this also means that if you put/merge multiple jars into the same jar, you need to merge all the reference.conf files as well: otherwise all defaults will be lost.
Akka Configuration Docs.

When I try building an executable with the jlink-plugin (using ./gradlew jlink) and then running the image, I do get a configuration file error based on the above statement. They provide some methods for doing this for fat-jars with different build tools here.

The shadowJar plugin has a capability for merging text files as described here, but unfortunately this is for building fat-jars when I really need to build an executable for a custom runtime image. Does the jlink-plugin or jlink itself have this capability? If not, is there someway to add this capability to your tool?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions