On Sat, 30 Jun 2018 17:57:50 +0200, Václav Haisman
wrote:
On 28 June 2018 at 20:54, Robert Scholte wrote:
Please see https://issues.apache.org/jira/browse/MPLUGIN-341 for the
full
story:
TLDR; No, Maven can't be (Java) modularized, otherwise all plugins
become
useless.
I am no
On 28 June 2018 at 20:54, Robert Scholte wrote:
> Please see https://issues.apache.org/jira/browse/MPLUGIN-341 for the full
> story:
>
> TLDR; No, Maven can't be (Java) modularized, otherwise all plugins become
> useless.
I am no expert but it seems to me Java 9 services deal with this. Or
Hi expert,
I used maven build and run goal : deploy to see how my spring framework project
run but I got the above error.
There is this stackoverflow person which has similar problem as mine:
See https://maven.apache.org/general.html#javadoc_jar_built_twice
It is very likely that your effective pom defines another explicit call on
the maven-javadoc-plugin, which now can be removed.
thanks,
Robert
ps. we had the same issues when we did a similar change for
maven-source-plugin
Hi Jim,
On 29/06/18 21:15, Jim Sellers wrote:
Hi all.
We have nexus reject over writing releases.
After upgrading maven from 3.5.3 to 3.5.4, the release plan tries to upload
the -sources jars twice, failing the build.
This is for a multi module project.
pom
\- ear
\- war
Example error
