[ https://issues.apache.org/jira/browse/MDEPLOY-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089080#comment-15089080 ]
Alexander Kriegisch commented on MDEPLOY-157: --------------------------------------------- Sorry for digging up this issue. I have this in my parent POM's {{pluginManagement}} section: {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <version>2.5.2</version> <configuration> <installAtEnd>true</installAtEnd> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <version>2.8.2</version> <configuration> <deployAtEnd>true</deployAtEnd> </configuration> </plugin> {code} I see artifacts being uploaded to the repository manager per module anyway. Am I doing anything wrong? > Add deployAtEnd option for multimodule projects > ----------------------------------------------- > > Key: MDEPLOY-157 > URL: https://issues.apache.org/jira/browse/MDEPLOY-157 > Project: Maven Deploy Plugin > Issue Type: New Feature > Components: deploy:deploy > Affects Versions: 2.7 > Reporter: Robert Scholte > Assignee: Robert Scholte > Fix For: 2.8 > > > With this option it will be possible to only deploy artifacts if all have > been succesfully installed. > See MRELEASE-664 for further details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)