Must have been hours of pain... Thanks for doing all this.
Tilman
On 01.11.2023 20:28, Andreas Lehmkühler wrote:
I did it. I fixed most of the issues so that I was able to cut the
2.0.30 release. There is one issue left, as the antrun plugin still
doesn't work automatically so that I had to tr
I did it. I fixed most of the issues so that I was able to cut the
2.0.30 release. There is one issue left, as the antrun plugin still
doesn't work automatically so that I had to trigger it manually at the
end of the process.
I'm going to investigate that one later, for today I'm done. I'll po
I've fixed an issue due to a major update of the maven-antrun-plugin and
ran into the next one :-(
Stay tuned ...
Am 01.11.23 um 13:32 schrieb Andreas Lehmkühler:
Hi,
I've solved the build issue and restarted the release process. It looks
good ...
The changes from PDFBOX-5699 introduced th
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
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
-
Hi,
sorry for all the noise - my mistake(s)
Maruan Sahyoun
