1/ jena-fuseki-ui
When I run maven, the yarn.lock file is being changed.
Most changes are to do with "integrity" beginning deleted.
"@babel/core@^7.11.0":
version "7.16.7"
resolved
"https://registry.yarnpkg.com/@babel/core/-/core-7.16.7.tgz#db990f931f6d40cb9b87a0dc7d2adc749f1dcbcf";
- integrity
sha512-aeLaqcqThRNZYmbMqtulsetOQZ/5gbR/dWruUCJcpas4Qoyy+QeagfDsPdMrqwsPRDNxJvBlRiZxxX7THO7qtA==
dependencies:
"@babel/code-frame" "^7.16.7"
"@babel/generator" "^7.16.7"
Some are reordering in the file.
I'm not sure what's going to happen in a release build - it may check in
the changes because it does other commits, or it might get upset that
changes are happening while running.
Can the update of yarn.lock be turned off?
2/ Java11.
There's a fix for javadoc production so we need customization of the
javadoc production for JDK11 only (the necessary setting has ben removed
in later JDKs.
How is that done? A profile would need to replicate the whole of the
modules settings which is doable but extreme.
Or activate by property "apache-release" which I think then means
multiple profiles are active. (Never done it myself)
We can hack it by producing duff javadoc and fixing it like the current
javadoc is fixed. Nuisance for javadoc artifact.
There is a script the website.
https://github.com/apache/jena-site/tree/javadoc
Andy
