[
https://jira.codehaus.org/browse/MDEPLOY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355370#comment-355370
]
J. Carrothers commented on MDEPLOY-189:
---------------------------------------
It appears the root cause of my issue is the following build extension defined
by one of the parent POMs of one of the projects which is being deployed.
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
I'm uncertain if this is a problem with Maven, with the deployment plugin, or
with the extension, but the problem persists, even if I use, what I believe is,
the latest version:
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav-jackrabbit</artifactId>
<version>2.7</version>
</extension>
> when skip is enabled for the final module, deployAtEnd artifacts are not
> deployed
> ---------------------------------------------------------------------------------
>
> Key: MDEPLOY-189
> URL: https://jira.codehaus.org/browse/MDEPLOY-189
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.8, 2.8.1, 2.8.2
> Environment: Maven 3.0.5 or Maven 3.1.1
> Reporter: J. Carrothers
>
> Whenever the final module in the reactor to run has skip=true, the final
> deploy phase, including any deployments to be done "at the end" by way of
> deployAtEnd are also skipped.
> A good example of this is skipping the deployment of an aggregator POM which
> is not the parent of the projects it is building and should not, itself, be
> deployed.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
