Re: Regarding MJAR-259 and MSOURCES-119

2019-05-07 Thread Anders Hammar
Checking m-jar-p, what is needed is an upgrade of plexus-archiver to version 4.0.0+ as it includes an upgraded dependency to plexus-io v3.1.1. See [1]. If you include m-jar-p in the pluginManagement section of your corporate parent-POM, you could bump this on the existing maven-jar-plugin v3.1.1

Regarding MJAR-259 and MSOURCES-119

2019-05-07 Thread Eric Lilja
Hi, in my organization we're seeing big increases in build time using newer versions of maven-jar-plugin and maven-sources-plugin, because those plugins are affected by a bug in plexus-io it seems. The issue in plexus-io has been fixed since some time:  [1] and I believe a release has been

Re: Regarding MJAR-259 and MSOURCES-119

2019-05-07 Thread Karl Heinz Marbaise
Hi, would it help to make a release within a time range of one or two weeks.. ? I can take a look ...and see what I can do..? Kind regards Karl Heinz Marbaise On 07.05.19 20:07, Eric Lilja wrote: Hi, in my organization we're seeing big increases in build time using newer versions of

Regarding MJAR-259 and MSOURCES-119

2019-05-07 Thread Eric Lilja
Hi, in my organization we're seeing big increases in build time using newer versions of maven-jar-plugin and maven-sources-plugin, because those plugins are affected by a bug in plexus-io. The issue in plexus-io has been fixed since some time: [1] and I believe a release has been made of

[GitHub] [maven-doxia] asfgit merged pull request #12: DOXIA-576 Upgrade HttpComponents: httpclient to 4.5.8 and httpcore to 4.4.11

2019-05-07 Thread GitBox
asfgit merged pull request #12: DOXIA-576 Upgrade HttpComponents: httpclient to 4.5.8 and httpcore to 4.4.11 URL: https://github.com/apache/maven-doxia/pull/12 This is an automated message from the Apache Git Service. To