jira-importer opened a new issue, #411: URL: https://github.com/apache/maven-deploy-plugin/issues/411
**[Matthias Bünger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER302100)** opened **[MDEPLOY-327](https://issues.apache.org/jira/browse/MDEPLOY-327?redirect=false)** and commented One mistake in my "What's new in Maven 4" story brought up: There is no default installAtEnd/ deployAtEnd for multi subprojects projects. I was convinced that this behavior has changed but we "only" have consistent timestamps for all subprojects and other improvements for the install/deploy property (like deploy in one request). I think it would align well to the Maven 4 "improved UX for multi subproject setups" changes, if the default value for "deployAtEnd" (and accordingly to "installAtEnd" of the install plugin) would be set to "true", so that the behavior matches what many (most? all?) users expect: deploy all or nothing. --- **Issue Links:** - [MDEPLOY-301](https://issues.apache.org/jira/browse/MDEPLOY-301) Switch to the new maven 4 api (_**"is fixed by"**_) **Backported to:** 4.0.0-beta-1 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
