maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MDEPLOY-200) deployAtEnd fails if the last project to build skip deployment
Date Tue, 01 Sep 2015 08:30:46 GMT

    [ https://issues.apache.org/jira/browse/MDEPLOY-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724974#comment-14724974
] 

Victor commented on MDEPLOY-200:
--------------------------------

Well, I don't know, I'm using maven 3.3.3 and this is what maven-deploy-plugin says for the
last project of the reactor:
{noformat}
[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ petals-activiti-rootbuilder
---
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy from plugin
realm ClassRealm[plugin>org.apache.maven.plugins:maven-deploy-plugin:2.8.2, parent: sun.misc.Launcher$AppClassLoader@3ad6a0e0]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy' with
basic configurator -->
[DEBUG]   (f) artifact = org.ow2.petals.samples:petals-activiti-rootbuilder:pom:0-SNAPSHOT
[DEBUG]   (f) attachedArtifacts = []
[DEBUG]   (f) deployAtEnd = true
[DEBUG]   (s) localRepository =       id: local
      url: file:///home/vnoel/.m2/repository/
   layout: default
snapshots: [enabled => true, update => always]
 releases: [enabled => true, update => always]

[DEBUG]   (f) offline = false
[DEBUG]   (f) packaging = pom
[DEBUG]   (f) pomFile = /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/pom.xml
[DEBUG]   (f) project = MavenProject: org.ow2.petals.samples:petals-activiti-rootbuilder:0-SNAPSHOT
@ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/pom.xml
[DEBUG]   (f) reactorProjects = [MavenProject: org.ow2.petals.samples:petals-activiti:5.0.0-SNAPSHOT
@ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/parent/pom.xml, MavenProject:
org.ow2.petals.samples:su-activiti-vacationService-provide:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/su-activiti-vacationService-provide/pom.xml,
MavenProject: org.ow2.petals.samples:su-SOAP-vacationService-consume:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/su-SOAP-vacationService-consume/pom.xml,
MavenProject: org.ow2.petals.samples:su-SOAP-notifyVacationService-provide:5.0.0-SNAPSHOT
@ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/su-SOAP-notifyVacationService-provide/pom.xml,
MavenProject: org.ow2.petals.samples:su-SOAP-archiveService-provide:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/su-SOAP-archiveService-provide/pom.xml,
MavenProject: org.ow2.petals.samples:su-SOAP-activitiIntegrationService-consume:5.0.0-SNAPSHOT
@ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/su-SOAP-activitiIntegrationService-consume/pom.xml,
MavenProject: org.ow2.petals.samples:sa-vacation-sample:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/sa-vacation-sample/pom.xml,
MavenProject: org.ow2.petals.samples:samples-SOAP-services:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/samples-SOAP-services/pom.xml,
MavenProject: org.ow2.petals.samples:sample-vacation-webapp:5.0.0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/sample-vacation-webapp/pom.xml,
MavenProject: org.ow2.petals.samples:petals-activiti-rootbuilder:0-SNAPSHOT @ /home/vnoel/Linagora/Petals/dev/git/petals-se-activiti/samples/pom.xml]
[DEBUG]   (f) retryFailedDeploymentCount = 1
[DEBUG]   (f) skip = true
[DEBUG]   (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] Skipping artifact deployment
{noformat}

Also, maybe it's important, but the reactor pom has not the same parent as the others, so
it doesn't share all the configuration of the plugin, but I explicitly enabled deployAtEnd
for it, and specified the right version.
But for example it has no distributionManagement section… 

> deployAtEnd fails if the last project to build skip deployment
> --------------------------------------------------------------
>
>                 Key: MDEPLOY-200
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-200
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>          Components: deploy:deploy
>    Affects Versions: 2.8.2
>            Reporter: Victor
>
> Hi,
> It seems that with deployAtEnd, if the last project to be built (typically the pom declaring
all the modules of the reactor build) is set as being skipped by maven-deploy-plugin, then
nothing is deployed at the end!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message