It looks like OGA Maven plugin has some overlap, but isn't quite the same as the proposed feature...
In my view, deprecation is largely orthogonal to alternatives: - Alternatives exist at all stages of an artifact's lifecycle, not just during deprecation. - Some artifacts are one-of-a-kind and have no (direct) alternatives. - Developers may need to use an alternatives system at any stage of an artifact's lifecycle, not just during deprecation. E.g. a company may discover that an artifact has a disallowed license and ask its developers to find an alternative. - Alternatives themselves come and go, so if an artifact maintainer recommends an alternative in a deprecation notice, this recommendation itself may become outdated. There may also be a better alternative that the maintainer does not know about. Therefore I see no reason to limit or tightly couple an alternatives system to the deprecation phase of an artifact. Developers may often use them together, but not exclusively. To my untrained eye, OGA Maven Plugin seems to address a bit of the alternatives piece and a bit of the deprecation piece, but only where there is a 1-for-1 replacement and the new library is the direct continuation of the old library? Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
