DO NOT REPLY [Bug 29251] - [patch] add @url to import task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29251. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29251 [patch] add @url to import task --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 09:32 --- Alternatively, we could think of having a file cache (in tmpdir) or specified in the import, where we put the fetched file for the sake of the build. One advantage of that is that we can use http's ifmodified requests to accelerate the build process. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27541] - JunitReport task fails under JDK 1.5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27541. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27541 JunitReport task fails under JDK 1.5 --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 11:56 --- I've just retried to work on this with JDK 1.5 beta2, I've patched the build file and junitreport to accept JDK 1.5 as executor - and will commit the changes to CVS HEAD shortly - but it still doesn't work. The stylesheet we use for junitreport uses Xalan redirect extensions and I fail to locate them in JDK1.5, so running junitreport fails with Errors while applying transformations: java.lang.RuntimeException: Unrecognized XSLTC extension 'org.apache.xalan.lib.Redirect:write' It requires is way more than my working XSLT knowledge to come up with a fix here, I'm afraid. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27541] - JunitReport task fails under JDK 1.5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27541. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27541 JunitReport task fails under JDK 1.5 --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 12:06 --- http://java.sun.com/j2se/1.5.0/compatibility.html#4959783 seems to be the relevant piece. In short, JDK 1.5 does not ship with Xalan, as far as Ant is concerned. We'll probably need an XSLTC implementation of our junitreport stylesheets. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant build.xml WHATSNEW
bodewig 2004/06/02 05:09:46
Modified:.build.xml WHATSNEW
Log:
Xalan2Executor doesn't need Xalan-J 2
Revision ChangesPath
1.422 +1 -7 ant/build.xml
Index: build.xml
===
RCS file: /home/cvs/ant/build.xml,v
retrieving revision 1.421
retrieving revision 1.422
diff -u -r1.421 -r1.422
--- build.xml 25 May 2004 11:36:40 - 1.421
+++ build.xml 2 Jun 2004 12:09:45 - 1.422
@@ -172,6 +172,7 @@
!-- depends on external libraries --
selector id=needs.trax
or
+ filename name=${optional.package}/junit/Xalan2Executor*/
filename name=${optional.package}/TraXLiaison*/
filename name=${optional.package}/sitraka/**/
filename name=${optional.package}/metamata/MMetrics*/
@@ -187,10 +188,6 @@
/or
/selector
- selector id=needs.xalan2
-filename name=${optional.package}/junit/Xalan2Executor*/
- /selector
-
selector id=needs.xslp
filename name=${optional.package}/XslpLiaison*/
/selector
@@ -642,7 +639,6 @@
selector refid=needs.trax unless=trax.present/
selector refid=needs.xalan1 unless=xalan.present/
-selector refid=needs.xalan2 unless=xalan2.present/
selector refid=needs.xslp unless=xslp.present/
selector refid=needs.apache-resolver
unless=apache.resolver.present/
selector refid=needs.junit unless=junit.present/
@@ -820,7 +816,6 @@
or
selector refid=needs.trax/
selector refid=needs.xalan1/
-selector refid=needs.xalan2/
selector refid=needs.xslp/
selector refid=needs.apache-resolver/
selector refid=needs.junit/
@@ -868,7 +863,6 @@
optional-jar dep=trax/
optional-jar dep=xalan1/
-optional-jar dep=xalan2/
optional-jar dep=xslp/
optional-jar dep=apache-resolver/
optional-jar dep=junit/
1.610 +4 -0 ant/WHATSNEW
Index: WHATSNEW
===
RCS file: /home/cvs/ant/WHATSNEW,v
retrieving revision 1.609
retrieving revision 1.610
diff -u -r1.609 -r1.610
--- WHATSNEW 31 May 2004 08:21:02 - 1.609
+++ WHATSNEW 2 Jun 2004 12:09:45 - 1.610
@@ -37,6 +37,10 @@
* The import task used the canonical version of a file path. This
has been changed to use the absolute path. Bugzilla 28505.
+* ant-xalan2.jar has been removed since the only class contained in it
+ didn't depend on Xalan-J 2 at all. Its sole dependency has always
+ been TraX and so it has been merged into ant-trax.jar.
+
Fixed bugs:
---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant WHATSNEW build.xml
bodewig 2004/06/02 05:10:59
Modified:.Tag: ANT_16_BRANCH WHATSNEW build.xml
Log:
merge
Revision ChangesPath
No revision
No revision
1.503.2.94 +4 -0 ant/WHATSNEW
Index: WHATSNEW
===
RCS file: /home/cvs/ant/WHATSNEW,v
retrieving revision 1.503.2.93
retrieving revision 1.503.2.94
diff -u -r1.503.2.93 -r1.503.2.94
--- WHATSNEW 31 May 2004 08:24:30 - 1.503.2.93
+++ WHATSNEW 2 Jun 2004 12:10:58 - 1.503.2.94
@@ -7,6 +7,10 @@
* The import task used the canonical version of a file path. This
has been changed to use the absolute path. Bugzilla 28505.
+* ant-xalan2.jar has been removed since the only class contained in it
+ didn't depend on Xalan-J 2 at all. Its sole dependency has always
+ been TraX and so it has been merged into ant-trax.jar.
+
Fixed bugs:
---
1.392.2.29 +1 -7 ant/build.xml
Index: build.xml
===
RCS file: /home/cvs/ant/build.xml,v
retrieving revision 1.392.2.28
retrieving revision 1.392.2.29
diff -u -r1.392.2.28 -r1.392.2.29
--- build.xml 25 May 2004 11:37:02 - 1.392.2.28
+++ build.xml 2 Jun 2004 12:10:59 - 1.392.2.29
@@ -171,6 +171,7 @@
!-- depends on external libraries --
selector id=needs.trax
or
+ filename name=${optional.package}/junit/Xalan2Executor*/
filename name=${optional.package}/TraXLiaison*/
filename name=${optional.package}/sitraka/**/
filename name=${optional.package}/metamata/MMetrics*/
@@ -186,10 +187,6 @@
/or
/selector
- selector id=needs.xalan2
-filename name=${optional.package}/junit/Xalan2Executor*/
- /selector
-
selector id=needs.xslp
filename name=${optional.package}/XslpLiaison*/
/selector
@@ -641,7 +638,6 @@
selector refid=needs.trax unless=trax.present/
selector refid=needs.xalan1 unless=xalan.present/
-selector refid=needs.xalan2 unless=xalan2.present/
selector refid=needs.xslp unless=xslp.present/
selector refid=needs.apache-resolver
unless=apache.resolver.present/
selector refid=needs.junit unless=junit.present/
@@ -819,7 +815,6 @@
or
selector refid=needs.trax/
selector refid=needs.xalan1/
-selector refid=needs.xalan2/
selector refid=needs.xslp/
selector refid=needs.apache-resolver/
selector refid=needs.junit/
@@ -867,7 +862,6 @@
optional-jar dep=trax/
optional-jar dep=xalan1/
-optional-jar dep=xalan2/
optional-jar dep=xslp/
optional-jar dep=apache-resolver/
optional-jar dep=junit/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/xdocs faq.xml
bodewig 2004/06/02 05:31:18
Modified:docs faq.html
docs/manual/OptionalTasks junitreport.html
src/main/org/apache/tools/ant/taskdefs/optional/junit
XalanExecutor.java
xdocsfaq.xml
Log:
Document the junitreport/JDK 1.5 problem, PR: 27541
Revision ChangesPath
1.99 +21 -0 ant/docs/faq.html
Index: faq.html
===
RCS file: /home/cvs/ant/docs/faq.html,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- faq.html 11 May 2004 16:37:02 - 1.98
+++ faq.html 2 Jun 2004 12:31:17 - 1.99
@@ -357,6 +357,12 @@
codeNoClassDefFoundError/code if forked.
/a/li
+lia href=#xalan-jdk1.5
+
+codelt;junitreportgt;/code doesn't work with JDK 1.5 but
+worked fine with JDK 1.4.
+
+ /a/li
/ul
h3 class=sectionAnswers/h3
@@ -1674,6 +1680,21 @@
lt;pathelement
path=quot;${ant.home}/lib/xml-apis.jar:${ant.home}/lib/xercesImpl.jarquot;/gt;
/pre
pto your task's lt;classpathgt;./p
+p class=faq
+ a name=xalan-jdk1.5/a
+
+codelt;junitreportgt;/code doesn't work with JDK 1.5 but
+worked fine with JDK 1.4.
+
+/p
+ pWhile JDK 1.4.x contains a version of Xalan-J 2, JDK 1.5
+(and later?) have a
href=http://java.sun.com/j2se/1.5.0/compatibility.html#4959783;moved
+to XSLTC/a. Since this task uses Xalan's redirect
+extensions for its internal stylesheet, Ant doesn't support
+XSLTC yet. This means that you have to install a
href=http://xml.apache.org/xalan-j/;Xalan-J 2/a in order
+to use this task with JDK 1.5./p
+pIf you want to follow progress on this, a
href=http://issues.apache.org/bugzilla/show_bug.cgi?id=27541;here/a
+is the relevant bug report./p
/div
/div
1.13 +11 -5 ant/docs/manual/OptionalTasks/junitreport.html
Index: junitreport.html
===
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/junitreport.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- junitreport.html 9 Feb 2004 21:50:08 - 1.12
+++ junitreport.html 2 Jun 2004 12:31:18 - 1.13
@@ -14,11 +14,17 @@
Library Dependencies/a for more information./p
h3Requirements/h3
-pThe task needs a href=http://xml.apache.org/xalan-j/;Xalan 2.x/a;
-although
-a href=http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip;Xalan
1.2.2/a
-does work, but as Xalan1 is not supported, we do not recommend this.
-/p
+pThe task needs a href=http://xml.apache.org/xalan-j/;Xalan
+2.x/a; although a
+href=http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip;Xalan
+1.2.2/a does work, but as Xalan1 is not supported, we do not
+recommend this. While JDK 1.4.x contains a version of Xalan-J 2, JDK
+1.5 and later have a
+href=http://java.sun.com/j2se/1.5.0/compatibility.html#4959783;moved
+to XSLTC/a. Since this task uses Xalan's redirect extensions for
+its internal stylesheet, Ant doesn't support XSLTC yet. This means
+that you have to install Xalan-J 2 in order to use this task with JDK
+1.5./p
p
If you do you use Xalan 1.2.2 you will need a compatible (older) version of
Xerces.
as well as BSF(bsf.jar). Again, using Xalan 2 is simpler and supported.
1.15 +12 -2
ant/src/main/org/apache/tools/ant/taskdefs/optional/junit/XalanExecutor.java
Index: XalanExecutor.java
===
RCS file:
/home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/junit/XalanExecutor.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- XalanExecutor.java9 Feb 2004 21:05:32 - 1.14
+++ XalanExecutor.java2 Jun 2004 12:31:18 - 1.15
@@ -27,6 +27,7 @@
import java.lang.reflect.Field;
import org.apache.tools.ant.BuildException;
import org.apache.tools.ant.Project;
+import org.apache.tools.ant.util.JavaEnvUtils;
/**
* Command class that encapsulate specific behavior for each
@@ -86,8 +87,17 @@
xalan1missing.printStackTrace(new PrintWriter(swr));
caller.task.log(Didn't find Xalan1., Project.MSG_DEBUG);
caller.task.log(swr.toString(), Project.MSG_DEBUG);
-throw new BuildException(Could not find xalan2 nor xalan1
-+ in the classpath. Check
http://xml.apache.org/xalan-j;);
+String msg = Could not find xalan2 nor xalan1
+
cvs commit: ant/xdocs faq.xml
bodewig 2004/06/02 05:33:21
Modified:docs Tag: ANT_16_BRANCH faq.html
docs/manual/OptionalTasks Tag: ANT_16_BRANCH
junitreport.html
src/main/org/apache/tools/ant/taskdefs/optional/junit Tag:
ANT_16_BRANCH XalanExecutor.java
xdocsTag: ANT_16_BRANCH faq.xml
Log:
merge
Revision ChangesPath
No revision
No revision
1.77.2.13 +21 -0 ant/docs/faq.html
Index: faq.html
===
RCS file: /home/cvs/ant/docs/faq.html,v
retrieving revision 1.77.2.12
retrieving revision 1.77.2.13
diff -u -r1.77.2.12 -r1.77.2.13
--- faq.html 20 Apr 2004 07:29:35 - 1.77.2.12
+++ faq.html 2 Jun 2004 12:33:21 - 1.77.2.13
@@ -351,6 +351,12 @@
codeNoClassDefFoundError/code if forked.
/a/li
+lia href=#xalan-jdk1.5
+
+codelt;junitreportgt;/code doesn't work with JDK 1.5 but
+worked fine with JDK 1.4.
+
+ /a/li
/ul
h3 class=sectionAnswers/h3
@@ -1650,6 +1656,21 @@
lt;pathelement
path=quot;${ant.home}/lib/xml-apis.jar:${ant.home}/lib/xercesImpl.jarquot;/gt;
/pre
pto your task's lt;classpathgt;./p
+p class=faq
+ a name=xalan-jdk1.5/a
+
+codelt;junitreportgt;/code doesn't work with JDK 1.5 but
+worked fine with JDK 1.4.
+
+/p
+ pWhile JDK 1.4.x contains a version of Xalan-J 2, JDK 1.5
+(and later?) have a
href=http://java.sun.com/j2se/1.5.0/compatibility.html#4959783;moved
+to XSLTC/a. Since this task uses Xalan's redirect
+extensions for its internal stylesheet, Ant doesn't support
+XSLTC yet. This means that you have to install a
href=http://xml.apache.org/xalan-j/;Xalan-J 2/a in order
+to use this task with JDK 1.5./p
+pIf you want to follow progress on this, a
href=http://issues.apache.org/bugzilla/show_bug.cgi?id=27541;here/a
+is the relevant bug report./p
/div
/div
No revision
No revision
1.11.2.3 +11 -5 ant/docs/manual/OptionalTasks/junitreport.html
Index: junitreport.html
===
RCS file: /home/cvs/ant/docs/manual/OptionalTasks/junitreport.html,v
retrieving revision 1.11.2.2
retrieving revision 1.11.2.3
diff -u -r1.11.2.2 -r1.11.2.3
--- junitreport.html 9 Feb 2004 22:12:11 - 1.11.2.2
+++ junitreport.html 2 Jun 2004 12:33:21 - 1.11.2.3
@@ -15,11 +15,17 @@
Library Dependencies/a for more information./p
h3Requirements/h3
-pThe task needs a href=http://xml.apache.org/xalan-j/;Xalan 2.x/a;
-although
-a href=http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip;Xalan
1.2.2/a
-does work, but as Xalan1 is not supported, we do not recommend this.
-/p
+pThe task needs a href=http://xml.apache.org/xalan-j/;Xalan
+2.x/a; although a
+href=http://xml.apache.org/dist/xalan-j/old/xalan-j_1_2_2.zip;Xalan
+1.2.2/a does work, but as Xalan1 is not supported, we do not
+recommend this. While JDK 1.4.x contains a version of Xalan-J 2, JDK
+1.5 and later have a
+href=http://java.sun.com/j2se/1.5.0/compatibility.html#4959783;moved
+to XSLTC/a. Since this task uses Xalan's redirect extensions for
+its internal stylesheet, Ant doesn't support XSLTC yet. This means
+that you have to install Xalan-J 2 in order to use this task with JDK
+1.5./p
p
If you do you use Xalan 1.2.2 you will need a compatible (older) version of
Xerces.
as well as BSF(bsf.jar). Again, using Xalan 2 is simpler and supported.
No revision
No revision
1.11.2.4 +12 -2
ant/src/main/org/apache/tools/ant/taskdefs/optional/junit/XalanExecutor.java
Index: XalanExecutor.java
===
RCS file:
/home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/junit/XalanExecutor.java,v
retrieving revision 1.11.2.3
retrieving revision 1.11.2.4
diff -u -r1.11.2.3 -r1.11.2.4
--- XalanExecutor.java9 Feb 2004 22:12:34 - 1.11.2.3
+++ XalanExecutor.java2 Jun 2004 12:33:21 - 1.11.2.4
@@ -27,6 +27,7 @@
import java.lang.reflect.Field;
import org.apache.tools.ant.BuildException;
import org.apache.tools.ant.Project;
+import org.apache.tools.ant.util.JavaEnvUtils;
/**
* Command class that encapsulate specific behavior for each
@@ -86,8 +87,17 @@
xalan1missing.printStackTrace(new PrintWriter(swr));
caller.task.log(Didn't find Xalan1.,
DO NOT REPLY [Bug 29341] New: - a pseudo attribute name is expected.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29341. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29341 a pseudo attribute name is expected. Summary: a pseudo attribute name is expected. Product: Ant Version: 1.6.0 Platform: All OS/Version: Windows XP Status: NEW Severity: Major Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I m getting this error when building , a pseudo attribute name is expected. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29341] - a pseudo attribute name is expected.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29341. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29341 a pseudo attribute name is expected. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 13:05 --- Please send this sort of question to the ant user group. It is most likey an error with the xml ness of your build file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JDK 1.5 issues
Hi, if you've followed the bugzilla mails or commits of today, you have already seen that junitreport doesn't work nicely with JDK 1.5.[1] The correct route seems to be to replace the stylesheets with something that does not require Xalan's redirect extensions, but this is way beyond my XSLT knowledge. Another issue I faced but that's probably irrelevant to anybody else, bootstrap(.sh|.bat) don't set -target 1.2 in their javac invocation, so the classes compiled by the bootstrap scripts won't run with older VMs. Unfortunately there is more, one of the tests fails with JDK 1.5: [junit] Testcase: testClosure(org.apache.tools.ant.taskdefs.optional.depend.DependTest):FAILED [junit] Depend did not leave correct number of files expected:2 but was:1 [junit] junit.framework.AssertionFailedError: Depend did not leave correct number of files expected:2 but was:1 [junit] at junit.framework.Assert.fail(Assert.java:47) [junit] at junit.framework.Assert.failNotEquals(Assert.java:282) [junit] at junit.framework.Assert.assertEquals(Assert.java:64) [junit] at junit.framework.Assert.assertEquals(Assert.java:201) [junit] at org.apache.tools.ant.taskdefs.optional.depend.DependTest.testClosure(DependTest.java:76) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:582) [junit] at junit.framework.TestCase.runTest(TestCase.java:154) [junit] at junit.framework.TestCase.runBare(TestCase.java:127) [junit] at junit.framework.TestResult$1.protect(TestResult.java:106) [junit] at junit.framework.TestResult.runProtected(TestResult.java:124) [junit] at junit.framework.TestResult.run(TestResult.java:109) [junit] at junit.framework.TestCase.run(TestCase.java:118) [junit] at junit.framework.TestSuite.runTest(TestSuite.java:208) [junit] at junit.framework.TestSuite.run(TestSuite.java:203) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:289) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnitTask.java:1074) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:689) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1426) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:646) [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) [junit] at org.apache.tools.ant.Task.perform(Task.java:363) [junit] at org.apache.tools.ant.Target.execute(Target.java:321) [junit] at org.apache.tools.ant.Target.performTasks(Target.java:348) [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1212) [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1060) [junit] at org.apache.tools.ant.Main.runBuild(Main.java:666) [junit] at org.apache.tools.ant.Main.startAnt(Main.java:187) [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196) [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55) Stefan Footnotes: [1] http://ant.apache.org/faq.html#xalan-jdk1.5 -- http://stefanbodewig.blogger.de/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27446] - Make sql task to suppress N rows affected messages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27446. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27446 Make sql task to suppress N rows affected messages [EMAIL PROTECTED] changed: What|Removed |Added Keywords||PatchAvailable OS/Version|Windows NT/2K |All Version|unspecified |1.6.1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New target's attribute
I added a new target's attribute(named type) so you cant specify the visibility. In this case the target is private and you can´t run it directly but you can call it from another target: target name=telnetVIP type=private ... /target C:\JDevWorkSpaces\ComunicacionBeta4\antant telnetVIP Buildfile: build.xml BUILD FAILED Private target(telnetVIP). Total time: 0 seconds I'm adding new types like public, protected, ... Do you find this useful? Zurdo __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
New target's attribute
I added a new target's attribute(named type) so you cant specify the visibility. In this case the target is private and you can´t run it directly but you can call it from another target: target name=telnetVIP type=private ... /target C:\JDevWorkSpaces\ComunicacionBeta4\antant telnetVIP Buildfile: build.xml BUILD FAILED Private target(telnetVIP). Total time: 0 seconds I'm adding new types like public, protected, ... Do you find this useful? Zurdo __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29344] New: - support for subversion (SVN)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29344. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29344 support for subversion (SVN) Summary: support for subversion (SVN) Product: Ant Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Add built-in support for subversion (SVN) SCM. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 27541] - JunitReport task fails under JDK 1.5
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27541. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27541 JunitReport task fails under JDK 1.5 --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 14:32 --- Well, I had a quick look at the XSL 2.0 spec, and they do have a xsl:result- document element which allows outputting to several documents, so no need to rely on extensions theoretically. (Where I'm confused is how XSL 2.0 relates to XSL 1.1 which also has output to mutliple documents. No mention I could see in the spec!). Does XSLTC support xsl:result-document already? So theoretically (again), we could apply a small transformation to the stylesheet itself to make it XSL 2.0 compatible, although rewritting the stylesheet for XSL 2.0 is another options. I worry about maintenance if we duplicate it though. JDK 1.5 is such a big leap (of faith?)... One wonders if it hasn't too many new things. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Ant Wiki] Updated: AntOddities
Date: 2004-06-02T11:26:57
Editor: 32.102.170.75
Wiki: Ant Wiki
Page: AntOddities
URL: http://wiki.apache.org/ant/AntOddities
Useful macrodef which arose on discussion on user list
Change Log:
--
@@ -400,3 +400,58 @@
BUILD SUCCESSFUL
Total time: 3 seconds
}}}
+
+
+
+
+== Compounding a property name from the instantiations of multiple previously
instanced properties ==
+
+=== The Problem ===
+
+Although plain Ant sytax does not allow one to do so, a simple macrodef can
derive property names by pasting together the instantiations of multiple
previously instanced properties.
+
+Given a set of resource-like properties such as:
+{{{
+ driver.bsd=SomeBSDDriver
+ driver.os2=A.Real.Old.Driver
+ driver.windows=GPFGalore
+
+ booter.bsd=boot
+ booter.os2=boot.sys
+ booter.windows=ntldr
+}}}
+
+You might wish to pass to some target or task properties/parameters such as
${component} and ${targetOS}
+in the form
+
+ {{{ do-something-with object=${${component}.${targetOS}}/ }}}
+
+so that if, for example, ${component} were valued as driver and ${targetOS}
were valued as os2,
+the value of ${${component}.${targetOS}} would be the expansion of
${driver.os2}, i.e., A.Real.Old.Driver.
+However, Ant expansions of property instantiations are not recursive. So in
this instance the expansion of ${${component}.${targetOS}} is not
A.Real.Old.Driver but instead undefined and possibly varying by Ant version.
(Ant 1.6.1 would yield a literal value of ${${component}.${targetOS}}
+while Ant 1.7 alpha currently yields ${${component}.os2})
+
+=== Solution Macrodef ===
+
+Define a macro allowing us to express the problem case as:
+
+{{{
+ macro.compose-property name=object stem=${component}
selector=${targetOS}/
+ do-something-with object=${object}/
+}}}
+
+
+Here is the macro (along lines suggested by Peter Reilly with reference to
http://ant.apache.org/faq.html#propertyvalue-as-name-for-property):
+
+{{{
+!-- Allows you define a new property with a value of ${${a}.${b}} which can't
be done by the Property task alone. --
+macrodef name=macro.compose-property
+attribute name=name/
+attribute name=stem/
+attribute name=selector/
+sequential
+property name=@{name} value=[EMAIL PROTECTED]@{selector}}/
+/sequential
+/macrodef
+
+}}}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Possible Ant 1.7 alpha bug: property expansion.
I was just adding to the Ant Wiki AntOddities page the following macrodef :
!-- Allows you define a new property with a value of ${${a}.${b}} which
can't be done by the Property task alone. --
macrodef name=macro.compose-property
attribute name=name/
attribute name=stem/
attribute name=selector/
sequential
property name=@{name} value=[EMAIL
PROTECTED]@{selector}}/
/sequential
/macrodef
I wrote a quick counter-example which shows how expansions of properties in Ant
is not recursive:
?xml version=1.0 encoding=UTF-8?
project basedir=. default=all name=changeme
target name=all
property name=a value=arf/
property name=b value=bark/
property name=arf.bark value=woof woof woof/
echo message=${${a}.${b}}/
/target
/project
but when I ran it, in Ant version 1.7 alpha built from CVS last night, instead
of getting the unexpanded value of
the overall expression which I expected:
[echo] ${${a}.${b}}
I received the unexpected:
[echo] ${${a}.bark}
This does not seem to me to be correct by the rules of Ant. Either the internal
expansion should be complete or not
at all ... the right term should not expand and leave the left unexpanded. It
seems to me the expected answer was
the one returned by Ant version 1.6.1 but I don't have that built now to see if
the current behavior is a regression.
--
Jack J. Woehr # We have gone from the horse and buggy
Senior Consultant # to the moon rocket in one lifetime, but
Purematrix, Inc. # there has not been a corresponding moral
www.purematrix.com # growth in mankind. - Dwight D. Eisenhower
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29347] New: - Nested property expansion shouldn't occur but does
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29347.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29347
Nested property expansion shouldn't occur but does
Summary: Nested property expansion shouldn't occur but does
Product: Ant
Version: 1.7Alpha (nightly)
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: Core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I was just adding to the Ant Wiki AntOddities page the following macrodef :
!-- Allows you define a new property with a value of ${${a}.${b}} which
can't be done by the Property task alone. --
macrodef name=macro.compose-property
attribute name=name/
attribute name=stem/
attribute name=selector/
sequential
property name=@{name} value=[EMAIL
PROTECTED]@{selector}}/
/sequential
/macrodef
I wrote a quick counter-example which shows how expansions of properties in Ant
is not recursive:
?xml version=1.0 encoding=UTF-8?
project basedir=. default=all name=changeme
target name=all
property name=a value=arf/
property name=b value=bark/
property name=arf.bark value=woof woof woof/
echo message=${${a}.${b}}/
/target
/project
but when I ran it, in Ant version 1.7 alpha built from CVS last night, instead
of getting the unexpanded value of
the overall expression which I expected:
[echo] ${${a}.${b}}
I received the unexpected:
[echo] ${${a}.bark}
This does not seem to me to be correct by the rules of Ant. Either the internal
expansion should be complete or not at all ... the right term should not expand
and leave the left unexpanded. It seems to me the expected answer was the one
returned by Ant version 1.6.1 but I don't have that built now to see if the
current behavior is a regression.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DispatchTask
Hi,
I'd like to introduce the concept of a DispatchTask to Ant. This class may
be subclassed by tasks that perform multiple operations depending upon a
parameter. Currently, the task-writer would be using if...else if...else
constructs. Extending from this class would make it more elegant. Use
cases include tasks that take in same set of parameters but perform
different operations based on needs.
Example usage would be:
somecompoundtask param1=... param2=... mode=list/
In the above example, the custom task writer extends from DispatchTask
instead of Task and implements a method with the signature:
public void list() throws BuildException
instead of the traditional
public void execute() throws BuildException
..and the list() method would be invoked.
A scratch-pad implementation follows.
==
package org.apache.tools.ant;
public abstract class DispatchTask extends Task {
private String mode;
public final void setMode(final String mode) {
this.mode = mode;
}
public void execute() throws BuildException {
if (mode != null) {
Method m = this.getClass().getMethod(mode, null);
m.invoke(this, null);
}
}
}
==
Comments?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Should have used bugzilla
Apologies for reporting the bug to the list. Lost in thought, have now used issues@ -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DispatchTask
From: Magesh Umasankar [mailto:[EMAIL PROTECTED] Hi, I'd like to introduce the concept of a DispatchTask to Ant. This class may be subclassed by tasks that perform multiple operations depending upon a parameter. Currently, the task-writer would be using if...else if...else constructs. Extending from this class would make it more elegant. Use cases include tasks that take in same set of parameters but perform different operations based on needs. Example usage would be: somecompoundtask param1=... param2=... mode=list/ In the above example, the custom task writer extends from DispatchTask instead of Task and implements a method with the signature: public void list() throws BuildException Hi Magesh. It's been a long time ;-) What's the advantage of this other writing different tasks, possibly with the usual Java code re-use? Especially if different modes require different params. I've written at least one task with an action attribute and then do the dispatch based on it, but I don't think this should be made into a framework. What's your more specific use case? --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
I wrote a quick counter-example which shows how expansions of properties
in Ant is not recursive:
?xml version=1.0 encoding=UTF-8?
project basedir=. default=all name=changeme
target name=all
property name=a value=arf/
property name=b value=bark/
property name=arf.bark value=woof woof woof/
echo message=${${a}.${b}}/
/target
/project
but when I ran it, in Ant version 1.7 alpha built from CVS last night,
instead of getting the unexpanded value of
the overall expression which I expected:
[echo] ${${a}.${b}}
I received the unexpected:
[echo] ${${a}.bark}
This does not seem to me to be correct by the rules of Ant. Either the
internal expansion should be complete or not
at all ... the right term should not expand and leave the left unexpanded.
It seems to me the expected answer was
the one returned by Ant version 1.6.1 but I don't have that built now to
see if the current behavior is a regression.
I believe that ${${a}.${b}} is parsed as:
getProperty(${a) + . + getProperty(b) + }, thus the result. --DD
C:\oss\org_apache\antxC:\pro\ant1.6.1\bin\ant -f woof.xml
Buildfile: woof.xml
[echo] ${${a}.bark}
BUILD SUCCESSFUL
Total time: 0 seconds
C:\oss\org_apache\antxC:\pro\ant1.6\bin\ant -f woof.xml
Buildfile: woof.xml
[echo] ${${a}.bark}
BUILD SUCCESSFUL
Total time: 0 seconds
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: DispatchTask
Subject:RE: DispatchTask
From: Dominique Devienne DDevienne () lgc ! com
Date: 2004-06-02 18:50:53
Hi Magesh. It's been a long time ;-)
:-)
What's the advantage of this other writing different tasks, possibly with
the usual Java code re-use? Especially if different modes require
different
params. I've written at least one task with an action attribute and then
do
the dispatch based on it, but I don't think this should be made into a
framework. What's your more specific use case? --DD
The advantage is that related operations are closely coupled. For example,
untar may operate in list mode, in actual expand mode, etc. and these
operations are bundled together as part of a single class instead of
subclassing from a parent abstract UnTar class for each operation.
Another advantage is being able to invoke an operation based on a property.
eg.
mytask mode=${mode}/
If each mode was its own task, writing the equivalent of the above would be
a little more complex, I think.
This, of course, is not the solution where parameters are going to be
different for multiple operations.
btw, action is a more appropriate name than mode. Maybe command too
is? I don't know.
You are saying that you have used it at least once. I have used it a few
times - usually for custom tasks where I either insert, update or delete a
set of rows in a DB based on some conditions outisde the task itself. IMHO
there is value in adding it to the core. But then that is because I'm
pitching for it ;-)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote:
I believe that ${${a}.${b}} is parsed as:
getProperty(${a) + . + getProperty(b) + }, thus the result. --DD
Well, it sure looks like it is :-)
But is that result reasonable? It looks more to me like an artifact of a coding
strategy
being elevated to a principle.
--
Jack J. Woehr # We have gone from the horse and buggy
Senior Consultant # to the moon rocket in one lifetime, but
Purematrix, Inc. # there has not been a corresponding moral
www.purematrix.com # growth in mankind. - Dwight D. Eisenhower
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
Dominique Devienne wrote:
I believe that ${${a}.${b}} is parsed as:
getProperty(${a) + . + getProperty(b) + }, thus the result. --DD
Well, it sure looks like it is :-)
But is that result reasonable? It looks more to me like an artifact of a
coding strategy being elevated to a principle.
First, don't shoot the messenger ;-)
Second, what's one to do? Ant by contract does not support nested
properties, so what's Ant to do when it sees on opening ${? It looks for the
closing curly brace, which is found after ${a, which is thus interpreted as
the property name to reference?
I duplicated the Ant logic using JDK 1.4 regex, and have the same logic
using the \\$\\{([^\\}]+)\\} regex (in Java code, thus the escapes). I
even have a test case that shows what you just discovered:
protected void setUp() {
_ve = new VariableEvaluator();
_ve.putVariable(foo, bar);
_ve.putVariable(ding, dong);
_ve.putVariable(var${weird, indeed);
}
public void test_evalString() {
assertEval(_ve, ${var${varname}}, ${var${varname}}, true);
assertEval(_ve, ${var${weird}}, indeed}, false);
}
--DD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote:
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
Dominique Devienne wrote:
I believe that ${${a}.${b}} is parsed as:
getProperty(${a) + . + getProperty(b) + }, thus the result. --DD
Well, it sure looks like it is :-)
But is that result reasonable? It looks more to me like an artifact of a
coding strategy being elevated to a principle.
First, don't shoot the messenger ;-)
Second, what's one to do? Ant by contract does not support nested
properties, so what's Ant to do when it sees on opening ${?
Glad you ask.
Ant should behave analagously to m4: recursively expand until it either
hits
ground or an uninstantiated ${decorated} name.
--
Jack J. Woehr # We have gone from the horse and buggy
Senior Consultant # to the moon rocket in one lifetime, but
Purematrix, Inc. # there has not been a corresponding moral
www.purematrix.com # growth in mankind. - Dwight D. Eisenhower
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
Second, what's one to do? Ant by contract does not support nested
properties, so what's Ant to do when it sees on opening ${?
Glad you ask.
Ant should behave analagously to m4: recursively expand until it
either hits ground or an uninstantiated ${decorated} name.
So we should break the contract (which most likely was just what the
implementation did at the time rather than a conscious decision, but I
wasn't there that many years ago), and break BC?
Ant allows to define property names with characters it uses to dereference
properties (a mistake I think), so how do you distinguish between the two?
I take it m4 doesn't allow to define a property/variable with $ and { and }
in its name, no? --DD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
Ant should behave analagously to m4: recursively expand until it
either hits ground or an uninstantiated ${decorated} name.
Oh, and the algorithm should be something like:
1. While argument X contains any ${} expressions {
2. Y : = Expansion of leftmost innermost ${ } expressions in X
3. Call Step 1 with (Y) as the argument
4. Replace in X the leftmost innermost ${} expression with the
result of the call. }
5. Return X
Do I have that right?
I wouldn't know, my algorithmic's pretty bad I now recognize.
But you side stepped the BC issue. You can always implement (and test) the
algorithm above, and see if you can get the committers to put it in. --DD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote:
From: Jack J. Woehr [mailto:[EMAIL PROTECTED]
Ant should behave analagously to m4: recursively expand until it
either hits ground or an uninstantiated ${decorated} name.
Oh, and the algorithm should be something like:
1. While argument X contains any ${} expressions {
2. Y : = Expansion of leftmost innermost ${ } expressions in X
3. Call Step 1 with (Y) as the argument
4. Replace in X the leftmost innermost ${} expression with the
result of the call. }
5. Return X
Do I have that right?
I wouldn't know, my algorithmic's pretty bad I now recognize.
But you side stepped the BC issue.
?? Not sure I get you. BC issue?
You can always implement (and test) the
algorithm above, and see if you can get the committers to put it in. --DD
Sure, but save me 15 minutes :-)... What file(s) of the source is the expansion
of a property expression found in?
--
Jack J. Woehr # We have gone from the horse and buggy
Senior Consultant # to the moon rocket in one lifetime, but
Purematrix, Inc. # there has not been a corresponding moral
www.purematrix.com # growth in mankind. - Dwight D. Eisenhower
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED] But you side stepped the BC issue. ?? Not sure I get you. BC issue? Backward-compatibility issue. --DD You can always implement (and test) the algorithm above, and see if you can get the committers to put it in. -- DD Sure, but save me 15 minutes :-)... What file(s) of the source is the expansion of a property expression found in? Should be the new PropertyHelper in the top level package. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Jack J. Woehr [mailto:[EMAIL PROTECTED] Okay, Alexey wrote: Just add something like if (project.getProperty(ant.bc)!=null) ... to make them happier. Was he speaking abstractly or is there an ant.bc property really? Can't know for sure, but Alexey might have been facetious... There's no such property, and any new 'magic' property will be a struggle to get past IMHO. Committers would have to chime in at this point... --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/src/etc/testcases/taskdefs/optional xmlvalidate.xml
antoine 2004/06/02 13:32:11 Modified:.WHATSNEW CONTRIBUTORS src/main/org/apache/tools/ant/taskdefs/optional XMLValidateTask.java src/testcases/org/apache/tools/ant/taskdefs/optional XmlValidateTest.java src/etc/testcases/taskdefs/optional xmlvalidate.xml Added: src/etc/testcases/taskdefs/optional/xml endpiece-noSchema-invalid.xml endpiece-noSchema.xml Log: Addition of a nested property element to the XMLValidateTask to support string parser properties PR: 23395 Submitted by: Matthew Hawthorne (mhawthorne at alumni dot pitt dot edu) Revision ChangesPath 1.1 ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema-invalid.xml Index: endpiece-noSchema-invalid.xml === ?xml version=1.0 encoding=UTF-8? !-- Invalid test XML file without any schema refeferences -- doc section title=endpiece With a little luck, the network will pick me up. This is Ripley - last survivor of The Nostromo - signing off. /section invalidelement/ /doc 1.1 ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema.xml Index: endpiece-noSchema.xml === ?xml version=1.0 encoding=UTF-8? !-- Test XML file without any schema refeferences -- doc section title=endpiece With a little luck, the network will pick me up. This is Ripley - last survivor of The Nostromo - signing off. /section /doc 1.611 +3 -0 ant/WHATSNEW Index: WHATSNEW === RCS file: /home/cvs/ant/WHATSNEW,v retrieving revision 1.610 retrieving revision 1.611 diff -u -r1.610 -r1.611 --- WHATSNEW 2 Jun 2004 12:09:45 - 1.610 +++ WHATSNEW 2 Jun 2004 20:32:11 - 1.611 @@ -128,6 +128,9 @@ Other changes: -- +* xmlvalidate has now a property nested element, + allowing to set string properties for the parser + Bugzilla Report 23395. * Docs fixes for xmlvalidate.html, javadoc.html, starteam. Bugzilla Reports 27092, 27284, 27554. 1.17 +3 -3 ant/CONTRIBUTORS Index: CONTRIBUTORS === RCS file: /home/cvs/ant/CONTRIBUTORS,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- CONTRIBUTORS 7 May 2004 18:10:34 - 1.16 +++ CONTRIBUTORS 2 Jun 2004 20:32:11 - 1.17 @@ -9,7 +9,7 @@ Anton Mazkovoi Arnaud Vandyck Arnout J. Kuiper -Aslak Hellesøy +Aslak Helles?y Avik Sengupta Balazs Fejes 2 Benoit Moussaud @@ -17,7 +17,6 @@ Brian Deitte Brian Felder Bruce Atherton -chanezon Charles Hudak Charlie Hubbard Chris Povirk @@ -72,7 +71,7 @@ Irene Rusman Jack J. Woehr James Duncan Davidson -Jan Matèrne +Jan Mat?rne Jason Hunter Jason Pettiss Jason Salter @@ -122,6 +121,7 @@ Matt Foemmel Matt Humphrey Matt Small +Matthew Hawthorne Matthew Inger Matthew Kuperus Heun Matthew Watson 1.41 +193 -44 ant/src/main/org/apache/tools/ant/taskdefs/optional/XMLValidateTask.java Index: XMLValidateTask.java === RCS file: /home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/XMLValidateTask.java,v retrieving revision 1.40 retrieving revision 1.41 diff -u -r1.40 -r1.41 --- XMLValidateTask.java 9 Mar 2004 16:48:15 - 1.40 +++ XMLValidateTask.java 2 Jun 2004 20:32:11 - 1.41 @@ -35,6 +35,7 @@ import org.apache.tools.ant.types.XMLCatalog; import org.apache.tools.ant.util.FileUtils; import org.apache.tools.ant.util.JAXPUtils; + import org.xml.sax.EntityResolver; import org.xml.sax.ErrorHandler; import org.xml.sax.InputSource; @@ -68,7 +69,7 @@ protected boolean failOnError = true; protected boolean warn = true; protected boolean lenient = false; -protected String readerClassName = null; +protected String readerClassName = null; /** file to be validated */ protected File file = null; @@ -76,20 +77,24 @@ protected Vector filesets = new Vector(); protected Path classpath; - /** * the parser is viewed as a SAX2 XMLReader. If a SAX1 parser is specified, * it's wrapped in an adapter that make it behave as a XMLReader. * a more 'standard' way of doing this would be to use the JAXP1.1 SAXParser * interface. */ -protected XMLReader xmlReader = null; // XMLReader
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote: There's no such property, and any new 'magic' property will be a struggle to get past IMHO. Committers would have to chime in at this point... --DD It can be a command-line option or a property option. Looks like I can just implement PropertyHelper.replacePropertiesRecursively() and make the use of it or PropertyHelper.replaceProperties() optional. -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
In my opinion, the problem reported is a bug, even if for instance JDK 1.4 regexp has a similar bug. I would go for fixing the bug without BC, in order not to make the code too complicated. This is just me though. Cheers, Antoine Jack J. Woehr wrote: Dominique Devienne wrote: There's no such property, and any new 'magic' property will be a struggle to get past IMHO. Committers would have to chime in at this point... --DD It can be a command-line option or a property option. Looks like I can just implement PropertyHelper.replacePropertiesRecursively() and make the use of it or PropertyHelper.replaceProperties() optional. -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant CONTRIBUTORS
antoine 2004/06/02 14:01:34 Modified:.CONTRIBUTORS Log: Accentuated characters had been converted to question marks, now fixed Revision ChangesPath 1.18 +2 -2 ant/CONTRIBUTORS Index: CONTRIBUTORS === RCS file: /home/cvs/ant/CONTRIBUTORS,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- CONTRIBUTORS 2 Jun 2004 20:32:11 - 1.17 +++ CONTRIBUTORS 2 Jun 2004 21:01:34 - 1.18 @@ -9,7 +9,7 @@ Anton Mazkovoi Arnaud Vandyck Arnout J. Kuiper -Aslak Helles?y +Aslak Hellesøy Avik Sengupta Balazs Fejes 2 Benoit Moussaud @@ -71,7 +71,7 @@ Irene Rusman Jack J. Woehr James Duncan Davidson -Jan Mat?rne +Jan Matèrne Jason Hunter Jason Pettiss Jason Salter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 23395] - Adding property element to xmlvalidate
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=23395. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=23395 Adding property element to xmlvalidate [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 21:05 --- checked into HEAD, will also be in the ANT_16 branch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29334] - Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29334. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29334 Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Target Milestone|--- |1.6.2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Possible Ant 1.7 alpha bug: property expansion.
From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED] In my opinion, the problem reported is a bug, even if for instance JDK 1.4 regexp has a similar bug. The JDK regex stuff is a tangent. It's just my own code to do Ant-like property substitution (or Shell like, or DOS like, as it's flexible) outside of Ant (or inside actually). Using greedy matching and/or recursive behavior as outlined by Jack, I guess I could also achieve nested property substitutions, but that's beside the point. I would go for fixing the bug without BC, in order not to make the code too complicated. This is just me though. Cool. Then people wouldn't need ac:propertycopy and/or the macrodef trick, or the propertyfile trick. Lets see what other committers think. Thanks Antoine, and glad to see you back in the saddle ;-) --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: ant/src/etc/testcases/taskdefs/optional xmlvalidate.xml
antoine 2004/06/02 14:13:18 Modified:.Tag: ANT_16_BRANCH WHATSNEW CONTRIBUTORS src/main/org/apache/tools/ant/taskdefs/optional Tag: ANT_16_BRANCH XMLValidateTask.java src/testcases/org/apache/tools/ant/taskdefs/optional Tag: ANT_16_BRANCH XmlValidateTest.java src/etc/testcases/taskdefs/optional Tag: ANT_16_BRANCH xmlvalidate.xml Added: src/etc/testcases/taskdefs/optional/xml Tag: ANT_16_BRANCH endpiece-noSchema-invalid.xml endpiece-noSchema.xml Log: Merge from HEAD Addition of properties for the parser as nested elements PR: 23395 Submitted by: Matthew Hawthorne (mhawthorne at alumni dot pitt dot edu) Revision ChangesPath No revision No revision 1.1.2.1 +0 -0 ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema-invalid.xml Index: endpiece-noSchema-invalid.xml === RCS file: /home/cvs/ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema-invalid.xml,v retrieving revision 1.1 retrieving revision 1.1.2.1 diff -u -r1.1 -r1.1.2.1 1.1.2.1 +0 -0 ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema.xml Index: endpiece-noSchema.xml === RCS file: /home/cvs/ant/src/etc/testcases/taskdefs/optional/xml/endpiece-noSchema.xml,v retrieving revision 1.1 retrieving revision 1.1.2.1 diff -u -r1.1 -r1.1.2.1 No revision No revision 1.503.2.95 +3 -0 ant/WHATSNEW Index: WHATSNEW === RCS file: /home/cvs/ant/WHATSNEW,v retrieving revision 1.503.2.94 retrieving revision 1.503.2.95 diff -u -r1.503.2.94 -r1.503.2.95 --- WHATSNEW 2 Jun 2004 12:10:58 - 1.503.2.94 +++ WHATSNEW 2 Jun 2004 21:13:17 - 1.503.2.95 @@ -98,6 +98,9 @@ Other changes: -- +* xmlvalidate has now a property nested element, + allowing to set string properties for the parser + Bugzilla Report 23395. * Docs fixes for xmlvalidate.html, javadoc.html, starteam. Bugzilla Reports 27092, 27284, 27554. 1.1.2.11 +1 -1 ant/CONTRIBUTORS Index: CONTRIBUTORS === RCS file: /home/cvs/ant/CONTRIBUTORS,v retrieving revision 1.1.2.10 retrieving revision 1.1.2.11 diff -u -r1.1.2.10 -r1.1.2.11 --- CONTRIBUTORS 28 Apr 2004 06:18:40 - 1.1.2.10 +++ CONTRIBUTORS 2 Jun 2004 21:13:17 - 1.1.2.11 @@ -17,7 +17,6 @@ Brian Deitte Brian Felder Bruce Atherton -chanezon Charles Hudak Charlie Hubbard Chris Povirk @@ -120,6 +119,7 @@ Matt Foemmel Matt Humphrey Matt Small +Matthew Hawthorne Matthew Inger Matthew Kuperus Heun Matthew Watson No revision No revision 1.36.2.5 +193 -44 ant/src/main/org/apache/tools/ant/taskdefs/optional/XMLValidateTask.java Index: XMLValidateTask.java === RCS file: /home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/XMLValidateTask.java,v retrieving revision 1.36.2.4 retrieving revision 1.36.2.5 diff -u -r1.36.2.4 -r1.36.2.5 --- XMLValidateTask.java 9 Mar 2004 17:01:41 - 1.36.2.4 +++ XMLValidateTask.java 2 Jun 2004 21:13:18 - 1.36.2.5 @@ -35,6 +35,7 @@ import org.apache.tools.ant.types.XMLCatalog; import org.apache.tools.ant.util.FileUtils; import org.apache.tools.ant.util.JAXPUtils; + import org.xml.sax.EntityResolver; import org.xml.sax.ErrorHandler; import org.xml.sax.InputSource; @@ -68,7 +69,7 @@ protected boolean failOnError = true; protected boolean warn = true; protected boolean lenient = false; -protected String readerClassName = null; +protected String readerClassName = null; /** file to be validated */ protected File file = null; @@ -76,20 +77,24 @@ protected Vector filesets = new Vector(); protected Path classpath; - /** * the parser is viewed as a SAX2 XMLReader. If a SAX1 parser is specified, * it's wrapped in an adapter that make it behave as a XMLReader. * a more 'standard' way of doing this would be to use the JAXP1.1 SAXParser * interface. */ -protected XMLReader xmlReader = null; // XMLReader used to validation process -protected ValidatorErrorHandler errorHandler -= new ValidatorErrorHandler(); // to report sax parsing errors +protected XMLReader xmlReader = null; +// XMLReader used to validation
cvs commit: ant/docs/manual/OptionalTasks ftp.html
antoine 2004/06/02 14:18:41 Modified:.WHATSNEW docs/manual install.html docs/manual/OptionalTasks ftp.html Log: Doc fix concerning the library requirements of the ftp task PR: 29334 Submitted by: Steve Cohen (scohen at apache dot org) Revision ChangesPath 1.612 +3 -0 ant/WHATSNEW Index: WHATSNEW === RCS file: /home/cvs/ant/WHATSNEW,v retrieving revision 1.611 retrieving revision 1.612 diff -u -r1.611 -r1.612 --- WHATSNEW 2 Jun 2004 20:32:11 - 1.611 +++ WHATSNEW 2 Jun 2004 21:18:41 - 1.612 @@ -128,6 +128,9 @@ Other changes: -- +* doc fix concerning the dependencies of the ftp task + Bugzilla Report 29334. + * xmlvalidate has now a property nested element, allowing to set string properties for the parser Bugzilla Report 23395. 1.70 +1 -1 ant/docs/manual/install.html Index: install.html === RCS file: /home/cvs/ant/docs/manual/install.html,v retrieving revision 1.69 retrieving revision 1.70 diff -u -r1.69 -r1.70 --- install.html 17 Feb 2004 07:59:36 - 1.69 +++ install.html 2 Jun 2004 21:18:41 - 1.70 @@ -403,7 +403,7 @@ tda name=commons-netcommons-net.jar/td tdftp, rexec and telnet tasksbr jakarta-oro 2.0.1 or later is required in any case together with commons-net.br -For a use with a Microsoft FTP server, a minimum version of commons-net of 1.2.0 or CVS HEAD from February 2004 or later is required. +For a use with a Microsoft FTP server, a minimum version of commons-net of 1.2.1 is required. /td tda href=http://jakarta.apache.org/commons/net/index.html; target=_tophttp://jakarta.apache.org/commons/net/index.html/a/td 1.25 +4 -2 ant/docs/manual/OptionalTasks/ftp.html Index: ftp.html === RCS file: /home/cvs/ant/docs/manual/OptionalTasks/ftp.html,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- ftp.html 17 Feb 2004 07:59:36 - 1.24 +++ ftp.html 2 Jun 2004 21:18:41 - 1.25 @@ -14,8 +14,10 @@ to perform each task./p pbNote:/b This task depends on external libraries not included in the Ant distribution. See a href=../install.html#commons-netLibrary Dependencies/a for more information./p -pThe ftp task makes no attempt to determine what file system syntax is -required by the remote server, and defaults to Unix standards. +pThe ftp task attempts to determine what file system is in place on the FTP server. +Supported server types are Unix, NT, OS2, VMS, and OS400. In addition, NT and OS400 servers +which have been configured to display the directory in Unix style are also supported correctly. +Otherwise, the system will default to Unix standards. iremotedir/i must be specified in the exact syntax required by the ftp server. If the usual Unix conventions are not supported by the server, iseparator/i can be used to set the file separator that should be used - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 29334] - Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29334. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29334 Update Ant Manual to reflect latest changes to jakarta-commons/net for FTP task [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-06-02 21:24 --- Changes submitted. Thanks. Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote: Cool. Then people wouldn't need ac:propertycopy and/or the macrodef trick, or the propertyfile trick. Lets see what other committers think. Should this lowly non-committer play with code or await some kind of consensus on design? -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote: Code has momentum. Design talk does not. Plat at will. --DD Okay. I'm going to add one class ..ant.util.RecursivePropertyParser and call it from ..ant.PropertyHelper.replacePropertiesRecursively() and add some switch between that method and .ant.PropertyHelper.replaceProperties to allow review and comparison. Does that sound reasonable? -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Possible Ant 1.7 alpha bug: property expansion.
Dominique Devienne wrote: It does to me. Just throw in a test case too. --DD Okay. Thanks. -- Jack J. Woehr # We have gone from the horse and buggy Senior Consultant # to the moon rocket in one lifetime, but Purematrix, Inc. # there has not been a corresponding moral www.purematrix.com # growth in mankind. - Dwight D. Eisenhower - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
