I propose that we generate a 1.1 release that supports the OpenSSL 1.0 and
1.1 API. What are the next steps in that process?
Alex
>Runtime retention is a potential problem, as an extra binary may be needed.
>The jar might no longer be a drop-in replacement.
That is exactly while the annotations are an option only to use.
On Wed, Aug 28, 2019 at 4:17 PM sebb wrote:
> On Wed, 28 Aug 2019 at 14:55, Peter Verhas wrote:
> >
>
On Wed, 28 Aug 2019 at 14:55, Peter Verhas wrote:
>
> Bruno P. Kinoshita>But if you could perhaps show the pros and cons,
>
> There is a slight overhead marking and naming the code snippets and also
> the code segments where the snippets should be inserted. It is slightly
> more complex than just
Bruno P. Kinoshita>But if you could perhaps show the pros and cons,
There is a slight overhead marking and naming the code snippets and also
the code segments where the snippets should be inserted. It is slightly
more complex than just copy-paste but not a big deal. If the unit test
lines are not
I haven't used Geci, so can't really comment on all the things it
might be capable of.
With respect to something equivalent to Python doctests, in the Groovy
project we
have JavadocAssertionTestBuilder and JavadocAssertionTestSuite classes.
Feel free to look to those for inspiration (at least).
F
