Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-75990941
There are situations the behaviour is not wrong, in my opinion. Resolution
for non project `<packaging>` related lifecycles, for example. Maven could
detect this automically based on various criteria: not the default lifecycle,
not project packaging related, attribute of a lifecycle, not executed at an
even hour, etc but it does not. No issue. The command line option lets you
choose the needed behaviour yourself without being forced (issue!) by Maven to
anything. I can live with this not getting committed. That's not the point. For
me that standalone site building tool would exactly be `mvn
--legacy-reactor-resolution site`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
