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
like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>3.1.1</version>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-archiver</artifactId>
<version>4.1.0</version>
</dependency>
</dependencies>
</plugin>
[1]
https://github.com/codehaus-plexus/plexus-archiver/blob/master/ReleaseNotes.md#plexus-archiver-400
/Anders
On Tue, May 7, 2019 at 8:07 PM Eric Lilja <[email protected]> wrote:
> 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 relevant plexus components containing the fix (but
> I might be wrong about that).
>
> However, both MJAR-259 [2] and MSOURCES-119 [3] are still open. When can we
> expect new releases of these two plugins (and other plugins/components
> affected by the same issue)? Is something block the release or no one
> simply got around to it yet?
>
> We're trying to stay current and modern in our little eco-system at work,
> but this issue is holding us back on older versions of aforementioned
> plugins.
>
> Thanks for your time!
>
> - Eric L
>
> [1] https://github.com/codehaus-plexus/plexus-io/pull/17
> [2] https://issues.apache.org/jira/browse/MJAR-259
> [3] https://issues.apache.org/jira/browse/MSOURCES-119
>
