Wait a sec, why is this an issue now instead of when we copied the annotations into our packages? We've already published these classes in our packages, presumably all is well?
Gary On Mon, Feb 29, 2016 at 8:18 AM, Oleg Kalnichevski <[email protected]> wrote: > On Mon, 2016-02-29 at 17:36 +0200, Justi Kd wrote: > > > > > Did you ask? If you feel strongly about this, let them know. More > voices is > > > better. > > > > > > Gary > > ... > > > I certainly don't > > mind, just that I think it would be more appropriate that it comes from > the HttpCore lead developers that decided to incorporate this and who > officially represent the project. > > > > I would see no problem removing @GuardedBy annotations (we do not really > use them) but would like to have @Immutable, @ThreadSafe and > @NonThreadSafe or their equivalents. > > I doubt Brian Goetz and Tim Peierls would care much some obscure project > such ours to go to the trouble of relicensing their work, but they might > be willing to concede @Immutable, @ThreadSafe and @NonThreadSafe being > generic enough to not require special licensing. > > You are welcome to approach them on our behalf if you feel strongly > about the issue. > > Oleg > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
