On Mon, Dec 12, 2016 at 8:22 PM, Christian Schulte <[email protected]> wrote: > Am 12/12/16 um 10:16 schrieb Tibor Digana: >> Is it really necessary to specify version of parent artifact in <parent/>? > > It must be possible to checkout a single module and build that in > isolation. A parent without a version cannot be resolved from a > repository. Supporting that means you need to checkout the whole project > (can be very huge) just to be able to find the parent on disk. > Installing/deploying an artifact without version is impossible - > incomplete coordinates. So there needs to be a version as soon as an > artifact is to be installed or deployed.
But is it really a requirement that the version MUST be there always? I never encountered your specific requirement, but I can imagine it be necessary some times. But I can give you enough examples where your requirement isn't necessary and the version can be omitted. So, if you need need to checkout a submodule stand alone, then one should include the version, but if that is not a use case, one can omit the version and instead rely on the parent's module's version. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
