In the situation where a java package does not have a target for producing documentation, but does bundle documentation there is currently no way for an ebuild to inherit the functionality within java-pkg-2_src_compile. This is a result of java-pkg-2_src_compile using use_doc which outputs 'javadoc' if ${1} is empty. dev-java/jarbundler-1.4.ebuild within the migrated-java-experimental-overlay demonstrates this error. I also apologies for the incoherent ramble that is the above. I have discussed this issue with Caster.
Created attachment 110046 [details] dev-java/jarbundler-1.4-r2.ebuild which will fail when doc use flag set test ebuild within overlay is now jarbundler-1.4-r2.ebuild
Created attachment 110059 [details, diff] possible solution Allows declaring EANT_DOC_TARGET="" in ebuild to skip the use_doc part. IMHO better than adding another EANT_DISABLE_DOC-like variable. The downside is that it now has own default value "javadoc" and isn't relying on use_doc default... but I don't think we're ever gonna change the default... Didn't see any easy way to test for "variable declared but empty", but maybe somebody else can come up with better solution.
Sometimes we just need to stop and think about over engineering. What is wrong with just: src_compile() { eant }
Considering how many variables are already there for default src_compile(), this small change doesn't add too much IMHO (at least not another variable).
(In reply to comment #4) > Considering how many variables are already there for default src_compile(), > this small change doesn't add too much IMHO (at least not another variable). > sure. I don't object to adding it but am not going to do it myself.
in cvs
