You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most people won't be building these by hand, but it's still not very attractive. I'm thinking of creating a YML or JSON format containing this info that we can ingest instead. It would still be possible to upload a module-info.java, but this new descriptor file would also need to be present to describe the versions of external artifacts. The descriptor could also be given by itself.
This file could be committed to version control or automatically generated by a Gradle or Maven plugin. I'm contemplating the uncreative name: jlink.online.yml.
The artifacts parameter would go away as a result of this change.
The text was updated successfully, but these errors were encountered:
To bundle external dependencies, you currently have to specify them in both the
modules
parameter and theartifacts
parameter. For example:Most people won't be building these by hand, but it's still not very attractive. I'm thinking of creating a YML or JSON format containing this info that we can ingest instead. It would still be possible to upload a
module-info.java
, but this new descriptor file would also need to be present to describe the versions of external artifacts. The descriptor could also be given by itself.Here's an example of something that might work:
This file could be committed to version control or automatically generated by a Gradle or Maven plugin. I'm contemplating the uncreative name:
jlink.online.yml
.The
artifacts
parameter would go away as a result of this change.The text was updated successfully, but these errors were encountered: