Hi Jim,
On 04/07/18 02:27, Jim Sellers wrote:
Hi Karl.
1) when I comment out the maven-source-plugin and run "mvn clean install" I
don't see any -sources.jar files in my local repo.
Of course not cause the source plugin is only part of the release profile ..
You have to activate the profile
Hi Karl.
1) when I comment out the maven-source-plugin and run "mvn clean install" I
don't see any -sources.jar files in my local repo.
2) I tried it just with the execution part commented out, and I don't see
any -sources jars again. I had expected to from your above comment.
3) I noticed that
Hi Karl.
I've created a minimal project. The git and nexus / repo info would have to
be set in a settings.xml file, and the nexus repo would have to not allow
overwriting releases.
https://github.com/sellersj/hello-world-not-using-corp-parent
This works for maven 3.5.3 but not 3.5.4
If you need
Hi,
The issue looks a bit like:
https://issues.apache.org/jira/browse/MNG-5359
On 03/07/18 21:04, Karl Heinz Marbaise wrote:
Hi Jim,
first thanks for the example project which helps a lot to find the real
problem...
So the issue is related to two things. First you have defined your own a
Hi Jim,
first thanks for the example project which helps a lot to find the real
problem...
So the issue is related to two things. First you have defined your own a
release profile which is ok so far...
The problem is related to the definition of the maven-sources-plugin
like this:
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
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 message
[ERROR] Failed to execute goal
