On 28 November 2016 at 13:12, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote: > On Mon, Nov 28, 2016 at 12:08 PM, sebb <seb...@gmail.com> wrote: > >> No, I'm suggesting that the annotations become an independent Commons >> component. >> If we don't want these used outside Commons (probably a good idea) >> then we can make this clear through Javadoc and package naming etc. >> >> The alternative is to add them to every component as and when they >> want to use them. >> And again, we should probably try to prevent them being used externally. >> >> My position is that only adding them to LANG is not the best solution. > > Okay, but do we really need yet another component? I'd suggest, that a > separate jar file (for example commons-lang-annotations) would be > sufficient, and fulfills your goals.
Either you have to allow a separate release cycle for that jar. Or you have to release a new version of the jar with every LANG release. The content will likely be identical for each one unless the Javadoc is tweaked. Also if it uses the lang package name convention, would the package name be changed with non-BC releases? That would be annoying for downstream users. If it does not use the LANG package naming, why is it bundled with LANG? Maybe that does not matter, but it seems a bit silly to me when one could release a stand-alone jar. The annotations jar has much more in common with the build plugin than a component. We don't insist on bundling the build plugin with another component. > Jochen > > > http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
