Am 15.08.2017 um 11:18 schrieb Ghislain Vaillant: [...] > My understanding so far: > > 1) DEB_BUILD_OPTIONS=nodoc: doc packages are built but left mostly empty > 2) DEB_BUILD_PROFILES=nodoc: doc packages are not built at all > >> This is a more general tool >> chain issue for Java packages. At the moment I'm not sure how well it is >> supported but it is certainly something we want to support. > > I believe what I have done only answers 2), and I agree solving 1) is > more of a toolchain issue. Same comment for nocheck support. > > I am happy to take it out from both libimglib2-java and > libparsington-java if it is an issue anyway. I find it convenient to use > "nocheck nodoc" when I have got a number of builds of inter-dependent > packages to run locally, but I could also live without. > > Or perhaps I am completely wrong.
I never had to use build profiles because for me it was always something related to bootstrapping Debian as a whole. This is actually the first Java package I have seen where someone makes use of the build profile syntax in debian/control. I still believe what you want is support for DEB_BUILD_OPTIONS=nodoc similar to DEB_BUILD_OPTIONS=nocheck. The nodoc option will be supported by maven-debian-helper soon according to one of Emmanuel's last posts on this list. I assume this will simply suppress the Javadoc step and you will end up with an empty doc package which is basically the same as having no documentation at all. I don't mind uploading the package as is but wanted to point out that build profiles is probably not what you really want. Regards, Markus
signature.asc
Description: OpenPGP digital signature
