Hi,
I've solved the build issue and restarted the release process. It looks
good ...
The changes from PDFBOX-5699 introduced the issue. Moving the scm
definition to the parent pom was correct, but the maven release plugin
stumbled upon the fact the we were holding the parent pom in its own
subdirectory, thje tagging of the release failed.
I've fixed that by moving everything from the parent pom to the main pom
in the root directory. Finally the prepare step of the release works.
But it looks like the second step doesn't :-(
I'll have a look ...
Am 30.10.23 um 20:02 schrieb Andreas Lehmkühler:
Hi,
I've experiencing some issues with the release build for 2.0.30. I have
an idea on how to fix it, but it will take some time, so that I'm going
to postpone the release for a couple of days.
Sorry for the svn noise.
Cheers
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
