Am 08/30/16 um 00:16 schrieb Paul Benedict: > I see a deployed faulty "consumer pom" to be more more harmful than > generating it locally on demand. At least with the local one I can upgrade > my client to fix a dependency calculation. There will be no such relief in > the case of your proposal.
It's not my proposal but I agree to what is proposed. This whole discussion started because users have requested to revert commits due to compatibility issues. They want to keep such "faulty" behaviour. If they want to fix it, they can deploy a new version using a more recent Maven version. The older Maven version will then also see this new behaviour. If the consumer pom contains the complete resolved dependency tree, the code interpreting that data is not much more than downloading some files from some repository. Yes. Repository information needs to be part of that consumer pom as well. So the resolved dependency tree including repository information from where to get the resolved artifacts. And we also need to find a way to handle version ranges. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
