Am 08/23/16 um 22:52 schrieb Christian Schulte: > future-proofness, this would need to be reverted as well. Does not solve > the version range issue, however. This is what makes it impossible to > deploy a pre-resolved dependency tree to the repository. So maybe that > is the major issue we need to find a solution for first to get a > solution solving everything else automatically.
Pragmatism would make us update the deploy plugin to deploy the effective model without import, include, version ranges, build, whatever instead of the on-disk model. This would be breaking backwards compatibility badly, of course but would solve the major issues so far. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
