jira-importer opened a new issue, #405: URL: https://github.com/apache/maven-deploy-plugin/issues/405
**[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** opened **[MDEPLOY-305](https://issues.apache.org/jira/browse/MDEPLOY-305?redirect=false)** and commented * Fix when module does not use m-deploy-p * Don't use metadata from main artifact to fetch pom.xml * Deploy all artifacts in one request --- **Issue Links:** - [MDEPLOY-200](https://issues.apache.org/jira/browse/MDEPLOY-200) deployAtEnd fails if the last project to build skip deployment (_**"fixes"**_) - [MDEPLOY-226](https://issues.apache.org/jira/browse/MDEPLOY-226) DeployAtEnd fails when module has extension (_**"fixes"**_) **Remote Links:** - [GitHub Pull Request #34 ](https://github.com/apache/maven-deploy-plugin/pull/34) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
