"Will Glass-Husain" <[EMAIL PROTECTED]> writes:
>Just to make sure I understand. If javax.sql.DataSource is in the
>classpath, then DataSourceResourceLoader is included? But if
>javax.sql.DataSource is not, then it is not?
Yes, this is exactly how it works.
>Can we display a user-friendly warning message (but compile anyway) if
>javax.sql.DataSource is not in the classpath. Something like "Excluding
>DataSourceResourceLoader from jar since javax.sql.DataSource is not in
>classpath. To compile this call, please download jdbc2_0-stdext.jar into
>your repository".
Hm. Do we need it? How many people will recompile the velocity jar and
when they do, how many will do it because they've changed something on
the inside and then we can consider them having a clue?
The sourceModifications thingie will hit only in exactly one spot:
someone trying to rebuild on JDK 1.3 SDK without having read the docs
(I do intend to write some manual about how to rebuild the jar using
maven, once we have everything from the build in place). JDK 1.3 will
go into EOL process pretty soon now, so I think that we should not
bother too much with this. The fact that the current ant build can
build four different jars makes IMHO peoples' head hurt much more.
Most people that will want to use velocity will download either the
binary distribution or the jar from ibiblio or the apache mirror
system. There we can make sure that the jar(s) are complete and
working. Remember, we are supposed to know what we are doing... ;-)
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
