I have a mixed kotlin/java multi-module project that uses src/main/java for
the java code and src/main/kotlin for kotlin code.
For the java-only projects, everything is fine. sourceDirectory points to
src/main/java, testSourceDirectory points to src/test/java.
We activate a specific profile that
You will get zero participation in that case. I have one mailbox with my
mailing lists that I check from time to time. If a discussion is not there,
I will not go and look for it. Neither to a bug tracker (dozens of projects
and hundreds of issues with discussions) nor a chat system where tens of
c
Hello fellow Maven & JPMS struggler!
I summarized the state of things for Jdbi here:
https://github.com/jdbi/jdbi/blob/master/JPMS-SUPPORT.md
My current belief is that there is no good path forward for projects to
transition from non-JPMS to JPMS unless you are willing to rework your
maven module
The sonatype nexus staging plugin at this point seems abandoned. Last
relevant commit/release was 17 months (!) ago, they killed the bug tracker
and removed all references to JIRA from the code.
The plugin does not work well in multi-module scenarios where the last
module does not commit an artifa
I use testng and it seems to work fine, fwiw. But I *have* noticed a
difference in the nexus-staging-plugin: it's not autoreleasing under 4.0
even though I have it configured to do so and does just fine under 3.9.4.
Haven't had a chance to dig in to that one.
On Sun, Aug 27, 2023 at 6:21 PM Mark