It's dependency:resolve-plugins that's wrong. What you can do is run a
Maven build with the -X flag and look at the beginning of the
maven-jar-plugin execution. There you should see the resolved tree of the
plugin's dependencies.
/Anders
On Wed, May 8, 2019 at 11:18 AM Eric Lilja wrote:
> Hi,
Hi, and thanks for the answers! We (and many others I'm sure) are happy to
see new releases as soon as possible, of course :-)
Anders: Thanks for the workaround, I implemented it in our corporate pom
for maven-jar-plugin and maven-source-plugin, plus maven-javadoc-plugin.
Then I wiped out
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
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
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
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
