Matthias Bünger created MDEPLOY-327:
---------------------------------------
Summary: Always "deployAtEnd"
Key: MDEPLOY-327
URL: https://issues.apache.org/jira/browse/MDEPLOY-327
Project: Maven Deploy Plugin
Issue Type: New Feature
Components: deploy:deploy
Reporter: Matthias Bünger
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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
