DO NOT REPLY [Bug 25181] - SYMLINK task creates cyclic symlinks

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181

SYMLINK task creates cyclic symlinks





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 01:49 ---
Created an attachment (id=9654)
Fix for bug 25181 with coresponding tests

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25181] - SYMLINK task creates cyclic symlinks

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181

SYMLINK task creates cyclic symlinks





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 02:03 ---
The patch just attached contains an amended testcase that fails based on this
report with the old code, and a patch to make the amended test case pass.

In doing this I took the position that the recorded symlinks take precedence
over the existing links, since that seems to me to be the case that is likely to
be more common. As the patch stands running a recreate will alter existing links
to match the recorded version. I am not sure if links to files were altered in
the past, but I think that was the behavior (links to directories were
mishandled as per this bug). If it is desired, I could put in an atribute that
controls whether or not links are overwritten and set the behavior to be default
whichever way seems most useful to the rest of the world. Let me know if you
want me to do that.

This overwriting behavior is also covered in the amended testcase.

After I go eat dinner, I am going to check the manual page for symlink to see if
the overwiting behavior is documented and patch it if it is not.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25181] - SYMLINK task creates cyclic symlinks

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181

SYMLINK task creates cyclic symlinks





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 02:08 ---
Created an attachment (id=9655)
Fixed silly netscape html wrapper (obsoletes previous attachment)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25181] - [PATCH] symlink task creates cyclic symlinks

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25181

[PATCH] symlink task creates cyclic symlinks

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|SYMLINK task creates cyclic |[PATCH] symlink task creates
   |symlinks|cyclic symlinks

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25687] New: - Macrodef'd Attribute Case

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25687

Macrodef'd Attribute Case

   Summary: Macrodef'd Attribute Case
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Other
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Any attributes passed to a macrodef'd macro are handled as if they are lower-
case.

So if I, for instance, add an attribute:


...


And attempt to access it as follows:


Ant will tell me the required attribute wasn't supplied.  Whereas if the 
attribute name is 'myattribute' it works regardless of the supplied case of 
attribute in the call.

This behaviour should be improved or, at the very least, the documentation 
should indicate this minor flaw, to avoid confusion.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

new task 'ants' required or not.

2003-12-22 Thread Sathyanarayana V. 
Hi All,

Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task to 
build/compile all the subprojectsof a project.  My purpose was to have  the 
compile time errors of all the subprojects as part of automated build report. 
The 'ant' task will stop building as soon as one subproject fails. I tried 
using java/exec tasks with 'failonerror '  attribute as false, but the problem 
with  this approach is that build status of subprojects is not available to the 
main build process and resulting Total build successful though subprojects are 
failing in-between.

   So, I have written new task  called 'ants' and used for my automated builds. 
This task internally uses 'ant' only.  What I would like to know is: Can I post 
this task of mine to apache or Is there any existing task/workaround available 
for the above required behavior.

Thanks in advance
Sathya

Re: new task 'ants' required or not.

2003-12-22 Thread Steve Loughran 
Sathyanarayana V. wrote:
Hi All,
	Recently,  as part of automating my project builds, I have used CruiseControl along with Ant.  Surprisingly, I didn't find any task to build/compile all the subprojectsof a project.  My purpose was to have  the compile time errors of all the subprojects as part of automated build report. The 'ant' task will stop building as soon as one subproject fails. I tried using java/exec tasks with 'failonerror '  attribute as false, but the problem with  this approach is that build status of subprojects is not available to the main build process and resulting Total build successful though subprojects are failing in-between.
OK
   So, I have written new task  called 'ants' and used for my automated builds. This task internally uses 'ant' only.  What I would like to know is: Can I post this task of mine to apache or Is there any existing task/workaround available for the above required behavior.
Ant 1.6 has ' that wil bulk compile a project ... does this do 
what you want or are there changes you'd recommend?

Thanks in advance
Sathya


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: new task 'ants' required or not.

2003-12-22 Thread Peter Reilly 
Steve Loughran wrote:
Sathyanarayana V. wrote:
Hi All,
Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task 
to build/compile all the subprojectsof a project.  My purpose was 
to have  the compile time errors of all the subprojects as part of 
automated build report. The 'ant' task will stop building as soon as 
one subproject fails. I tried using java/exec tasks with 'failonerror 
'  attribute as false, but the problem with  this approach is that 
build status of subprojects is not available to the main build 
process and resulting Total build successful though subprojects are 
failing in-between.

OK
   So, I have written new task  called 'ants' and used for my 
automated builds. This task internally uses 'ant' only.  What I would 
like to know is: Can I post this task of mine to apache or Is there 
any existing task/workaround available for the above required behavior.

Ant 1.6 has ' that wil bulk compile a project ... does this do 
what you want or are there changes you'd recommend?
Also ant 1.6 has a -keep-going which will continue exectuting targets 
that do not rely on the task that failed.
Peter


Thanks in advance
Sathya


-
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]

cvs commit: ant/src/etc/testcases/taskdefs macrodef.xml

2003-12-22 Thread peterreilly 
peterreilly2003/12/22 01:46:23

  Modified:docs/manual/CoreTasks macrodef.html
   src/main/org/apache/tools/ant/taskdefs MacroDef.java
MacroInstance.java
   src/testcases/org/apache/tools/ant/taskdefs
MacroDefTest.java
   src/etc/testcases/taskdefs macrodef.xml
  Log:
  Macrodef can only see lower case attribute names due to its
  use of DynamicConfigurator.
  Fix the doc and the code to at least make this consistent.
  PR: 25687
  Obtained from: Geoffrey Wiseman
  
  Revision  ChangesPath
  1.7   +5 -1  ant/docs/manual/CoreTasks/macrodef.html
  
  Index: macrodef.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/macrodef.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- macrodef.html 3 Dec 2003 13:16:01 -   1.6
  +++ macrodef.html 22 Dec 2003 09:46:23 -  1.7
  @@ -59,7 +59,11 @@
 AT this location").
 The escape sequence @@{x} is used to allow @{x} to be
 placed in the text without substitution of x.
  -  This corresponds to the $${x} escape sequence for properties
  +  This corresponds to the $${x} escape sequence for properties.
  +
  +
  +  The case of the attribute is ignored, so @{myAttribute} is treated the
  +  same as @{MyAttribute}.
   
   Parameters
   
  
  
  
  1.15  +2 -1  ant/src/main/org/apache/tools/ant/taskdefs/MacroDef.java
  
  Index: MacroDef.java
  ===
  RCS file: /home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/MacroDef.java,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- MacroDef.java 3 Dec 2003 13:16:01 -   1.14
  +++ MacroDef.java 22 Dec 2003 09:46:23 -  1.15
  @@ -57,6 +57,7 @@
   import java.util.ArrayList;
   import java.util.List;
   import java.util.Map;
  +import java.util.Locale;
   import java.util.HashMap;
   
   import org.apache.tools.ant.AntTypeDefinition;
  @@ -293,7 +294,7 @@
   throw new BuildException(
   "Illegal name [" + name + "] for attribute");
   }
  -this.name = name;
  +this.name = name.toLowerCase(Locale.US);
   }
   
   /**
  
  
  
  1.14  +2 -1  
ant/src/main/org/apache/tools/ant/taskdefs/MacroInstance.java
  
  Index: MacroInstance.java
  ===
  RCS file: 
/home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/MacroInstance.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- MacroInstance.java16 Dec 2003 21:13:15 -  1.13
  +++ MacroInstance.java22 Dec 2003 09:46:23 -  1.14
  @@ -57,6 +57,7 @@
   import java.util.ArrayList;
   import java.util.List;
   import java.util.Iterator;
  +import java.util.Locale;
   import java.util.Map;
   import java.util.Set;
   import java.util.HashSet;
  @@ -200,7 +201,7 @@
   case STATE_EXPECT_NAME:
   if (ch == '}') {
   state = STATE_NORMAL;
  -String name = macroName.toString();
  +String name = 
macroName.toString().toLowerCase(Locale.US);
   String value = (String) macroMapping.get(name);
   if (value == null) {
   ret.append("@{" + name + "}");
  
  
  
  1.6   +6 -0  
ant/src/testcases/org/apache/tools/ant/taskdefs/MacroDefTest.java
  
  Index: MacroDefTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/taskdefs/MacroDefTest.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- MacroDefTest.java 3 Dec 2003 13:16:01 -   1.5
  +++ MacroDefTest.java 22 Dec 2003 09:46:23 -  1.6
  @@ -103,5 +103,11 @@
   "double",
   "@{prop} is 'property', value of ${property} is 'A property 
value'");
   }
  +
  +public void testIgnoreCase() {
  +expectLog(
  +"ignorecase",
  +"a is ab is b");
  +}
   }
   
  
  
  
  1.6   +11 -0 ant/src/etc/testcases/taskdefs/macrodef.xml
  
  Index: macrodef.xml
  ===
  RCS file: /home/cvs/ant/src/etc/testcases/taskdefs/macrodef.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- macrodef.xml  3 Dec 2003 13:16:01 -   1.5
  +++ macrodef.xml  22 Dec 2003 09:46:23 -  1.6
  @@ -75,4 +75,15 @@
   
   
 
  +
  +  
  +
  +  
  +  
  +@{myattribute} is @{MYATTRIBUTE}
  +  
  +
  +
  +

Re: new task 'ants' required or not.

2003-12-22 Thread Antoine Lévy-Lambert 
Sathyanarayana V. wrote:
Hi All,
Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task to 
build/compile all the subprojectsof a project.  My purpose was to have  the 
compile time errors of all the subprojects as part of automated build report. 
The 'ant' task will stop building as soon as one subproject fails. I tried 
using java/exec tasks with 'failonerror '  attribute as false, but the problem 
with  this approach is that build status of subprojects is not available to the 
main build process and resulting Total build successful though subprojects are 
failing in-between.
  So, I have written new task  called 'ants' and used for my automated builds. 
This task internally uses 'ant' only.  What I would like to know is: Can I post 
this task of mine to apache or Is there any existing task/workaround available 
for the above required behavior.
Thanks in advance
Sathya
 

Hi Sathya,
thanks for letting us know about your new task 'ants'. In ant 1.6.0 we 
have the  task which can process a number of ant files, and can 
run with failonerror="false". The only thing is that it does not have a 
mechanism to report back to the main project which subprojects have 
failed. Maybe the way of recording which projects have failed would be 
with a custom listener.

Otherwise, if you use ant-contrib, you can use  or  to 
do iterations, and   to catch build exceptions.

Another possibility would be that you promote your sub-projects to 
projects and build each of them with gump, another Apache tool 
(http://jakarta.apache.org/gump/).

I do not know whether you can then combine gump and CruiseControl or 
whether this is an overkill.

Cheers,
Antoine
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/src/etc/testcases/taskdefs macrodef.xml

2003-12-22 Thread peterreilly 
peterreilly2003/12/22 02:08:58

  Modified:docs/manual/CoreTasks Tag: ANT_16_BRANCH macrodef.html
   src/main/org/apache/tools/ant/taskdefs Tag: ANT_16_BRANCH
MacroDef.java MacroInstance.java
   src/testcases/org/apache/tools/ant/taskdefs Tag:
ANT_16_BRANCH MacroDefTest.java
   src/etc/testcases/taskdefs Tag: ANT_16_BRANCH macrodef.xml
  Log:
  Sync with HEAD
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.2.2.6   +5 -1  ant/docs/manual/CoreTasks/macrodef.html
  
  Index: macrodef.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/macrodef.html,v
  retrieving revision 1.2.2.5
  retrieving revision 1.2.2.6
  diff -u -r1.2.2.5 -r1.2.2.6
  --- macrodef.html 3 Dec 2003 13:22:30 -   1.2.2.5
  +++ macrodef.html 22 Dec 2003 10:08:58 -  1.2.2.6
  @@ -60,7 +60,11 @@
 AT this location").
 The escape sequence @@{x} is used to allow @{x} to be
 placed in the text without substitution of x.
  -  This corresponds to the $${x} escape sequence for properties
  +  This corresponds to the $${x} escape sequence for properties.
  +
  +
  +  The case of the attribute is ignored, so @{myAttribute} is treated the
  +  same as @{MyAttribute}.
   
   Parameters
   
  
  
  
  No   revision
  No   revision
  1.7.2.8   +2 -1  ant/src/main/org/apache/tools/ant/taskdefs/MacroDef.java
  
  Index: MacroDef.java
  ===
  RCS file: /home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/MacroDef.java,v
  retrieving revision 1.7.2.7
  retrieving revision 1.7.2.8
  diff -u -r1.7.2.7 -r1.7.2.8
  --- MacroDef.java 3 Dec 2003 13:22:30 -   1.7.2.7
  +++ MacroDef.java 22 Dec 2003 10:08:58 -  1.7.2.8
  @@ -57,6 +57,7 @@
   import java.util.ArrayList;
   import java.util.List;
   import java.util.Map;
  +import java.util.Locale;
   import java.util.HashMap;
   
   import org.apache.tools.ant.AntTypeDefinition;
  @@ -293,7 +294,7 @@
   throw new BuildException(
   "Illegal name [" + name + "] for attribute");
   }
  -this.name = name;
  +this.name = name.toLowerCase(Locale.US);
   }
   
   /**
  
  
  
  1.5.2.9   +2 -1  
ant/src/main/org/apache/tools/ant/taskdefs/MacroInstance.java
  
  Index: MacroInstance.java
  ===
  RCS file: 
/home/cvs/ant/src/main/org/apache/tools/ant/taskdefs/MacroInstance.java,v
  retrieving revision 1.5.2.8
  retrieving revision 1.5.2.9
  diff -u -r1.5.2.8 -r1.5.2.9
  --- MacroInstance.java16 Dec 2003 21:19:26 -  1.5.2.8
  +++ MacroInstance.java22 Dec 2003 10:08:58 -  1.5.2.9
  @@ -57,6 +57,7 @@
   import java.util.ArrayList;
   import java.util.List;
   import java.util.Iterator;
  +import java.util.Locale;
   import java.util.Map;
   import java.util.Set;
   import java.util.HashSet;
  @@ -200,7 +201,7 @@
   case STATE_EXPECT_NAME:
   if (ch == '}') {
   state = STATE_NORMAL;
  -String name = macroName.toString();
  +String name = 
macroName.toString().toLowerCase(Locale.US);
   String value = (String) macroMapping.get(name);
   if (value == null) {
   ret.append("@{" + name + "}");
  
  
  
  No   revision
  No   revision
  1.2.2.4   +6 -0  
ant/src/testcases/org/apache/tools/ant/taskdefs/MacroDefTest.java
  
  Index: MacroDefTest.java
  ===
  RCS file: 
/home/cvs/ant/src/testcases/org/apache/tools/ant/taskdefs/MacroDefTest.java,v
  retrieving revision 1.2.2.3
  retrieving revision 1.2.2.4
  diff -u -r1.2.2.3 -r1.2.2.4
  --- MacroDefTest.java 3 Dec 2003 13:22:30 -   1.2.2.3
  +++ MacroDefTest.java 22 Dec 2003 10:08:58 -  1.2.2.4
  @@ -103,5 +103,11 @@
   "double",
   "@{prop} is 'property', value of ${property} is 'A property 
value'");
   }
  +
  +public void testIgnoreCase() {
  +expectLog(
  +"ignorecase",
  +"a is ab is b");
  +}
   }
   
  
  
  
  No   revision
  No   revision
  1.2.2.4   +11 -0 ant/src/etc/testcases/taskdefs/macrodef.xml
  
  Index: macrodef.xml
  ===
  RCS file: /home/cvs/ant/src/etc/testcases/taskdefs/macrodef.xml,v
  retrieving revision 1.2.2.3
  retrieving revision 1.2.2.4
  diff -u -r1.2.2.3 -r1.2.2.4
  --- macrodef.xml  3 Dec 2

DO NOT REPLY [Bug 25687] - Macrodef'd Attribute Case

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25687

Macrodef'd Attribute Case

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 10:09 ---
Thanks for the report.
This slipped by due a last minute backward compibility issue with
DynamicConfigurator.
The doc is fixed (for ant 1.6.1) and the code now ignores the case of the
attribute.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

a comment about xml namespace

2003-12-22 Thread Jim Fuller 
Consider the following;



http://www.w3c.org/RDF/";
xmlns:DC="http://purl.org/RDF/DC/";>
http://purl.org/metadata/dublin_core_elements"; 
DC:Title="namespace build"  
DC:Creator="Jim Fuller"
DC:Subject="xml namespaces" 
DC:Description="Contains Ant artifacts for building" 
DC:Publisher="Webcomposite s.r.o." 
DC:Format="text/html" 
DC:Type="Technical Report" 
DC:Language="en" 
DC:Date="12/22/2003"/>


intermixing of namespaces






XML Namespaces was initially created to avoid collision within documents
that have multiple xml vocabularies. 

Ant seems to assume by default that all namespaces have something to do
with build processing...is their any convention planned for having Ant
ignore specific namespace elements...or more usefully all namespaces
that have no Ant processing associated with it ?

For instance, the above example maybe generated by a sophisticated XML
editor that uses Dublin Core and RDF as a method of tracking versions of
the build.xml file. This is a simple use case, there are other more
important use cases involving xml db repositories.

Regards, Jim Fuller



Jim Fuller Technical Architect  WebComposite s.r.o.
[EMAIL PROTECTED]/http://www.ruminate.co.uk
Co-Author ISBN 1861007213 Professional PHP4 XML
Co-Author ISBN 1861008074 Professional PHP Web Services
Technical Reviewer 'Beginning XSLT', 'Beginning Databases',
'XML Antipatterns' and various other xml / web service books








-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a comment about xml namespace

2003-12-22 Thread Peter Reilly 
This is what I (think I) originally proposed, but did
not articulate it correctly.
http://marc.theaimsgroup.com/?l=ant-dev&m=105240500519029&w=2
Peter
Jim Fuller wrote:
Consider the following;


	http://www.w3c.org/RDF/";
xmlns:DC="http://purl.org/RDF/DC/";>
	
RDF:HREF="http://purl.org/metadata/dublin_core_elements"; 
		DC:Title="namespace build" 	
		DC:Creator="Jim Fuller"
		DC:Subject="xml namespaces" 
		DC:Description="Contains Ant artifacts for building" 
		DC:Publisher="Webcomposite s.r.o." 
		DC:Format="text/html" 
		DC:Type="Technical Report" 
		DC:Language="en" 
		DC:Date="12/22/2003"/>
	
	
	intermixing of namespaces
	
	
		
	


XML Namespaces was initially created to avoid collision within documents
that have multiple xml vocabularies. 

Ant seems to assume by default that all namespaces have something to do
with build processing...is their any convention planned for having Ant
ignore specific namespace elements...or more usefully all namespaces
that have no Ant processing associated with it ?
For instance, the above example maybe generated by a sophisticated XML
editor that uses Dublin Core and RDF as a method of tracking versions of
the build.xml file. This is a simple use case, there are other more
important use cases involving xml db repositories.
Regards, Jim Fuller

Jim Fuller Technical Architect  WebComposite s.r.o.
[EMAIL PROTECTED]/http://www.ruminate.co.uk
Co-Author ISBN 1861007213 Professional PHP4 XML
Co-Author ISBN 1861008074 Professional PHP Web Services
Technical Reviewer 'Beginning XSLT', 'Beginning Databases',
'XML Antipatterns' and various other xml / web service books




-
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]

DO NOT REPLY [Bug 25697] New: - filterchain doesnt support nested "concatfilter" element

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25697

filterchain doesnt support nested "concatfilter" element

   Summary: filterchain doesnt support nested "concatfilter" element
   Product: Ant
   Version: 1.6.0
  Platform: PC
   URL: http://ant.apache.org/manual/CoreTypes/filterchain.html#
concatfilter
OS/Version: Windows NT/2K
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


and it should, as described in documentation

i used it in  task


 
 

 


i installed clean ant 1.6.0 with java 1.4.2

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25698] New: - tutorial-writing-tasks-src.zip corrupted

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25698

tutorial-writing-tasks-src.zip corrupted

   Summary: tutorial-writing-tasks-src.zip corrupted
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I downloaded apache-ant-1.6.0-bin.tar.bz2 and unpacked it. Now in the unpacked
dir, docs/manual/tutorial-writing-tasks-src.zip seems to be corrupt. E.g.:

ant16$ jar tvf docs/manual/tutorial-writing-tasks-src.zip 
 0 Mon Sep 01 17:01:16 EDT 2003 src/
java.util.zip.ZipException: invalid block type
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:140)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:139)
at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:91)
at sun.tools.jar.Main.list(Main.java:744)
at sun.tools.jar.Main.run(Main.java:192)
at sun.tools.jar.Main.main(Main.java:904)
ant16$ ls -l docs/manual/tutorial-writing-tasks-src.zip 
-rw-r--r--1 jglick   jglick   2474 Dec 18 15:12
docs/manual/tutorial-writing-tasks-src.zip
ant16$ cksum docs/manual/tutorial-writing-tasks-src.zip
937430050 2474 docs/manual/tutorial-writing-tasks-src.zip

Some kind of packaging error perhaps? Is this file corrupt for other people too?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: new task 'ants' required or not.

2003-12-22 Thread Sathyanarayana V. 

Probelm with 'subant' is: it doesnt communicate/contribute to overall build 
status. subprojects may fail, but  the overall process will be successful. 
Wouldnt it contribute in over all build status.

Thanks,
Sathya




-Original Message-
From: Peter Reilly [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 2:53 PM
To: Ant Developers List
Subject: Re: new task 'ants' required or not.


Steve Loughran wrote:

> Sathyanarayana V. wrote:
>
>> Hi All,
>>
>> Recently,  as part of automating my project builds, I have used 
>> CruiseControl along with Ant.  Surprisingly, I didn't find any task 
>> to build/compile all the subprojectsof a project.  My purpose was 
>> to have  the compile time errors of all the subprojects as part of 
>> automated build report. The 'ant' task will stop building as soon as 
>> one subproject fails. I tried using java/exec tasks with 'failonerror 
>> '  attribute as false, but the problem with  this approach is that 
>> build status of subprojects is not available to the main build 
>> process and resulting Total build successful though subprojects are 
>> failing in-between.
>
>
> OK
>
>>
>>So, I have written new task  called 'ants' and used for my 
>> automated builds. This task internally uses 'ant' only.  What I would 
>> like to know is: Can I post this task of mine to apache or Is there 
>> any existing task/workaround available for the above required behavior.
>
>
> Ant 1.6 has ' that wil bulk compile a project ... does this do 
> what you want or are there changes you'd recommend?

Also ant 1.6 has a -keep-going which will continue exectuting targets 
that do not rely on the task that failed.
Peter

>
>>
>> Thanks in advance
>> Sathya
>>
>>
>
>
>
> -
> 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]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: a comment about xml namespace

2003-12-22 Thread Steve Loughran 
Jim Fuller wrote:
Consider the following;


	http://www.w3c.org/RDF/";
xmlns:DC="http://purl.org/RDF/DC/";>
	
RDF:HREF="http://purl.org/metadata/dublin_core_elements"; 
		DC:Title="namespace build" 	
		DC:Creator="Jim Fuller"
		DC:Subject="xml namespaces" 
		DC:Description="Contains Ant artifacts for building" 
		DC:Publisher="Webcomposite s.r.o." 
		DC:Format="text/html" 
		DC:Type="Technical Report" 
		DC:Language="en" 
		DC:Date="12/22/2003"/>
	
	
	intermixing of namespaces
	
	
		
	


XML Namespaces was initially created to avoid collision within documents
that have multiple xml vocabularies. 

Ant seems to assume by default that all namespaces have something to do
with build processing...is their any convention planned for having Ant
ignore specific namespace elements...or more usefully all namespaces
that have no Ant processing associated with it ?
hmm. this looks more like you want XML in ant with no ant processing in it.
For instance, the above example maybe generated by a sophisticated XML
editor that uses Dublin Core and RDF as a method of tracking versions of
the build.xml file. This is a simple use case, there are other more
important use cases involving xml db repositories.
Ant1.7 lets you have any XML you like inside some task. So you could 
have a  task that required valid XML and took whatever was 
inside. Or even an  task that required valid RDF

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: new task 'ants' required or not.

2003-12-22 Thread Antoine Lévy-Lambert 
Sathyanarayana V. wrote:
Problem with 'subant' is: it doesnt communicate/contribute to overall build 
status. subprojects may fail, but  the overall process will be successful. 
Wouldnt it contribute in over all build status.
Thanks,
Sathya
 

My view is that ant is not designed to build several projects, with some 
projects failing and other being successful.
gump is really the tool that would be OK for this purpose.

Concerning your ants task, there was a proposal for something a bit 
similar called  which is a flavour of  which can 
return properties.

What you can do in ant 1.6 would be to use macrodef to describe the 
build of a generic subproject, and foreach or for from ant-contrib plus 
try/catch to get the status of each subproject

for instance (untested pseudocode)
macrodef build_one_subproject
try
build the subproject
catch
   
endmacrodef



${subroj_1-failure}
${subroj_2-failure}
${subroj_3-failure}
this would be doing what you would like.
You can probably iterate among your subprojects using for or foreach from 
ant-contrib.
Cheers,
Antoine

 

Sathyanarayana V. wrote:
   

Hi All,
   Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task 
to build/compile all the subprojectsof a project.  My purpose was 
to have  the compile time errors of all the subprojects as part of 
automated build report. The 'ant' task will stop building as soon as 
one subproject fails. I tried using java/exec tasks with 'failonerror 
'  attribute as false, but the problem with  this approach is that 
build status of subprojects is not available to the main build 
process and resulting Total build successful though subprojects are 
failing in-between.
 

OK
   

  So, I have written new task  called 'ants' and used for my 
automated builds. This task internally uses 'ant' only.  What I would 
like to know is: Can I post this task of mine to apache or Is there 
any existing task/workaround available for the above required behavior.
 

Ant 1.6 has ' that wil bulk compile a project ... does this do 
what you want or are there changes you'd recommend?
   

Also ant 1.6 has a -keep-going which will continue exectuting targets 
that do not rely on the task that failed.
Peter

 

Thanks in advance
Sathya
 

   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

EN: alias and JspC

2003-12-22 Thread Edson Alves Pereira 


> --
> De:   Edson Alves Pereira[SMTP:[EMAIL PROTECTED]
> Responder:Tomcat Users List
> Enviada:  segunda-feira, 22 de dezembro de 2003 10:22
> Para: 'Tomcat-User List'
> Assunto:  alias and JspC
> 
>   Hello folks, i´d like to know how can i define a alias for my JSP
> pages, for example usually we do:
> 
>   http://localhost/my-webapp/jsp/hello.jsp
> 
>   How can i make ant´s jspc tag build my JSP pages with /jsp as a
> default alias instead of / ( this infact isn´t a alias just a name before
> JSP page, but you got the idea )?
> 
>   Regards,
>   Edson
>

Re: new task 'ants' required or not.

2003-12-22 Thread Peter Reilly 
Sathyanarayana V. wrote:
Probelm with 'subant' is: it doesnt communicate/contribute to overall build status. subprojects may fail, but  the overall process will be successful. Wouldnt it contribute in over all build status.
 

This is now quite true,
If a subproject fails, subant will fail also.
With the -keep-going or -k option to ant,
if the subproject fails, subant will run the rest of the subprojects, 
but the overall build will still fail:

 
   
 
   
   
 
   
 
Generates:
Buildfile: subant.xml
badgood:
  [subant] File '/home/preilly/learning/ant/bad.xml' failed with message 
'Following error occured while executing this line
  [subant] /home/preilly/learning/ant/bad.xml:2: The content of elements must 
consist of well-formed character data or markup.'.
good:
[echo] Good
Target 'badgood' failed with message 'Following error occured while executing 
this line
/home/preilly/learning/ant/bad.xml:2: The content of elements must consist of 
well-formed character data or markup.'.
BUILD FAILED
/home/preilly/learning/ant/subant.xml:8: Following error occured while 
executing this line
/home/preilly/learning/ant/bad.xml:2: The content of elements must 
consist of well-formed character data or markup.

Peter
Thanks,
Sathya

-Original Message-
From: Peter Reilly [mailto:[EMAIL PROTECTED]
Sent: Monday, December 22, 2003 2:53 PM
To: Ant Developers List
Subject: Re: new task 'ants' required or not.
Steve Loughran wrote:
 

Sathyanarayana V. wrote:
   

Hi All,
   Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task 
to build/compile all the subprojectsof a project.  My purpose was 
to have  the compile time errors of all the subprojects as part of 
automated build report. The 'ant' task will stop building as soon as 
one subproject fails. I tried using java/exec tasks with 'failonerror 
'  attribute as false, but the problem with  this approach is that 
build status of subprojects is not available to the main build 
process and resulting Total build successful though subprojects are 
failing in-between.
 

OK
   

  So, I have written new task  called 'ants' and used for my 
automated builds. This task internally uses 'ant' only.  What I would 
like to know is: Can I post this task of mine to apache or Is there 
any existing task/workaround available for the above required behavior.
 

Ant 1.6 has ' that wil bulk compile a project ... does this do 
what you want or are there changes you'd recommend?
   

Also ant 1.6 has a -keep-going which will continue exectuting targets 
that do not rely on the task that failed.
Peter

 

Thanks in advance
Sathya
 

-
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]
-
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]

DO NOT REPLY [Bug 25704] New: - Support for Sun Solaris' Tar Format for long file name

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25704

Support for Sun Solaris' Tar Format for long file name

   Summary: Support for Sun Solaris' Tar Format for long file name
   Product: Ant
   Version: 1.6.0
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When file name is more than 100 characters, Sun splits the name and the path and
stores the file name in the first 100 characters of the header block and the
directory name of up to 155 characters at the end of the header block.

I modified ANT 1.6.1 to support Sun Solaris' Tar format. Please incorporate the
changes to the future release of ANT. Let me know if you need further
information at [EMAIL PROTECTED]



Jack Chen

/*
 * The Apache Software License, Version 1.1
 *
 * Copyright (c) 2000-2003 The Apache Software Foundation.  All rights
 * reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in
 *the documentation and/or other materials provided with the
 *distribution.
 *
 * 3. The end-user documentation included with the redistribution, if
 *any, must include the following acknowlegement:
 *   "This product includes software developed by the
 *Apache Software Foundation (http://www.apache.org/)."
 *Alternately, this acknowlegement may appear in the software itself,
 *if and wherever such third-party acknowlegements normally appear.
 *
 * 4. The names "Ant" and "Apache Software
 *Foundation" must not be used to endorse or promote products derived
 *from this software without prior written permission. For written
 *permission, please contact [EMAIL PROTECTED]
 *
 * 5. Products derived from this software may not be called "Apache"
 *nor may "Apache" appear in their names without prior written
 *permission of the Apache Group.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
 * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 * 
 *
 * This software consists of voluntary contributions made by many
 * individuals on behalf of the Apache Software Foundation.  For more
 * information on the Apache Software Foundation, please see
 * .
 */

package org.apache.tools.ant.taskdefs;

import java.io.BufferedOutputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.OutputStream;
import java.util.Enumeration;
import java.util.Vector;
import java.util.zip.GZIPOutputStream;
import org.apache.tools.ant.BuildException;
import org.apache.tools.ant.DirectoryScanner;
import org.apache.tools.ant.Project;
import org.apache.tools.ant.types.EnumeratedAttribute;
import org.apache.tools.ant.types.FileSet;
import org.apache.tools.ant.util.MergingMapper;
import org.apache.tools.ant.util.SourceFileScanner;
import org.apache.tools.bzip2.CBZip2OutputStream;
import org.apache.tools.tar.TarConstants;
import org.apache.tools.tar.TarEntry;
import org.apache.tools.tar.TarOutputStream;
import org.apache.tools.zip.UnixStat;

/**
 * Creates a tar archive.
 *
 * @author Stefano Mazzocchi
 * mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]
 * @author Stefan Bodewig
 * @author Magesh Umasankar
 *
 * @since Ant 1.1
 *
 * @ant.task category="packaging"
 */
public class Tar extends MatchingTask {

/**
 * @deprecated Tar.WARN is deprecated and is replaced with
 * Tar.TarLongFileMode.WARN
 */
public static final String WARN

DO NOT REPLY [Bug 25705] New: - Various broken links and other errors in Ant documentation

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25705

Various broken links and other errors in Ant documentation

   Summary: Various broken links and other errors in Ant
documentation
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Produced with this script:












where nbantext.jar contains this task:

http://www.netbeans.org/unbranded-source/browse/~checkout~/nbbuild/antsrc/org/netbeans/nbbuild/CheckLinks.java?content-type=text/plain

There are probably a few false positives in there but most look to be real 
errors.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25705] - Various broken links and other errors in Ant documentation

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25705

Various broken links and other errors in Ant documentation





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 17:57 ---
Created an attachment (id=9666)
Log of broken links and similar HTML errors

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25707] New: - [PATCH] Avoid XHTML and funny chars in manual

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25707

[PATCH] Avoid XHTML and funny chars in manual

   Summary: [PATCH] Avoid XHTML and funny chars in manual
   Product: Ant
   Version: 1.6.0
  Platform: All
OS/Version: All
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Encountered a few constructions which are not rendered well by Swing's HTML
renderer (and thus JavaHelp): XHTML minimalized closing tags; and odd characters
(like a non-ASCII right single quote).

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25707] - [PATCH] Avoid XHTML and funny chars in manual

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25707

[PATCH] Avoid XHTML and funny chars in manual





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 18:18 ---
Created an attachment (id=9668)
Suggested patch

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25707] - [PATCH] Avoid XHTML and funny chars in manual

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25707

[PATCH] Avoid XHTML and funny chars in manual





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 18:44 ---
Would  be ok to use ? - it should work
for xhtml and for pre xml html.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25709] New: - [PATCH] Remind user that Java 1.4+ includes its own regexp impl

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25709

[PATCH] Remind user that Java 1.4+ includes its own regexp impl

   Summary: [PATCH] Remind user that Java 1.4+ includes its own
regexp impl
   Product: Ant
   Version: 1.6.0
  Platform: All
OS/Version: All
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Should be self-explanatory.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25709] - [PATCH] Remind user that Java 1.4+ includes its own regexp impl

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25709

[PATCH] Remind user that Java 1.4+ includes its own regexp impl





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 18:19 ---
Created an attachment (id=9670)
Suggested patch

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25707] - [PATCH] Avoid XHTML and funny chars in manual

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25707

[PATCH] Avoid XHTML and funny chars in manual





--- Additional Comments From [EMAIL PROTECTED]  2003-12-22 19:07 ---
Yes, I think  works OK.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: new task 'ants' required or not.

2003-12-22 Thread Dale Anson 
Sounds like the proposed  is identical to the existing 
 in ant-contrib.

Dale
Antoine Lévy-Lambert wrote:
Sathyanarayana V. wrote:
Problem with 'subant' is: it doesnt communicate/contribute to overall 
build status. subprojects may fail, but  the overall process will be 
successful. Wouldnt it contribute in over all build status.

Thanks,
Sathya
 

My view is that ant is not designed to build several projects, with some 
projects failing and other being successful.
gump is really the tool that would be OK for this purpose.

Concerning your ants task, there was a proposal for something a bit 
similar called  which is a flavour of  which can 
return properties.

What you can do in ant 1.6 would be to use macrodef to describe the 
build of a generic subproject, and foreach or for from ant-contrib plus 
try/catch to get the status of each subproject

for instance (untested pseudocode)
macrodef build_one_subproject
try
build the subproject
catch
   
endmacrodef



${subroj_1-failure}
${subroj_2-failure}
${subroj_3-failure}
this would be doing what you would like.
You can probably iterate among your subprojects using for or foreach 
from ant-contrib.

Cheers,
Antoine

 

Sathyanarayana V. wrote:
  

Hi All,
   Recently,  as part of automating my project builds, I have used 
CruiseControl along with Ant.  Surprisingly, I didn't find any task 
to build/compile all the subprojectsof a project.  My purpose 
was to have  the compile time errors of all the subprojects as part 
of automated build report. The 'ant' task will stop building as soon 
as one subproject fails. I tried using java/exec tasks with 
'failonerror '  attribute as false, but the problem with  this 
approach is that build status of subprojects is not available to the 
main build process and resulting Total build successful though 
subprojects are failing in-between.

OK
  

  So, I have written new task  called 'ants' and used for my 
automated builds. This task internally uses 'ant' only.  What I 
would like to know is: Can I post this task of mine to apache or Is 
there any existing task/workaround available for the above required 
behavior.

Ant 1.6 has ' that wil bulk compile a project ... does this 
do what you want or are there changes you'd recommend?
  

Also ant 1.6 has a -keep-going which will continue exectuting targets 
that do not rely on the task that failed.
Peter

 

Thanks in advance
Sathya

  

-
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]

DO NOT REPLY [Bug 25711] New: - Perforce task 'p4submit' should *not* set p4.needsresolve to 0 upon success

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25711

Perforce task 'p4submit' should *not* set p4.needsresolve to 0 upon success

   Summary: Perforce task 'p4submit' should *not* set
p4.needsresolve to 0 upon success
   Product: Ant
   Version: unspecified
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Optional Tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When 'p4submit' finishes, it sets the property p4.needsresolve to 1 if the 
submit failed because some files need to be resolved before submission.  That's 
ok.  However, the docs state that p4submit sets the property to 0 if it 
succeeded.

That's incorrect behavior - firstly, because the target call flags 'if' 
and 'unless' check only if the property is set, not if it's set to 1.  This 
means it's harder to check if your perforce submit succeeded.  

The second problem is that ant properties are immutable - once they're set, 
they can't be changed.

That means I can't have my ant script do more than one submit at a time, 
because I won't be able to detect the results of the second submit.  That's not 
helpful.

I recognize there might be some backward-compatiblity issues - perhaps we 
should leave the existing property intact, and add a new property - 
p4.resolveneeded.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 25713] New: - reference string is too long

2003-12-22 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25713

reference string is too long 

   Summary: reference string is too long
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Major
  Priority: Other
 Component: Optional Tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The build runs OK on Win2K server. But on my XP box, it failed on one of the 
projects. Error message -

[csc] fatal error CS2021: File name ';D:\Upside4\build\output\bin\Util.dll
;D:\Upside4\build\output\bin\Infragistics.WebUI.UltraWebChart.v3.dll;D:\Upside4
\
build\output\bin\Infragistics.UltraChart.Core.v3.dll;D:\Upside4
\build\output\bin
\Infragistics.UltraChart.Data.v3.dll;D:\Upside4
\build\output\bin\Infragistics.Ul
traChart.Render.ActiveImage.v3.dll;D:\Upside4
\build\output\bin\Infragistics.Ultr
aChart.Render.v3.dll;D:\Upside4
\build\output\bin\Infragistics.UltraChart.Resourc
es.v3.dll' is too long or invalid

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: a comment about xml namespace

2003-12-22 Thread Jim Fuller 
Hello Peter,

OK thx for that and apologies if I am coming late to the conversation on
this. I think your email is clear; perhaps it's understandably
Ant-centric with respect to how to namespaces are processed during an
Ant build.

I like the idea that Ant may understand what to do with other external
namespaces like such as proposed with the html: example. And generally
agree with how it is proposed how Ant deals with namespaces it 'knows'
about.

The main point of my example is that instead of continually expanding
the Ant schema to accommodate other meta data that is non-build
specific, to allow non-ant specific namespaced elements/attributes (meta
data) to be allowed inside an ant build document.
 
Perhaps these namespaces can bind to another java class ( as with
binding java functions in XSLT ) which ultimately determine how they are
processed within an Ant context...perhaps not though I can see this
being useful in consistently bringing in external scripting languages to
Ant ( though this is not critical to my argument ). 

A few use cases;

Eventually perhaps there will be a standard method of annotating xml
documents, I use the RDF/Dublin core initiative but perhaps someone
would want to use an XHTML custom module embedded in Ant 
elements. 
There is a real need for versioning Ant xml files

Perhaps Ant will be required during the course of a build sensitive
pieces of information, why not intermix XML Encryption / Signature which
could be expanded when/if securely during the build process ? This could
range to simple username/passwords to embedding public/private keys
etc .

I would simply propose that all namespaces that Ant has no information
on how to handle are by default ignored, with possibly an ant property
and associated command line switch to control how to handle processing
of external namespaces, though I would settle initially for just
ignoring non-ant namespaces. 

XML namespaces should also be able to be applied to xml property
files...though that's another conversation.

It's in this way that we can provide a 'dense' xml document packed with
all the information for a build, at the same time leveraging external
xml vocabularies instead of cooking their own variant every time the
need pops up. At some point we shall see the boundaries between
file-based documents blurring with the usage of storing such XML in XML
DB repositories. XML namespaces will become the true boundary between
xml vocabularies instead of a physical boundary imposed by our current
usage of files and directories. Perhaps this is something to think about
for Ant 2.0.

Cheers, jim

-Original Message-
From: Peter Reilly [mailto:[EMAIL PROTECTED] 
Sent: 22 December 2003 13:53
To: Ant Developers List
Subject: Re: a comment about xml namespace

This is what I (think I) originally proposed, but did
not articulate it correctly.

http://marc.theaimsgroup.com/?l=ant-dev&m=105240500519029&w=2

Peter
Jim Fuller wrote:

>Consider the following;
>
>
>
>   http://www.w3c.org/RDF/";
>xmlns:DC="http://purl.org/RDF/DC/";>
>   RDF:HREF="http://purl.org/metadata/dublin_core_elements"; 
>   DC:Title="namespace build"  
>   DC:Creator="Jim Fuller"
>   DC:Subject="xml namespaces" 
>   DC:Description="Contains Ant artifacts for building" 
>   DC:Publisher="Webcomposite s.r.o." 
>   DC:Format="text/html" 
>   DC:Type="Technical Report" 
>   DC:Language="en" 
>   DC:Date="12/22/2003"/>
>   
>   
>   intermixing of namespaces
>   
>   
>   
>   
>
>
>XML Namespaces was initially created to avoid collision within
documents
>that have multiple xml vocabularies. 
>
>Ant seems to assume by default that all namespaces have something to do
>with build processing...is their any convention planned for having Ant
>ignore specific namespace elements...or more usefully all namespaces
>that have no Ant processing associated with it ?
>
>For instance, the above example maybe generated by a sophisticated XML
>editor that uses Dublin Core and RDF as a method of tracking versions
of
>the build.xml file. This is a simple use case, there are other more
>important use cases involving xml db repositories.
>
>Regards, Jim Fuller
>
>
>---
-
>Jim Fuller Technical Architect  WebComposite s.r.o.
>[EMAIL PROTECTED]/http://www.ruminate.co.uk
>Co-Author ISBN 1861007213 Professional PHP4 XML
>Co-Author ISBN 1861008074 Professional PHP Web Services
>Technical Reviewer 'Beginning XSLT', 'Beginning Databases',
>'XML Antipatterns' and various other xml / web service books
>---
-
>
>
>
>
>
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>

RE: a comment about xml namespace

2003-12-22 Thread Jim Fuller 
>Ant1.7 lets you have any XML you like inside some task. So you could 
>have a  task that required valid XML and took whatever was 
>inside. Or even an  task that required valid RDF

+1 to that,

cheers, Jim Fuller


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]