Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
[EMAIL PROTECTED] wrote:
remm2003/10/27 00:03:35
Modified:.build.properties.sample
Log:
- Upgrade to pool 1.1 and DBCP 1.1.
Revision ChangesPath
1.71 +5 -5 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- build.properties.sample 23 Oct 2003 15:32:09 - 1.70
+++ build.properties.sample 27 Oct 2003 08:03:35 - 1.71
@@ -161,17 +161,17 @@
# - Commons DBCP, version 1.0 or later -
-commons-dbcp.home=${base.path}/commons-dbcp-1.0
+commons-dbcp.home=${base.path}/commons-dbcp-1.1
commons-dbcp.lib=${commons-dbcp.home}
-commons-dbcp.jar=${commons-dbcp.lib}/commons-dbcp.jar
-commons-dbcp.loc=${base-jakarta.loc}/commons/dbcp/binaries/commons-dbcp-1.0.tar.gz
+commons-dbcp.jar=${commons-dbcp.lib}/commons-dbcp-1.1.jar
+commons-dbcp.loc=http://archive.apache.org/dist/jakarta/commons/dbcp/binaries/commons-dbcp-1.1.tar.gz
${base-jakarta.loc} is http://archive.apache.org/dist/jakarta, why don't you use it?
# - Commons Pool, version 1.0 or later -
commons-pool.home=${base.path}/commons-pool-1.1
commons-pool.lib=${commons-pool.home}
commons-pool.jar=${commons-pool.lib}/commons-pool-1.1.jar
-commons-pool.loc=${base-jakarta.loc}/commons/pool/binaries/commons-pool-1.1.tar.gz
+commons-pool.loc=http://archive.apache.org/dist/jakarta/commons/pool/binaries/commons-pool-1.1.tar.gz
# - JavaService, version 1.2.0 or later -
-
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]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Bill Barker wrote: jfarcand2002/11/11 20:16:59 Modified:.build.properties.sample Log: Update to Xerces 2.2.1. Not working any different than 2.2.0 for me. :-( 2002-11-11 22:46:32 action: null org.xml.sax.SAXParseException: The string -- is not permitted within comments. Then it still has the same problem with Struts 1.0. I'll keep Xerces 2.1.0 for Tomcat 4.1.x. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Wow. I'm confuse. I did some test yesterday and everythings seems to work fine for me. I will continue to ping the Xerces guys -- Jeanfrancois Remy Maucherat wrote: Bill Barker wrote: jfarcand2002/11/11 20:16:59 Modified:.build.properties.sample Log: Update to Xerces 2.2.1. Not working any different than 2.2.0 for me. :-( 2002-11-11 22:46:32 action: null org.xml.sax.SAXParseException: The string -- is not permitted within comments. Then it still has the same problem with Struts 1.0. I'll keep Xerces 2.1.0 for Tomcat 4.1.x. Remy -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
- Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 11, 2002 8:16 PM Subject: cvs commit: jakarta-tomcat-4.0 build.properties.sample jfarcand2002/11/11 20:16:59 Modified:.build.properties.sample Log: Update to Xerces 2.2.1. Not working any different than 2.2.0 for me. :-( 2002-11-11 22:46:32 action: null org.xml.sax.SAXParseException: The string -- is not permitted within comments. -- To unsubscribe, e-mail: mailto:tomcat-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-dev-help;jakarta.apache.org
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:46:33
Modified:.build.properties.sample
Log:
Upgrade to the lastest xerces.
Revision ChangesPath
1.52 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.properties.sample 4 Oct 2002 08:43:48 - 1.51
+++ build.properties.sample 4 Oct 2002 08:46:33 - 1.52
@@ -117,9 +117,9 @@
# - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
-xerces.home=${base.path}/xerces-2_1_0
+xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
-xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
Shouln't we stay with xerces 2.1.0 until we found the problem with 2.2.0 ?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Hi,
Well the downlaod task needs a little more.
I would like to test *.loc:
if starting with http then use a download task.
if not use a cvs + build task.
Any comments?
Cheers
Jean-frederic
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:43:48
Modified:.build.properties.sample
Log:
Update to the laster commons-logging (the older gives problems with log4j).
Revision ChangesPath
1.51 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- build.properties.sample 4 Sep 2002 13:38:50 - 1.50
+++ build.properties.sample 4 Oct 2002 08:43:48 - 1.51
@@ -78,11 +78,11 @@
# - Commons Logging, version 1.0.1 or later -
-commons-logging.home=${base.path}/commons-logging-1.0.1
+commons-logging.home=${base.path}/commons-logging-1.0.2
commons-logging.lib=${commons-logging.home}
commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
commons-logging.jar=${commons-logging.lib}/commons-logging.jar
-commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
+commons-logging.loc=http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.2/commons-logging-1.0.2.tar.gz
# - Java Naming and Directory Interface (JNDI), version 1.2 or later -
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Henri Gomez wrote:
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:46:33
Modified:.build.properties.sample
Log:
Upgrade to the lastest xerces.
Revision ChangesPath
1.52 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.properties.sample4 Oct 2002 08:43:48 -1.51
+++ build.properties.sample4 Oct 2002 08:46:33 -1.52
@@ -117,9 +117,9 @@
# - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
-xerces.home=${base.path}/xerces-2_1_0
+xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
-xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
Shouln't we stay with xerces 2.1.0 until we found the problem with 2.2.0 ?
Even in this case we have to change the sample file:
+++
$ wget http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
--12:00:13-- http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
= `Xerces-J-bin.2.1.0.tar.gz'
Resolving proxy.mch.fsc.net... done.
Connecting to proxy.mch.fsc.net[172.25.80.170]:81... connected.
Proxy request sent, awaiting response... 404 Not Found
12:00:13 ERROR 404: Not Found.
+++
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
jean-frederic clere wrote:
Henri Gomez wrote:
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:46:33
Modified:.build.properties.sample
Log:
Upgrade to the lastest xerces.
Revision ChangesPath
1.52 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.properties.sample4 Oct 2002 08:43:48 -1.51
+++ build.properties.sample4 Oct 2002 08:46:33 -1.52
@@ -117,9 +117,9 @@
# - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
-xerces.home=${base.path}/xerces-2_1_0
+xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
-xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
Shouln't we stay with xerces 2.1.0 until we found the problem with
2.2.0 ?
yep, 2.1.0 moved to :
http://xml.apache.org/dist/xerces-j/old_xerces2/
Did someone contacted Xerces Team about our problem of comment checking ?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Henri Gomez wrote:
jean-frederic clere wrote:
Henri Gomez wrote:
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:46:33
Modified:.build.properties.sample
Log:
Upgrade to the lastest xerces.
Revision ChangesPath
1.52 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.properties.sample4 Oct 2002 08:43:48 -1.51
+++ build.properties.sample4 Oct 2002 08:46:33 -1.52
@@ -117,9 +117,9 @@
# - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
-xerces.home=${base.path}/xerces-2_1_0
+xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
-xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
Shouln't we stay with xerces 2.1.0 until we found the problem with
2.2.0 ?
yep, 2.1.0 moved to :
http://xml.apache.org/dist/xerces-j/old_xerces2/
Did someone contacted Xerces Team about our problem of comment checking ?
No, and I have another problem probably due to 2.2.0:
+++
build-main:
[style] DEPRECATED - xslp processor is deprecated. Use trax or xalan instead.
[style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
[style] at
org.apache.tools.ant.taskdefs.optional.XslpLiaison.init(XslpLiaison.java:80)
[style] at java.lang.Class.newInstance0(Native Method)
[style] at java.lang.Class.newInstance(Class.java:232)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at
org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[style] at org.apache.tools.ant.Main.start(Main.java:196)
[style] at org.apache.tools.ant.Main.main(Main.java:235)
[style] java.lang.NoClassDefFoundError:
org/apache/xalan/xslt/XSLTProcessorFactory
[style] at
org.apache.tools.ant.taskdefs.optional.XalanLiaison.init(XalanLiaison.java:84)
[style] at java.lang.Class.newInstance0(Native Method)
[style] at java.lang.Class.newInstance(Class.java:232)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)[style] at
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Did someone contacted Xerces Team about our problem of comment checking ? No, and I have another problem probably due to 2.2.0: ant didn't find you Xalan 2.4.0 jar ? Is it in ant/lib ? build-main: [style] DEPRECATED - xslp processor is deprecated. Use trax or xalan instead. [style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor [style] at org.apache.tools.ant.taskdefs.optional.XslpLiaison.init(XslpLiaison.java:80) [style] at java.lang.Class.newInstance0(Native Method) [style] at java.lang.Class.newInstance(Class.java:232) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.Project.executeTargets(Project.java:1250) [style] at org.apache.tools.ant.Main.runBuild(Main.java:610) [style] at org.apache.tools.ant.Main.start(Main.java:196) [style] at org.apache.tools.ant.Main.main(Main.java:235) [style] java.lang.NoClassDefFoundError: org/apache/xalan/xslt/XSLTProcessorFactory [style] at org.apache.tools.ant.taskdefs.optional.XalanLiaison.init(XalanLiaison.java:84) [style] at java.lang.Class.newInstance0(Native Method) [style] at java.lang.Class.newInstance(Class.java:232) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554) [style] at org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371) [style] at org.apache.tools.ant.Task.perform(Task.java:319) [style] at org.apache.tools.ant.Target.execute(Target.java:309) [style] at org.apache.tools.ant.Target.performTasks(Target.java:336) [style] at org.apache.tools.ant.Project.executeTarget(Project.java:1306) [style] at org.apache.tools.ant.Project.executeTargets(Project.java:1250) [style] at org.apache.tools.ant.Main.runBuild(Main.java:610) [style] at org.apache.tools.ant.Main.start(Main.java:196) [style] at org.apache.tools.ant.Main.main(Main.java:235) BUILD FAILED file:/home6/clere/jakarta-tomcat-4.1.12-src/webapps/tomcat-docs/build.xml:82: javax.xml.transform.TransformerFactoryConfigurationError: Provider for javax.xml.transform.TransformerFactory cannot be found +++ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Clere, Jean-Frederic wrote:
Henri Gomez wrote:
jean-frederic clere wrote:
Henri Gomez wrote:
[EMAIL PROTECTED] wrote:
jfclere 2002/10/04 01:46:33
Modified:.build.properties.sample
Log:
Upgrade to the lastest xerces.
Revision ChangesPath
1.52 +3 -3 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- build.properties.sample4 Oct 2002 08:43:48 -1.51
+++ build.properties.sample4 Oct 2002 08:46:33 -1.52
@@ -117,9 +117,9 @@
# - Xerces XML Parser, version 2.0.0 or later -
# Note: Optional with JDK 1.4+, or if Xerces 1.x is present
-xerces.home=${base.path}/xerces-2_1_0
+xerces.home=${base.path}/xerces-2_2_0
xerces.lib=${xerces.home}
-xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.1.0.tar.gz
+xerces.loc=http://xml.apache.org/dist/xerces-j/Xerces-J-bin.2.2.0.tar.gz
xercesImpl.jar=${xerces.lib}/xercesImpl.jar
xmlParserAPIs.jar=${xerces.lib}/xmlParserAPIs.jar
Shouln't we stay with xerces 2.1.0 until we found the problem with
2.2.0 ?
yep, 2.1.0 moved to :
http://xml.apache.org/dist/xerces-j/old_xerces2/
Did someone contacted Xerces Team about our problem of comment checking ?
No, and I have another problem probably due to 2.2.0:
+++
build-main:
[style] DEPRECATED - xslp processor is deprecated. Use trax or xalan
instead.
[style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
[style] at
org.apache.tools.ant.taskdefs.optional.XslpLiaison.init(XslpLiaison.java:80)
[style] at java.lang.Class.newInstance0(Native Method)
[style] at java.lang.Class.newInstance(Class.java:232)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:376)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:557)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at
org.apache.tools.ant.Project.executeTargets(Project.java:1250)
[style] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[style] at org.apache.tools.ant.Main.start(Main.java:196)
[style] at org.apache.tools.ant.Main.main(Main.java:235)
[style] java.lang.NoClassDefFoundError:
org/apache/xalan/xslt/XSLTProcessorFactory
[style] at
org.apache.tools.ant.taskdefs.optional.XalanLiaison.init(XalanLiaison.java:84)
[style] at java.lang.Class.newInstance0(Native Method)
[style] at java.lang.Class.newInstance(Class.java:232)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:379)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:554)
[style] at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:195)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
[style] at org.apache.tools.ant.Task.perform(Task.java:319)
[style] at org.apache.tools.ant.Target.execute(Target.java:309)
[style] at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[style] at
org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[style] at
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Ooops that has nothing to do with xerces but the ant installation: xalan was missing in my installation... That's what I thinked (cf my prev message) ;-) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
[EMAIL PROTECTED] wrote: On Tue, 11 Jun 2002, Remy Maucherat wrote: I'll adopt a hard line stance, since I think it is the only way to avoid the situation with dependencies to get out of hand (where we bundle custom builds of every dependent module). We have to use only release components in a release build. If there are too many issues, then it is our fault for relying on broken components, and those dependencies must be removed. I agree that using only stable releases is the ideal solution. Except I don't think it scales. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. I don't agree, I'd like to use the latest stable version. I'd like that too. I just don't think it works. At least for jakarta components we should try to make it work. Well, let's close this issue - the release manager should do the build with whatever he likes, we vote on the end result. If you can get the stars to align on the release date and use only stable versions - great. There are 2 points: - Making reliable releases. - Having reproduceable build. I am going to update the build.xml to help for the second (as commons-logging 1.0.1 is still not released). I am also thinking that if the problem is in commons-logging we should help to make the needed release hapend. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample build.xml
[EMAIL PROTECTED] wrote: jfclere 2002/06/12 09:47:05 Modified:.build.properties.sample build.xml Log: Arrange commons-logging... We have to use cvs until it gets released. Thanks for fixing that :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Remy Maucherat wrote: GOMEZ Henri wrote: Shoud I get the cvs version instead ? I don't think Costin put his packaging changes in the commons repository yet. It would be a good idea if he did. But you broke the ant download as http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. In the meantime, I'm packaging the milestones with: - the commons-logging JARs from j-t-c/lib - MX4J JARs from j-t-c/lib Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
jean-frederic clere wrote: Remy Maucherat wrote: GOMEZ Henri wrote: Shoud I get the cvs version instead ? I don't think Costin put his packaging changes in the commons repository yet. It would be a good idea if he did. But you broke the ant download as http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample
http://jakarta.apache.org/builds/jakarta-commons/release/common s-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? Do you speak about releasing commons-logging 1.0.1 ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample
BTW, all required OSS rpms needed to build tc 4.1.3 are available at jpackage.org : TC 4.1.3 rpm should be out really soon ... - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: GOMEZ Henri Sent: Tuesday, June 11, 2002 6:10 PM To: Tomcat Developers List Subject: RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample http://jakarta.apache.org/builds/jakarta-commons/release/common s-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? Do you speak about releasing commons-logging 1.0.1 ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
On Tue, 11 Jun 2002, Remy Maucherat wrote: But you broke the ant download as http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? The current solution of using 'released' versions will create problems, what happens with commons-logging now is just one example. We should be able to patch/fix the software we depend on. Assuming that the stars will allign when we want to release and 20 or so software packages will have a release at the same time ( or shortly before ) is crazy. Assuming 20 or so software packages are bug free and don't need any fix and will work just fine is also a bit too optimistic. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. Anyway, that's my opinion of what it 'should'. The reality is that it's much easier to use either .jars in CVS or download some packages. I have updated the j-t-c/lib with builds from latest ( I suppose the commit message was too big so filtered out ), and I'll check in a file that'll build most of the stuff from source. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
[EMAIL PROTECTED] wrote: On Tue, 11 Jun 2002, Remy Maucherat wrote: But you broke the ant download as http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ does not exist yet. Getting commons-logging from cvs and building it is not very dificult and is probably better that having a jar file in the repository. This can be done in the meantime. Or we can also try to get commons-logging 1.0.1 out ASAP. Costin, what do you think ? The current solution of using 'released' versions will create problems, what happens with commons-logging now is just one example. We should be able to patch/fix the software we depend on. Assuming that the stars will allign when we want to release and 20 or so software packages will have a release at the same time ( or shortly before ) is crazy. Assuming 20 or so software packages are bug free and don't need any fix and will work just fine is also a bit too optimistic. I'll adopt a hard line stance, since I think it is the only way to avoid the situation with dependencies to get out of hand (where we bundle custom builds of every dependent module). We have to use only release components in a release build. If there are too many issues, then it is our fault for relying on broken components, and those dependencies must be removed. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. I don't agree, I'd like to use the latest stable version. Anyway, that's my opinion of what it 'should'. The reality is that it's much easier to use either .jars in CVS or download some packages. I have updated the j-t-c/lib with builds from latest ( I suppose the commit message was too big so filtered out ), and I'll check in a file that'll build most of the stuff from source. That's not a good practice, and I hope this is the exception rather than the rule. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
On Tue, 11 Jun 2002, Remy Maucherat wrote: I'll adopt a hard line stance, since I think it is the only way to avoid the situation with dependencies to get out of hand (where we bundle custom builds of every dependent module). We have to use only release components in a release build. If there are too many issues, then it is our fault for relying on broken components, and those dependencies must be removed. I agree that using only stable releases is the ideal solution. Except I don't think it scales. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. I don't agree, I'd like to use the latest stable version. I'd like that too. I just don't think it works. Well, let's close this issue - the release manager should do the build with whatever he likes, we vote on the end result. If you can get the stars to align on the release date and use only stable versions - great. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Hum, can't access :
http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 10, 2002 7:27 AM
To: [EMAIL PROTECTED]
Subject: cvs commit: jakarta-tomcat-4.0 build.properties.sample
remm2002/06/09 22:27:18
Modified:.build.properties.sample
Log:
- Bundle some hypothetical 1.0.1 release of commons-logging,
with a separate API JAR.
Revision ChangesPath
1.42 +5 -4 jakarta-tomcat-4.0/build.properties.sample
Index: build.properties.sample
===
RCS file: /home/cvs/jakarta-tomcat-4.0/build.properties.sample,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- build.properties.sample 29 May 2002 10:44:02 - 1.41
+++ build.properties.sample 10 Jun 2002 05:27:18 - 1.42
@@ -6,7 +6,7 @@
# modules that Tomcat depends on. Copy this file to
build.properties
# in the top-level source directory, and customize it as needed.
#
-# $Id: build.properties.sample,v 1.41 2002/05/29 10:44:02
jfclere Exp $
+# $Id: build.properties.sample,v 1.42 2002/06/10 05:27:18 remm Exp $
#
---
--
@@ -77,11 +77,12 @@
commons-digester.loc=http://jakarta.apache.org/builds/jakarta-c
ommons/release/commons-digester/v1.2/commons-digester-1.2.tar.gz
-# - Commons Logging, version 0.1 or later -
-commons-logging.home=${base.path}/commons-logging-1.0
+# - Commons Logging, version 1.0.1 or later -
+commons-logging.home=${base.path}/commons-logging-1.0.1
commons-logging.lib=${commons-logging.home}
+commons-logging-api.jar=${commons-logging.lib}/commons-logging-api.jar
commons-logging.jar=${commons-logging.lib}/commons-logging.jar
-commons-logging.loc=http://jakarta.apache.org/builds/jakarta-c
ommons/release/commons-logging/v1.0/commons-logging-1.0.tar.gz
+commons-logging.loc=http://jakarta.apache.org/builds/jakarta-c
ommons/release/commons-logging/v1.0.1/commons-logging-1.0.1.tar.gz
# - Java Naming and Directory Interface (JNDI), version
1.2 or later -
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
GOMEZ Henri wrote: Hum, can't access : http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ Yes. You have to use the two jars in j-t-c/lib while waiting for the dot release to happen. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample
Shoud I get the cvs version instead ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Monday, June 10, 2002 6:39 PM To: Tomcat Developers List Subject: Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample GOMEZ Henri wrote: Hum, can't access : http://jakarta.apache.org/builds/jakarta-commons/release/common s-logging/v1.0.1/ Yes. You have to use the two jars in j-t-c/lib while waiting for the dot release to happen. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
GOMEZ Henri wrote: Shoud I get the cvs version instead ? I don't think Costin put his packaging changes in the commons repository yet. It would be a good idea if he did. In the meantime, I'm packaging the milestones with: - the commons-logging JARs from j-t-c/lib - MX4J JARs from j-t-c/lib Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-4.0 build.properties.sample
In the meantime, I'm packaging the milestones with: - the commons-logging JARs from j-t-c/lib - MX4J JARs from j-t-c/lib and mx4j 1.1 ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: cvs commit: jakarta-tomcat-4.0 build.properties.sample
on 9/17/01 8:55 PM, Craig R. McClanahan [EMAIL PROTECTED] wrote: Jon, I agree with the general principle of using the same name as it unpacks with, but the jndi1_2_1.zip download doesn't even have an internal directory -- so the name people use is arbitrary. Craig Hmmm...Stuffit created a directory for me. Ok, well, I like this arbitrary name better because it matches up more closely with the rest of the names. :-) -jon
