Not beyond the fact that @Plugin moved packages and already breaks recompiling
plugins from 2.x to 3.x. However, the metadata is loaded from 2.x plugins via
the .dat files, and that still loads the metadata appropriately. There’s at
least one test in JsonTemplateLayout for comparing behavior to
I assume all of this stuff doesn’t break compatibility with 2.x plugins?
Ralph
> On May 20, 2022, at 2:36 PM, Matt Sicker wrote:
>
> By the way, I hope my latest commit renaming categories to namespaces
> and moving some annotation metadata around should help clarify the
> scope of things. In p
By the way, I hope my latest commit renaming categories to namespaces
and moving some annotation metadata around should help clarify the
scope of things. In particular, I made an alias annotation for Core
category/namespace plugins called @Configurable which makes their use
case more obvious. Simil
Sounds good to me. I'll see if I have anything pending over the weekend but
if I do it is not critical.
Gary
On Fri, May 20, 2022, 12:06 Ralph Goers wrote:
> I am working through the last few issues I want to resolve for 2.18.0.
> I’d like to hope I can have them done today but I might not. I w
Thanks all!
WRT Ralph's comments:
The compressed active log can be read as it is being written with no problems
using e.g. zcat/zless. This can read up to the end of the data despite the GZIP
not being closed.
There is a concern about the application dying and not closing the GZIP
compression
I am working through the last few issues I want to resolve for 2.18.0. I’d
like to hope I can have them done today but I might not. I will be traveling
tomorrow through Wed, May 25 to visit friends and family. While it is possible
I might be able to do the release then, it is unlikely. So right
