[
https://jira.codehaus.org/browse/MNG-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352195#comment-352195
]
Tobias Stoeckmann commented on MNG-5684:
----------------------------------------
It was a left-over of an initial Jenkins setup, in which deploy was just added
among the other targets.
Thanks for pointing out that it's expected behaviour, although I have to repeat
that there are changes between 3.2.2 and 3.2.3. In 3.2.3, the deployment of
javadoc and source jars happens twice, as they are probably installed twice if
I understand you correctly.
Yet it's just more of an info, it "breaks" a call that is already broken for
issuing "install" twice.
> deployment happens twice
> ------------------------
>
> Key: MNG-5684
> URL: https://jira.codehaus.org/browse/MNG-5684
> Project: Maven
> Issue Type: Bug
> Components: Deployment, Plugins and Lifecycle
> Affects Versions: 3.2.3
> Environment: Windows 7, Java 8. Happened on Linux distributions (also
> Java 8) as well.
> Reporter: Tobias Stoeckmann
> Attachments: 3.2.2-clean-install-deploy.log,
> 3.2.3-clean-install-deploy.log, my-app.zip
>
>
> Since version 3.2.3, "clean install deploy" will deploy javadoc and source
> jars twice, which fails on our deployment policy. Release versions can be
> deployed only once.
> "clean deploy" fixes the issue, "clean install deploy" triggers it. "clean
> install" alone is okay, too. It installs javadoc and source jars only once.
> Please see attached a minimal example project, it's created through
> archetype. I've added javadoc and install plugin, as well as
> distributionManagement to deploy into "test" directory of user's home.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
