https://bz.apache.org/bugzilla/show_bug.cgi?id=47950
--- Comment #8 from Uwe Schindler (ASF) <[email protected]> --- There are several possibilities: You can change the inner fileset of forbiddenapis to exclude some files, yes. In Lucene we use an Annotation. An example is given in the forbiddenapis JAR file, but you dont want to depend on it in the code. So we defined our own @SuppressForbidden annotation in our own source code. The Ant config just gest the class name. http://svn.apache.org/repos/asf/lucene/dev/trunk/lucene/core/src/java/org/apache/lucene/util/SuppressForbidden.java And here it is enabled: <!-- applies to both source and test code --> <target name="-check-forbidden-all" depends="-init-forbidden-apis,compile-core,compile-test"> <forbidden-apis internalRuntimeForbidden="true" suppressAnnotation="**.SuppressForbidden" classpathref="forbidden-apis.allclasses.classpath"> <bundledSignatures name="jdk-unsafe-${javac.target}"/> <bundledSignatures name="jdk-deprecated-${javac.target}"/> <signaturesFileSet dir="${common.dir}/tools/forbiddenApis"> <include name="base.txt"/> <include name="lucene.txt" if="forbidden-isLucene"/> </signaturesFileSet> <fileset dir="${build.dir}/classes/java" excludes="${forbidden-base-excludes}"/> <fileset dir="${build.dir}/classes/test" excludes="${forbidden-tests-excludes}" erroronmissingdir="false"/> </forbidden-apis> </target> -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
