yes on all points. I like it. Particularly the point about losing j2ee.
Anybody use jar-core? Seems obscure to me.
WILL
----- Original Message -----
From: "Henning P. Schmiedehausen" <[EMAIL PROTECTED]>
Newsgroups: hometree.jakarta.velocity.dev
To: <[email protected]>
Sent: Monday, September 26, 2005 3:09 AM
Subject: Jar Building
Hi,
currently we have seven different jar building tasks for the ant build:
- jar - builds the regular jar
- jar-J2EE - builds the regular jar + DataSource loader
- jar-core - builds just the Velocity engine, minus texen,
anakia, convert and the servlet
- jar-util - just texen, anakia, convert
- jar-servlet - just the VelocityServlet
- jar-dep - regular jar + some classes from commons-collections,
commons-lang, logkit, oro repacked
- jar-J2EE-dep - regular jar + Datasource Loader + some classes from
commons-collections, commons-lang,
logkit, oro repacked
Which leads to the following jars:
431183 Sep 26 11:47 velocity-1.5-dev.jar
434233 Sep 26 11:44 velocity-J2EE-1.5-dev.jar
297167 Sep 26 11:46 velocity-core-1.5-dev.jar
32150 Sep 26 11:46 velocity-util-1.5-dev.jar
4686 Sep 26 11:47 velocity-servlet-1.5-dev.jar
1166066 Sep 26 11:47 velocity-dep-1.5-dev.jar
1169116 Sep 26 11:47 velocity-J2EE-dep-1.5-dev.jar
The difference between velocity and velocity J2EE is ~ three whooping
KB with no difference for the actual users unless they use the
DataSource loader which is actually pretty exotic (and whoever is
loading templates from JDBC probably knows what they are doing... :-) ).
velocity-servlet contains a single class that is deprecated.
I do like the split between "core" and "util", however I'm afraid we
can't just do that for 1.5 Most users of Velocity, Anakia and Texen
might be upset if we suddently require two jars instead of one. This
is something for Velocity 2.0
Interestingly enough, the sizes of "core", "util" and "servlet" don't
add up to the full jar. This is because the test classes are missing
from all three jars.
I'd like to propose the following things for the 1.5 release of velocity:
- jar-core, jar-util and jar-servlet targets go away. This means that the
current users of "velocity-core" will have a penalty of ~36k in jar size
and
every one else will greatly benefit from the reduction of different
velocity
jars floating around.
- jar and jar-J2EE are rolled into "jar". The build checks whether the
javax.sql.DataSource class is available (which is J2EE, jdbc.jar or JDK
1.4+)
and if not, issues a big warning about the missing class. This is only
important for people that want to customize their velocity version or
rebuild
the jar. And it will make building actually simpler because there will be
less
confusion about which target to choose and which jar to build.
- same goes for jar-dep and jar-J2EE-dep
- none of the actual jars will contain the test classes.
- We will make sure that the official Velocity 1.5 release will be built
with
JDK 1.3.1 and jdbc thus making the resulting jars and distributions
runnable
on all JDK platforms from 1.3 to 1.5.
Opinions?
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
