tucek
tucek
> Where do we want to publish the javadoc? Also on doc.liblektra.org? > > Maybe we cheat a little bit and tell students to look at the master API doc...
> Do we need "internal API developer Javadoc"? In Elektra we stopped building it because nobody used it. From my experience the best rule of thumb is: every non-(package-)private interface,...
Closed accidentally via PR.
I will try to activate strict java doc checking in gradle build, which should close this issue.
Yes, java docs are part of building the Java binding artifact (also necessary for maven upload).
> @tucek you can immediately offer something like this in the Java API, the aliases are not useful for the bindings anyway. @markus2330 please have a look at the newly...
> LGTM in principle, but a few tests to validate everything would be nice. However, I'm not entirely sure how to best test this. It probably needs a mix of...
As discussed i will add a test for construct KeySet, getPointer, ksDel, ksDecRef, ksDel should succeed.
This PR is rdy to be merged if build errors are not related to my changes. see also https://github.com/ElektraInitiative/libelektra/pull/4439#issuecomment-1233570354
rebased and to current elektra master and resolved conflicts