> I'm pretty sure this can be solved without touching the maven startup
scripts.
> And I don't like the idea to hack the script
Agreed. I did not like the idea either, and even worse, I was unable to
reproduce the results I had.
Am Mo., 14. Dez. 2020 um 21:58 Uhr schrieb Robert Scholte <
I'm pretty sure this can be solved without touching the maven startup scripts.
And I don't like the idea to hack the script because one plugin has issues.
I expect good help on your question on the jigsaw mailinglist.
Robert
On 14-12-2020 15:21:04, Benjamin Marwell wrote:
I was able to provide a
Hi,
The Idea of making a signature by java code without an external binary is
very good.
I have plans to automate some of CI/CD and such plugin will be very useful
for me.
I can customise it for easy use with CI system
So waiting for you,
I will release it under my github organization,
TBH, the notion that the build script (whatever the tool) is just copied
wholesale into a published artifact is a little weird. That's part of what
threw me off - I think that our CI system may have been using
help:effective-pom to add a copy of the rendered pom into the CI reporting,
but I may be
Il giorno lun 14 dic 2020 alle ore 15:21 Benjamin Marwell <
bmarw...@apache.org> ha scritto:
> I was able to provide a test, but the only solution to the underlying I
> found was to modify the mvn start script by adding the missing modules (or
> maybe even better: all system modules).
>
I tried
I was able to provide a test, but the only solution to the underlying I
found was to modify the mvn start script by adding the missing modules (or
maybe even better: all system modules).
>From what I could see from slack, plexus compiler would need to be a
module, requiring jdk.javadoc.
Thus, we
