Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67621081
I would need a way to disable workspace resolution mainly for the `site`
lifecycle.
cmd> svn checkout .../tags/maven-3.0
cmd> cd maven-3.0
cmd> mvn site
This feeds intermediate build results to the various reports thrown away
right after site generation whereas
cmd> mvn --legacy-reactor-resolution site
makes Maven 3 download the artifacts from `central` or fail, if not finding
them.
Feeding the released artifacts to the various reports is the expected
behaviour in my opinion as the reports are now generated using the same
released artifacts instead of some intermediate build result. The `site`
lifecycle does not produce any artifacts. It consumes pre-built artifacts and
should really fail, if those artifacts cannot be found. Maven 2 did the right
thing here, in my opinion. I would always execute `mvn
--legacy-reactor-resolution site` with this option available.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
