Hello, developers!
Just attempted to do an
ant
build on fortress clean from the cvs and found
that I had to do a couple of tweakings to do that.
1. ===patch for avalon-excalibur/fortress/build.xml
--- build.orig 2003-06-04 09:27:12.000000000 +0400
+++ build.xml 2003-06-04 10:08:25.000000000 +0400
@@ -106,6 +106,7 @@
<ant antfile="${depchecker.prefix}/depchecker.xml" target="checkEvent"/>
<ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLogger"/>
<ant antfile="${depchecker.prefix}/depchecker.xml" target="checkI18n"/>
+ <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkLifecycle"/>
<ant antfile="${depchecker.prefix}/depchecker.xml"
target="checkRequiredClass">
<property name="proj.jar.name" value="xml-apis.jar"/>
<property name="class" value="org.xml.sax.InputSource"/>
2. ===switch from log4j-1.2.7 to log4j-1.2.8?
It happened that I have 1.2.8 rather then 1.2.7 in avalon/lib.
Which do you have?
Should the version probably be bumped on all our projects?
(I have found it in 3 places).
2.1===
--- avalon-excalibur/logger/default.properties.orig 2003-04-22 04:07:56.000000000
+0400
+++ avalon-excalibur/logger/default.properties 2003-06-04 10:21:07.000000000 +0400
@@ -40,7 +40,7 @@
jdbc.jar=${lib.repo}/jdbc2_0-stdext.jar
mail.jar=${lib.repo}/mail.jar
jms.jar=${lib.repo}/jms.jar
-log4j.jar=${avalon-framework.home}/lib/log4j-1.2.7.jar
+log4j.jar=${avalon-framework.home}/lib/log4j-1.2.8.jar
# For unit testing:
2.2===
--- avalon-excalibur/check-targets.properties.orig 2003-02-11 07:40:26.000000000
+0300
+++ avalon-excalibur/check-targets.properties 2003-06-04 10:20:43.000000000 +0400
@@ -64,7 +64,7 @@
junit.dist.url=http://www.junit.org/
# Log4J
-log4j.version=1.2.7
+log4j.version=1.2.8
log4j.id=log4j
log4j.license=${asl.license}
log4j.license.url=${asl.license.url}
2.3 ===
--- avalon/check-targets.properties.orig 2003-02-11 15:23:24.000000000 +0300
+++ avalon/check-targets.properties 2003-06-04 10:34:31.000000000 +0400
@@ -64,7 +64,7 @@
junit.dist.url=http://www.junit.org/
# Log4J
-log4j.version=1.2.7
+log4j.version=1.2.8
log4j.id=log4j
log4j.license=${asl.license}
log4j.license.url=${asl.license.url}
3. =========================
Not that this matters much (avalon-excalibur/libraries.properties
overrides this anyway), but just not to make anyone feel embarrassed:
--- avalon-excalibur/store/default.properties.orig 2003-02-06 16:38:34.000000000
+0300
+++ avalon-excalibur/store/default.properties 2003-06-04 10:43:54.000000000 +0400
@@ -21,7 +21,7 @@
avalon-framework.jar=${avalon-framework.lib}/avalon-framework.jar
# ----- Jisp 2.0.1 -----
-jisp.jar=lib/Jisp2.0.1.jar
+jisp.jar=lib/jisp-2.0.1.jar
# --------------------------------------------------
(have to confess I was so embarrassed that used to keep both
jisp-2.0.1.jar and Jisp2.0.1.jar in my avalon-excalibur/lib
untill today)
4. ==========================================
How great would be the idea to have some servlet.jar
(say from jakarta-servletapi-*.jar, maybe servlet 2.2 spec
compliant) in avalon-excalibur/lib?
(I mean in the cvs.)
5. ========================
And what about putting log4j.jar to avalon/lib?
(Disclaimer: I just don't know what the general
policy about keeping jars in the cvs is, so I ask
questions 4 and 5. More important in this mail
of course are the other sections).
- WBR, Anton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
