new EntityManagerFactoryImpl constructor behavior proposal

[Justin]

When passing in a list of "libsToScan" to
EntityManagerFactoryImpl(String persistenceUnitName, Map props,
Set<String> libsToScan) it adds those libraries to the classpath to
scan.

The challenge we are facing is we want to use SimpleJPA in the same
project that we are using a new version of Hibernate which uses a new/
custom version of JPA. When using this constructor the code chokes
when trying to process an object in the classpath that has newer
annotations.

One possible resolution to this issue, is to add the ability to limit
the scope of the scanning to a package/class/library as opposed to
appending it.

Building from trunk I was able to add a boolean to the constructor to
specify whether or not to append on or use exclusively the libToScan
libraries.

Is there a way around this with the current version?
Any thoughts on including this kind of change in the next release?
Are there any plans to make this project JPA 2.0 compliant?

Thank you,

~Justin