Hello Neil. > A longer term approach to this might be to download the sources from > Maven, validate the license headers (akin to RAT), and build from > source as part of our build?
Yes, building from (OpenJDK) sources is an approach I'd prefer in the future as well. Actually I've prototyped it in my https://github.com/jaroslavTulach/ nb-javac/ repository. The repository contains just a few wrapper files: https://github.com/JaroslavTulach/nb-javac/tree/ 7e51495f3a275a7891ee93b96d092f600990cada/make/langtools/netbeans/nb-javac/src/ nbjavac and it clones the rest from OpenJDK in an Ant build script: https://github.com/JaroslavTulach/nb-javac/blob/ 7e51495f3a275a7891ee93b96d092f600990cada/make/langtools/netbeans/nb-javac/ build.xml#L91 Do you think these wrappers and the build script should become part of a NetBeans repository? Or is it better to get it working in a separate repository - like the one I have? > > This also raises the question whether the build > > is reproducible and whether it is ok, that there is no direct > > connection between the binary artifact ant the source artifact. > > Yes, and the ambiguity of the LauncherProperties file does raise a > question about the current process there too. Adding a RAT check to verify only "Classpath exception" files are imported from the OpenJDK repository would certainly be a step towards the desirable state and it could prevent human mistakes when releasing the bits. -jt --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
