Build failed in Jenkins: PDFBox » PDFBox-2.0.x » Apache PDFBox parent #1175

See Changes: -- Established TCP socket on 33429 maven35-agent.jar already up to date maven35-interceptor.jar already up to date

Build failed in Jenkins: PDFBox » PDFBox-2.0.x #1175

See Changes: -- [...truncated 2.36 KB...] [INFO] Apache PDFBox parent [pom] [HUDSON] Collecting dependencies info[INFO] Apache

Re: NVD update hangs during release build

I meant adding true to the part. Something isn't ok with NVD, maybe it got worse since then: https://blog.fefe.de/?ts=9b0740e0 https://www.heise.de/news/Sicherheitsforscher-genervt-Luecken-Datenbank-NVD-seit-Wochen-unvollstaendig-9656574.html Tilman On 20.03.2024 22:05, Andreas Lehmkühler

Re: NVD update hangs during release build

Mhmm - is there a way to build locally and test the NVD update? Ran it on a different project I have for a client locally and NVD update worked without issues and without an API key. BR Maruan Am Donnerstag, dem 21.03.2024 um 08:36 +0100 schrieb Tilman Hausherr: > I meant adding true to the

Build failed in Jenkins: PDFBox » PDFBox-2.0.x #1177

See Changes: -- Started by user Tilman Hausherr Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds36 (ubuntu) in workspace

Build failed in Jenkins: PDFBox » PDFBox-2.0.x » Apache PDFBox parent #1177

See Changes: -- Established TCP socket on 39915 maven35-agent.jar already up to date maven35-interceptor.jar already up to date

Build failed in Jenkins: PDFBox » PDFBox-2.0.x » Apache PDFBox parent #1178

See Changes: -- Established TCP socket on 35659 maven35-agent.jar already up to date maven35-interceptor.jar already up to date

Build failed in Jenkins: PDFBox » PDFBox-2.0.x #1178

See Changes: -- Started by user Tilman Hausherr Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds42 (tmp-22 ubuntu) in

[VOTE] Release Apache PDFBox 2.0.31

Hi, a candidate for the PDFBox 2.0.31 release is avaiable at: https://dist.apache.org/repos/dist/dev/pdfbox/2.0.31/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/pdfbox/tags/2.0.31/ The SHA-512 checksum of the archive is

Re: NVD update hangs during release build

I've simply deactivated the plugin as proposed, so that we can do the release. I don't like the Idea to go back to an old version. I'm pretty sure someone will fix that issue as we aren't the only ones using that plugin. Andreas Am 21.03.24 um 18:13 schrieb sahy...@fileaffairs.de: OK - can

Re: [VOTE] Release Apache PDFBox 2.0.31

+1 Tilman On 21.03.2024 18:51, Andreas Lehmkühler wrote: Hi, a candidate for the PDFBox 2.0.31 release is avaiable at:     https://dist.apache.org/repos/dist/dev/pdfbox/2.0.31/ The release candidate is a zip archive of the sources in:    

Re: NVD update hangs during release build

Jeremy Long wrote something that I haven't really understood. Maybe it means building the NVD archive on a separate system and then transferring it. https://github.com/jeremylong/DependencyCheck/issues/6515#issuecomment-2011824975 However a leter message in the same issue made more sense, I'm

Jenkins build is back to normal : PDFBox » PDFBox-2.0.x » Apache PDFBox parent #1179

See - To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail:

Re: NVD update hangs during release build

OK - can replicate the issue too. works for me locally up to dependency-check-maven 8.4.3 - would that be an option? BR Maruan Am Donnerstag, dem 21.03.2024 um 17:38 +0100 schrieb Tilman Hausherr: > add > > -Ppedantic > > Tilman > > On 21.03.2024 17:28, sahy...@fileaffairs.de wrote: > > which

Re: NVD update hangs during release build

which mvn cmd do in need to issue to trigger the check? mvn clean install didn't for me. Am I missing something? BR Maruan Am Donnerstag, dem 21.03.2024 um 17:24 +0100 schrieb Tilman Hausherr: > Jeremy Long wrote something that I haven't really understood. Maybe > it > means building the NVD

Re: NVD update hangs during release build

add -Ppedantic Tilman On 21.03.2024 17:28, sahy...@fileaffairs.de wrote: which mvn cmd do in need to issue to trigger the check? mvn clean install didn't for me. Am I missing something? BR Maruan Am Donnerstag, dem 21.03.2024 um 17:24 +0100 schrieb Tilman Hausherr: Jeremy Long wrote

Re: [VOTE] Release Apache PDFBox 2.0.31

+1 Maruan > Am 21.03.2024 um 18:53 schrieb Andreas Lehmkühler : > > Hi, > > a candidate for the PDFBox 2.0.31 release is avaiable at: > >https://dist.apache.org/repos/dist/dev/pdfbox/2.0.31/ > > The release candidate is a zip archive of the sources in: > >

Re: [VOTE] Release Apache PDFBox 2.0.31

In the parent pom.xml in the zip file, there's a "release" submodule specified. However, there's no release directory in the src zip that would match: https://svn.apache.org/repos/asf/pdfbox/tags/2.0.31/release/ Is that expected? On Thu, Mar 21, 2024 at 1:53 PM Andreas Lehmkühler wrote: > Hi,

Re: [VOTE] Release Apache PDFBox 2.0.31

IMHO this is not a show stopper > Am 22.03.2024 um 06:54 schrieb Andreas Lehmkühler : > >  > >> Am 21.03.24 um 20:07 schrieb Tim Allison: >> In the parent pom.xml in the zip file, there's a "release" submodule >> specified. However, there's no release directory in the src zip that would >>

Re: [VOTE] Release Apache PDFBox 2.0.31

Am 21.03.24 um 20:07 schrieb Tim Allison: In the parent pom.xml in the zip file, there's a "release" submodule specified. However, there's no release directory in the src zip that would match: https://svn.apache.org/repos/asf/pdfbox/tags/2.0.31/release/ Is that expected? Hmmm, of course