Subject | Build on Windows |
---|---|
Author | Massimo Ferrari |
Post date | 2001-10-27T07:41:45Z |
I attached the batch files I used to build the driver on windows, hoping
these batches will be useful for someone other too.
I slightly modified build.xml to get the javadocs compiled (I couldn't
compile them with the CVS build.xml):
i substituted the packages property with:
<property name="packages" value="org.firebirdsql.*"/>
and removed 'main' from the sourcepath javadoc's directive
<javadoc packagenames="${packages}"
sourcepath="${src.dir}"
destdir="${build.javadocs.dir}"
classpath="${classpath}"
author="true"
version="true"
windowtitle="${Name} API"
doctitle="${Name}"
extdirs="${src.lib.dir}"
bottom="Copyright © 2001 David Jencks and other authors.
All rights reserved."
/>
BTW: I find the type 4 driver a very handy solution, better to maintain and
use than the InterClient driver (although maybe not so performant?).
Although I use EJBs, I would find very useful to have a standalone version
of the driver, with its own pooling mechanismus, for all the other purposes
that simply do not rely on the J2EE/EJB platform. Until now I used JDBC1.0
or 2.0 drivers, and I still do not understand a lot about JCA ands its
environment, but I would be glad to contribute (is it a promise? :) )...
Regars
Massimo
these batches will be useful for someone other too.
I slightly modified build.xml to get the javadocs compiled (I couldn't
compile them with the CVS build.xml):
i substituted the packages property with:
<property name="packages" value="org.firebirdsql.*"/>
and removed 'main' from the sourcepath javadoc's directive
<javadoc packagenames="${packages}"
sourcepath="${src.dir}"
destdir="${build.javadocs.dir}"
classpath="${classpath}"
author="true"
version="true"
windowtitle="${Name} API"
doctitle="${Name}"
extdirs="${src.lib.dir}"
bottom="Copyright © 2001 David Jencks and other authors.
All rights reserved."
/>
BTW: I find the type 4 driver a very handy solution, better to maintain and
use than the InterClient driver (although maybe not so performant?).
Although I use EJBs, I would find very useful to have a standalone version
of the driver, with its own pooling mechanismus, for all the other purposes
that simply do not rely on the J2EE/EJB platform. Until now I used JDBC1.0
or 2.0 drivers, and I still do not understand a lot about JCA ands its
environment, but I would be glad to contribute (is it a promise? :) )...
Regars
Massimo