When Saxon-PE or Saxon-EE JAR files are on the classpath, but the user does not ask for any facilities that require Saxon-PE or Saxon-EE, the intention is the product should work exactly as if Saxon-HE had been loaded. This happens for example when Saxon is loaded as a result of the JAXP classpath search for a TransformerFactory.
In this situation Saxon is producing a warning message to System.err saying that no license could be found. This is confusing if it occurs in an environment where users were not expecting a license to be needed.
A patch is being raised (which will appear in the next PE/EE maintenance release) that causes this message to be output only in the case where the -t flag has been set on the command line (or the equivalent option used in the API).