This is just an idle question:
When I use build.xml to build the "dist" target, the resulting .jar ends up
containing a copy of hibernate.properties, I assume because of the rule
which reads <include name="**/*.properties"/>.
However, the distribution jars on SourceForge don't contain
hibernate.properties. Are they built some other way?
The reason I noticed this is that after switching to calling
buildSessionFactory() with no arguments, when hibernate.properties is in the
jar, it is loaded by default. When I got a message about a missing
com.ibm.db2.jdbc.app.DB2Driver, I knew something was wrong, since I don't
use DB2... Removing the file from the jar allows my own external properties
file to be loaded.
Not a problem, I'm just wondering what secret technique is being used to
build the distribution jars.
Anton
|
