Re: Split package caused by DisableStrictChecks

Hi,

> It won't be backward compatible, but on the other hand it's just one
annotation,
> it's very new and I suppose there aren't many people using it,
> if any (except my day job, which uses it in a handful of places).

I'm using it, too!
It really helps replacing some older stuff that needs to be extended
without breaking everything else.
But how do you deal with @InjectComponent in base classes?
Maybe a boolean "allowMissing() default false" could be added to
@InjectComponent, or @DisableStrictChecks could also target fields.
I digress, that's another discussion.

Moving just @DisableStrictChecks annotation to
org.apache.tapestry5.*core*.annotations would still split the annotations
because all other core annotations are in org.apache.tapestry5.annotations.
But moving them would affect everyone, so it makes more sense to leave them
there for now.

Maybe wait until the next big update with more breaking changes, like
removing some deprecations or tweaking a few things (method signatures with
type bounds, functional interfaces, streams, etc.), and then move the rest
to have all annotations in a single jar.

Cheers
Ben