Conversation
|
With the simple conversion mentioned above I'm getting a build failure based on dsbulk-docs: |
|
Problem looks to stem from dsbulk-docs. That component isn't deployed to Maven Central and appears to consist entirely of a couple small Java apps used to generate the settings.md Markdown file and the sample config files in the "manual" directory. It's correct that this project doesn't contribute any Java code to the package to be uploaded to Central Portal; it's the output of these apps in the "manual" directory that represent their contribution. Thing is that this output is used in two separate occasions:
So what's needed here is some way to generalize this functionality into something that can still be used in both places but doesn't present itself as a new component (which therefore introduces the expectation that it will contribute to the distribution). Still working on it. |
|
Removing dsbulk-docs from the list of modules in the build resolves the issue and makes sense conceptually; dsbulk-docs isn't included in what's released to Maven Central and is intended only as a local helper for the build. |
Entirely based off the native-protocol equivalent