I separate my unit test source code from my production source code by placing them in separate top level directories. However, to allow testing package level classes and methods, I use the same package for the production source and unit tests. Unfortunately, this confuses the JavadocPackage check. The check flags the package containing the unit tests as not having a package-info.java even though the production source package does contain one. If I add a package-info.java to the unit test package, an error occurs indicating that there is already a package-info.java.