RE: Blog "Complex build systems need a real language" found

[didge]

I tend to sympathize with the assertion since certainly as my build scripts
have grown in complexity, I have found that I would greatly benefit from the
same structuring functionality commonly found in general purpose scripting
languages that support modularity, reuse and extension, but that are missing
or lacking in Ant.

To be sure, , , , Antlib, namespaces, and
others address many of these issues, and are welcome, powerful and useful
additions to Ant, making it more manegeable than ever before.  However, they
have also come at the cost of unresolved edge cases and ungainly syntax.

I offer as an example what can be done when the basis of a build script is
not a new language, but an existing, general purpose scripting language.  As
an experiment, I attempted to mimic Ant's style and organization as a
language extension of python, i.e. packaged as a python module such that
build scripts are pure python.  Thus, build authors benefit from python's
cross-platform scripting capabilities and mature structuring fuctionality.

The project's admittedly unimaginative working title is 'pant'.

In pant, I ported the main concepts of target, task, project, fileset,
javac, copy, and delete, among others.  Here is what a simple build file
looks like, my hope is that it would be readily comprehensible by Ant users
even if they don't know much python:

# build.py - example pyant build script
import os
from pant import *

project = Project(name = "test", default = "build")

class properties(Target):
classesdir = "build/classes"
srcdir = "src"
jarname = "test.jar"

class compile(Target):
depends = properties
def run(self):
javac(src = properties.srcdir,
destdir = properties.classesdir)

class clean(Target):
depends = properties
def run(self):
delete(dir = properties.classesdir)

class jar(Target):
depends = properties
def run(self):
jar(
destfile = properties.jarname,
basedir = properties.srcname,
destdir = properties.classesdir)

class build(Target):
def run(self):
clean()
compile()
jar()

Notes:
0. Everything in this example is pure python.  There are no modifications to
the language itself.
1. Targets are defined by subclassing pant.Target.
2. The depends class variable of a subclass of Target is a list of other
Target subclasses and is analgous to the depends attribute of Ant's target
element.
3. The body of a Target subclass's run method is analogous to the body of an
Ant target's element content.  Within the run method's body, any legal
python code may be executed and normal scoping rules apply.  After all
dependent targets are run, if any, the run method of a Target is called, if
defined.
4. Targets may be run by simply calling them, i.e. clean().
5. Targets may be defined in another python script and imported using
python's import keyword.
6. Parameters may be passed to Targets when calling them, e.g.
clean(dir="some/dir")

didge

> -Original Message-
> From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 21, 2004 10:09 AM
> To: Ant Developers List
> Subject: RE: Blog "Complex build systems need a real language" found
>
>
> > From: Dominique Devienne [mailto:[EMAIL PROTECTED]
> >
> > > From: Peter Reilly [mailto:[EMAIL PROTECTED]
> > >
> > > According to the last entry, they are currently
> > > using a 45,000 line ant script =-O
> > > which one of the team is reducing to ~700 lines by
> > > using a custom dependency task.
> >
> > I didn't read all the thread completely, but I heartedly
> > agree with Peter that much of the complexity of an Ant
> > script can be removed by developing custom tasks/types.
> >
> > You go to Java to encapsulate complex processes, which are
> > then exposed as much simpler high level tasks hiding all the
> > coding complexities. Using Python in AAP, or Ruby might allow
> > easier/faster programming than Java, but Java can do it all
> > nonetheless, and I personally know Java much better than
> > Python and Ruby ;-)
> >
>
> And with scriptdef, you can write your tasks just the same in any
> supported
> scripting language, if it will fit your needs.
>
> Jose Alberto
>
> -
> 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 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 20:49 ---
I'm generating the Class-Path entry automatically, by:
 - using a fileset 
 - and then using pathconvert,
  with a map entry to strip absolute referencing (is there a better way to 
do this?) to make them relative, 
 - and then passing that resultant string to the attribute tag

Is there a better way to achieve this, without having to resort to keeping an 
up-to-date hard-coded list?   Perhaps one of these steps is what's causing the 
breakage.

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

DO NOT REPLY [Bug 26318] - misspelt is misspelled

[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=26318

misspelt is misspelled





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 18:59 ---
Although I am Canadian and prefer the North American 'spelled', I believe
'spelt' is also correct (and presumably used by Brtis and Aussies). Take a look:

(described under the 3rd meaning of the word spell).
http://dictionary.reference.com/search?q=spelt

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

DO NOT REPLY [Bug 26318] New: - misspelt is misspelled

[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=26318

misspelt is misspelled

   Summary: misspelt is misspelled
   Product: Ant
   Version: 1.6.0
  Platform: All
OS/Version: All
Status: NEW
  Severity: Minor
  Priority: Other
 Component: Optional Tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


apache-ant-1.6.0/src/main/org/apache/tools/ant/UnknownElement.java:+
" - You have misspelt '" + elementName + "'." + lSep

Please change "misspelt" to "misspelled".

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

DO NOT REPLY [Bug 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 18:54 ---
As far as I can tell, Ant's manifest Class-Path wrapping works absolutely fine.
I don't generally use the manifest tag, but even using the jar task with a
manifest attribute to feed it a manifest results in wrapping. If I feed it the
following manifest:
-
Manifest-Version: 1.0
Class-Path: 
 aopalliance-0.1.jar 
 asm-1.4.jar 
 avalon-framework-4.1.3.jar 
 axis-1.1.jar 
 behaviour_xml.jar 
 ccpp-1.0.jar 
 ccpp-ri-1.0.jar 
 cglib2-1.0.jar 
 classworlds-1.0.jar 
 commons-beanutils-1.6.jar 
 commons-collections-2.1.jar 
 commons-dbcp-1.1.jar 
 commons-digester-1.5.jar 
 commons-lang-1.0.1.jar 
 commons-logging-1.0.3.jar 
 core-services.jar 
 core-util.jar 
 core-dbutil.jar 
 cryptix-3.2.0.jar 
 data-access.jar 
 device-descriptor-xml.jar 
 dom4j-1.3.jar 
 ehcache-0.7.jar 
 glue-std-3.2.3.jar 
 hibernate2-2.1.1.jar 
 jad-manifest-rules-xml.jar 
 jakarta-oro-2.0.8.jar 
 jato-beta5.jar 
 jaxen-1.0-FCS-full.jar 
 jaxp-api-1.2.3.jar 
 jaxrpc-api-1.0.jar 
 jdom-b8.jar 
 jena-1.4.0.jar 
 jstl-1.0.4.jar 
 junit-3.8.1.jar 
 log4j-1.2.8.jar 
 log4j-properties.jar 
 odmg-3.0.jar 
 oscore-tira-1.1.0.jar 
 osuser-tira-1.1.0.jar 
 osuser-tira-jdbc-1.0.0.jar 
 osworkflow-tira-1.1.0.jar 
 packaging.jar 
 png-sixlegs-1.2.3.jar 
 provisioning.jar 
 qa-util.jar 
 quartz-1.0.2.jar 
 rdffilter-1.0.0.jar 
 saaj-1.1.jar 
 saxpath-1.0-fcs.jar 
 spring-1.0M4.jar 
 standard-1.0.4.jar 
 tapestry-3.0-beta-3-post.jar 
 tapestry-contrib-3.0-beta-3-post.jar 
 tira-classfile-1.0.2.jar 
 wsdl4j-20030609.jar 
 xbean-1.0.0.jar 
- 
Ant then puts the following in the jar file:
-
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.0
Created-By: 1.4.2_01-b06 (Sun Microsystems Inc.)
Class-Path: aopalliance-0.1.jar asm-1.4.jar avalon-framework-4.1.3.jar
  axis-1.1.jar behaviour_xml.jar ccpp-1.0.jar ccpp-ri-1.0.jar cglib2-1
 .0.jar classworlds-1.0.jar commons-beanutils-1.6.jar commons-collecti
 ons-2.1.jar commons-dbcp-1.1.jar commons-digester-1.5.jar commons-lan
 g-1.0.1.jar commons-logging-1.0.3.jar core-services.jar core-util.jar
  core-dbutil.jar cryptix-3.2.0.jar data-access.jar device-descriptor-
 xml.jar dom4j-1.3.jar ehcache-0.7.jar glue-std-3.2.3.jar hibernate2-2
 .1.1.jar jad-manifest-rules-xml.jar jakarta-oro-2.0.8.jar jato-beta5.
 jar jaxen-1.0-FCS-full.jar jaxp-api-1.2.3.jar jaxrpc-api-1.0.jar jdom
 -b8.jar jena-1.4.0.jar jstl-1.0.4.jar junit-3.8.1.jar log4j-1.2.8.jar
  log4j-properties.jar odmg-3.0.jar oscore-tira-1.1.0.jar osuser-tira-
 1.1.0.jar osuser-tira-jdbc-1.0.0.jar osworkflow-tira-1.1.0.jar packag
 ing.jar png-sixlegs-1.2.3.jar provisioning.jar qa-util.jar quartz-1.0
 .2.jar rdffilter-1.0.0.jar saaj-1.1.jar saxpath-1.0-fcs.jar spring-1.
 0M4.jar standard-1.0.4.jar tapestry-3.0-beta-3-post.jar tapestry-cont
 rib-3.0-beta-3-post.jar tira-classfile-1.0.2.jar wsdl4j-20030609.jar 
 xbean-1.0.0.jar 
-

And I have had no issues with this in either JDK 1.3.1, JDK 1.4.0, 1.4.1, or 
1.4.2.

May I suggest that something else is the problem, maybe line termination, etc?

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

Re: [Fwd: Ant bug# 26300]

[Antoine Lévy-Lambert]

Peter Reilly wrote:


Subject:
Ant bug# 26300
From:
Adam Levine <[EMAIL PROTECTED]>
Date:
Wed, 21 Jan 2004 10:04:24 -0600
To:
[EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
I've read the noted documentation on the manifest format.  The problem 
is I'm not generating this manigest - ant is.  And i'm getting class 
not found errors from the results.

If i explode the jar, edit the manifest by hand to put it all on one 
line, even tho that's against the spec, repackage it and run it, it 
works fine.

So, would you not think this is a problem with the generated manifest, 
the one I have no control over?

this is happening on all machines tested on thus far (solaris, 
windows) and diff't jdks.. 1.3, 1.4..  and v 1.5 and 1.6 of Ant.

Where would you suggest I take this issue now?  to sun?
thanks
_
Rethink your business approach for the new year with the helpful tips 
here. http://special.msn.com/bcentral/prep04.armx



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I think we should check what Adam Levine is writing - that is that jars 
made with ant which have a folded class path in the manifest are not usable.

The issue should be certainly taken to Sun if it is confirmed and 
against the Java spec.

Meanwhile we could add in ant the possibility of not folding classpaths 
in manifest, even if it is against the spec, so that users can live.

Antoine

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

RE: Blog "Complex build systems need a real language" found

[Jose Alberto Fernandez]

> From: Dominique Devienne [mailto:[EMAIL PROTECTED] 
> 
> > From: Peter Reilly [mailto:[EMAIL PROTECTED]
> > 
> > According to the last entry, they are currently
> > using a 45,000 line ant script =-O
> > which one of the team is reducing to ~700 lines by
> > using a custom dependency task.
> 
> I didn't read all the thread completely, but I heartedly
> agree with Peter that much of the complexity of an Ant
> script can be removed by developing custom tasks/types.
> 
> You go to Java to encapsulate complex processes, which are
> then exposed as much simpler high level tasks hiding all the 
> coding complexities. Using Python in AAP, or Ruby might allow 
> easier/faster programming than Java, but Java can do it all 
> nonetheless, and I personally know Java much better than 
> Python and Ruby ;-)
> 

And with scriptdef, you can write your tasks just the same in any
supported
scripting language, if it will fit your needs.

Jose Alberto

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

DO NOT REPLY [Bug 26299] - Using sshexec to run ant remotely - Using ant to run sshexec

[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=26299

Using sshexec to run ant remotely - Using ant to run sshexec

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WORKSFORME



--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 18:06 ---
This is not a bug in the sshexec task. Please take this to the users list for 
help.

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

DO NOT REPLY [Bug 26310] - Ant 1.6 and XDoclet 1.2 "destDir attribute must be present." error

[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=26310

Ant 1.6 and XDoclet 1.2 "destDir attribute must be present." error





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 17:52 ---
I can confirm that this is a problem
however for my simple class the problem also exists in ant 1.5.2
The class is:
package task;
import org.apache.tools.ant.Task;
public class ShowDestDir extends Task {
private String destDir;
public void setDestDir(String n) {
this.destDir = n;
}
public void execute() {
log("destdir is " + destDir);
destDir = null;
}
}

The build file is:

  
  

  


The result for 1.6.0 and 1.5.2 is:
Buildfile: xdoc.xml

go:
[showdestdir] destdir is hello

go:
[showdestdir] destdir is null

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

DO NOT REPLY [Bug 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 17:02 ---
I've read the noted documentation on the manifest format.  The problem is I'm 
not generating this manifest - ant is.  And i'm getting class not found errors 
from the results.

If i explode the jar, edit the manifest by hand to put it all on one line, even 
tho that's against the spec, repackage it and run it, it works fine.


So, would you not think this is a problem with the generated manifest, the one 
I have no control over?


this is happening on all machines tested on thus far (solaris, windows) and 
diff't jdks.. 1.3, 1.4..  and v 1.5 and 1.6 of Ant.  and now 1.7Alpha

Where would you suggest I take this issue now?  to sun?


thanks

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

[Fwd: Ant bug# 26300]

[Peter Reilly]

--- Begin Message ---
I've read the noted documentation on the manifest format.  The problem is 
I'm not generating this manigest - ant is.  And i'm getting class not found 
errors from the results.

If i explode the jar, edit the manifest by hand to put it all on one line, 
even tho that's against the spec, repackage it and run it, it works fine.

So, would you not think this is a problem with the generated manifest, the 
one I have no control over?

this is happening on all machines tested on thus far (solaris, windows) and 
diff't jdks.. 1.3, 1.4..  and v 1.5 and 1.6 of Ant.

Where would you suggest I take this issue now?  to sun?
thanks
_
Rethink your business approach for the new year with the helpful tips here. 
http://special.msn.com/bcentral/prep04.armx



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

DO NOT REPLY [Bug 26312] - concat changes binary files

[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=26312

concat changes binary files





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 16:04 ---
Yep there is a problem with encoding. By default concat
uses an output and inputstream reader using the default encoding
(which I think is UTF-8) this does not work too good with
binary files.

Try using:


  
  


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

DO NOT REPLY [Bug 25345] - jspc tag broken with new version of jasper

[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=25345

jspc tag broken with new version of jasper





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 15:58 ---
The Tomcat team have added back the -v setter, so future versions may work. I
say may as there are other changes that can break things.

Therefore I intend to document that the Ant-supplied version of  is only
for the 4.x version of tomcat; for later versions you should use Tomcat's own
task. This will make life a lot simpler.

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

DO NOT REPLY [Bug 26242] - Changes in jasper command line break ant's task

[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=26242

Changes in jasper command line break ant's  task

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 15:45 ---
I've added back the setter.

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

DO NOT REPLY [Bug 26312] New: - concat changes binary files

[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=26312

concat changes binary files

   Summary: concat changes binary files
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Hello,
I am attempting to concat a shell script and a tgz file but here is the 
problem, the gzip file is corrupted after the concat (I have tested the gz file 
from before the concat it is fine. In particular when I do a od -x I see things 
like an 8f -> 3f ... (many thousands like that) I am wondering if it may have 
to do w/ the encoding? 
Here is my concat block:

  
 
 
  

Am I missing something?

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

RE: FYI: Blog "Complex build systems need a real language" found

[Dominique Devienne]

> From: Peter Reilly [mailto:[EMAIL PROTECTED]
> 
> According to the last entry, they are currently
> using a 45,000 line ant script =-O
> which one of the team is reducing to ~700 lines by
> using a custom dependency task.

I didn't read all the thread completely, but I heartedly
agree with Peter that much of the complexity of an Ant
script can be removed by developing custom tasks/types.

You go to Java to encapsulate complex processes, which are
then exposed as much simpler high level tasks hiding all the
coding complexities. Using Python in AAP, or Ruby might allow
easier/faster programming than Java, but Java can do it all
nonetheless, and I personally know Java much better than
Python and Ruby ;-)

This is the approach we've taken, and it's working out pretty
well. It's not perfect, and much cruder than Maven for example,
while having some of the same characteristics, but fits our
needs and evolves with our needs. I actually enjoy coding Ant
tasks, and gradually remove all complex stuff from our build
files!

Anyways, this is just one more data point. --DD

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

DO NOT REPLY [Bug 26310] New: - Ant 1.6 and XDoclet 1.2 "destDir attribute must be present." error

[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=26310

Ant 1.6 and XDoclet 1.2 "destDir attribute must be present." error

   Summary: Ant 1.6 and XDoclet 1.2 "destDir attribute must be
present." error
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Build Process
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When using ant 1.6 and XDoclet 1.2 I get an error when I try to execute the 
same target twice, within one session.

When executing the target twice via the  target I don't get an error?

To illustrate I have made the following small buildfile (testbuild.xml):


Test ant script to verify xdoclet error.
!You must have the XDoclet jars in the ${basedir}/lib directory!












   







!Please note that you must have the XDoclet jars in the ${basedir}/lib.!

Testrun 1:

C:\server\java>ant -f testbuild.xml
Buildfile: testbuild.xml

default:

BUILD SUCCESSFUL
Total time: 3 seconds

Testrun 2:

C:\server\java>ant -f testbuild.xml default default
Buildfile: testbuild.xml

default:

default:
   [doclet] C:\server\java\testbuild.xml:14: destDir attribute must be present.
   [doclet] at xdoclet.DocletTask.validateOptions(DocletTask.java:491)
   [doclet] at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:94)
   [doclet] at org.apache.tools.ant.Task.perform(Task.java:401)
   [doclet] at org.apache.tools.ant.Target.execute(Target.java:338)
   [doclet] at org.apache.tools.ant.Target.performTasks(Target.java:365)
   [doclet] at org.apache.tools.ant.Project.executeTarget(Project.java:1237)
   [doclet] at org.apache.tools.ant.Project.executeTargets
(Project.java:1094)
   [doclet] at org.apache.tools.ant.Main.runBuild(Main.java:669)
   [doclet] at org.apache.tools.ant.Main.startAnt(Main.java:220)
   [doclet] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:215)
   [doclet] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:90)

BUILD FAILED
C:\server\java\testbuild.xml:14: Unexpected error

Total time: 4 seconds

Testrun 3:

C:\server\java>ant -f testbuild.xml default testAntCall
Buildfile: testbuild.xml

default:

testAntCall:

default:

BUILD SUCCESSFUL
Total time: 4 seconds

I have not investigated if the "dependency" error is general, ie. not just 
related to xdoclet?!

My reason for beliving it to be an Ant bug, opposed to a XDoclet bug, is that I 
can't reproduce the errors with Ant1.5.2 or Ant1.5.4

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

DO NOT REPLY [Bug 26308] - fail on verify errors in borland deployment tool

[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=26308

fail on verify errors in borland deployment tool 





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 13:11 ---
Created an attachment (id=10042)
patch to org/apache/tools/ant/taskdefs/optional/ejb/BorlandDeploymentTool.java 
file

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

DO NOT REPLY [Bug 26308] New: - fail on verify errors in borland deployment tool

[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=26308

fail on verify errors in borland deployment tool 

   Summary: fail on verify errors in borland deployment tool
   Product: Ant
   Version: 1.6.0
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Optional Tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


In 1.6.0 and previous releases of ANT the borland deployment tool does not 
abort the build when errors in the verify procedure are detected. For most 
applications it might be reasonable to abort the procedure, if the verification 
procedure fails. A deployment of EJB-jars which have not passed verification to 
a Borland AppServer will be surely unsuccessful.

The changes to create this functionality are minimal. An additional 
attribute "failOnVerifyError" is added to the 
org/apache/tools/ant/taskdefs/optional/ejb/BorlandDeploymentTool.java file with 
appropriate handling of the attribute: if it is set to true, the javaTask or 
execTask which execute the verification procedure have the failonerror 
attribute set. For backwards compatibility, this attribute is false on default.

The changes done to the verifyBorlandJarV4 method are tested, those done to the
verifyBorlandJarV5 method are UNTESTED. This is because we do not have such a 
version of the Borland AppServer available.

I attach a diff created between the source file BorlandDeploymentTool.java in 
the 1.6.0 version to a solution created by us. This simply adds the attribute 
and its handling to the class. The diff is suitable as a patch file.

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

cvs commit: ant WHATSNEW

[antoine]

antoine 2004/01/21 04:55:53

  Modified:docs/manual/OptionalTasks clearcase.html
   docs/manual tasksoverview.html
   src/main/org/apache/tools/ant/taskdefs defaults.properties
   src/main/org/apache/tools/ant/taskdefs/optional/clearcase
CCCheckin.java CCCheckout.java CCLock.java
CCMkbl.java CCMklabel.java CCMklbtype.java
CCUnCheckout.java CCUnlock.java CCUpdate.java
ClearCase.java CCRmtype.java
   .WHATSNEW
  Added:   src/main/org/apache/tools/ant/taskdefs/optional/clearcase
CCMkattr.java CCMkdir.java CCMkelem.java
  Log:
  - Added an extra option to 'failonerr' to each ClearCase task/command.
  - Extended the functionality of cccheckout. It can check (notco) to see if
the desired element is already checked out to the current view. Thus it
won't attempt to check it out again.
  - Added three new ClearCase commands: ccmkattr, ccmkdir, ccmkelem
  - Checkstyle
  PR: 26253
  Submitted by: Sean Egan (sean at cm-logic dot com)
  
  Revision  ChangesPath
  1.9   +289 -13   ant/docs/manual/OptionalTasks/clearcase.html
  
  
http://cvs.apache.org/viewcvs/ant/docs/manual/OptionalTasks/clearcase.html.diff?r1=1.8&r2=1.9
  
  
  1.26  +1 -1  ant/docs/manual/tasksoverview.html
  
  
http://cvs.apache.org/viewcvs/ant/docs/manual/tasksoverview.html.diff?r1=1.25&r2=1.26
  
  
  1.155 +3 -0  
ant/src/main/org/apache/tools/ant/taskdefs/defaults.properties
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/defaults.properties.diff?r1=1.154&r2=1.155
  
  
  1.11  +30 -20
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCCheckin.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCCheckin.java.diff?r1=1.10&r2=1.11
  
  
  1.12  +104 -46   
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCCheckout.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCCheckout.java.diff?r1=1.11&r2=1.12
  
  
  1.5   +70 -49
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCLock.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCLock.java.diff?r1=1.4&r2=1.5
  
  
  1.5   +38 -33
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkbl.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkbl.java.diff?r1=1.4&r2=1.5
  
  
  1.7   +38 -39
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMklabel.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMklabel.java.diff?r1=1.6&r2=1.7
  
  
  1.7   +42 -41
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMklbtype.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMklbtype.java.diff?r1=1.6&r2=1.7
  
  
  1.11  +17 -7 
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUnCheckout.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUnCheckout.java.diff?r1=1.10&r2=1.11
  
  
  1.5   +57 -34
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUnlock.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUnlock.java.diff?r1=1.4&r2=1.5
  
  
  1.13  +32 -21
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUpdate.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCUpdate.java.diff?r1=1.12&r2=1.13
  
  
  1.15  +85 -14
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/ClearCase.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/ClearCase.java.diff?r1=1.14&r2=1.15
  
  
  1.7   +36 -33
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCRmtype.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCRmtype.java.diff?r1=1.6&r2=1.7
  
  
  1.1  
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkattr.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkattr.java?rev=1.1
  
  
  1.1  
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkdir.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkdir.java?rev=1.1
  
  
  1.1  
ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkelem.java
  
  
http://cvs.apache.org/viewcvs/ant/src/main/org/apache/tools/ant/taskdefs/optional/clearcase/CCMkelem.jav

RE: Help creating a MatchingTask

[Jim Fuller]

Try something like this (


import java.io.File;
import java.io.IOException;
import java.util.Enumeration;
import java.util.Vector;

import org.apache.tools.ant.BuildException;
import org.apache.tools.ant.DirectoryScanner;
import org.apache.tools.ant.Task;
import org.apache.tools.ant.Project;
import org.apache.tools.ant.types.FileSet;



public class AntFileSetTest extends Task{
private Vector filesets = new Vector();


public void addFileset(FileSet fileset) {
filesets.add(fileset);
}

public void execute(){

   log("executing Xindice Ant Task");



int fileCount = 0;
int successCount = 0;

Enumeration enum = filesets.elements();

while(enum.hasMoreElements()){

FileSet fileset = (FileSet) enum.nextElement();
DirectoryScanner ds = fileset.getDirectoryScanner(getProject());
String[] files = ds.getIncludedFiles();

for(int i=0; i
   




The output would be a the 'file processed' message displaying per
included file.

Gl, Jim Fuller

> -Original Message-
> From: Mark McKay [mailto:[EMAIL PROTECTED] 
> Sent: 21 January 2004 09:43
> To: Ant Developers List
> Subject: Re: Help creating a MatchingTask
> 
> 
> Conor MacNeill wrote:
> 
> >Mark,
> >
> >Peter and Jan look to have figured out your compile issue. I would 
> >recommend,
> >however, that you reconsider using MatchingTask. It was the 
> way early Ant 
> >tasks were implements but it is not ideal. A better approach 
> would be to use 
> >an addFileset(FileSet fs) method and process that fileset 
> (or multiple 
> >filesets) in your execute method.
> >
> >Your task then has an explicit fileset
> >
> >
> >  
> >
> >
> >It's a cleaner approach overall.
> >
> >Conor
> >  
> >
> 
> Thanks for all the help offered so far.  I've modified my code and 
> getting better results, but am still error prone. 
> 
> I can build my ant task now; however, when I try to use it I get:
> 
> build.xml [18] The  data type doesn't support the nested 
> "includes" element.
> BUILD FAILED
> 
> I'm assuming this means that 'fileset' is seen as an ordinary nested 
> element, and not the special FileSet facility provided by Ant.
> 
> I've included my task and code.  Any further help would be great!
> 
> Mark McKay
> 
> =
> 
> 
> 
> 
>   classname="com.kitfox.anttask.MyAntTask"
>  classpath="${ant.project.name}.jar"/>
> 
> 
> >
> 
> 
> 
> 
> 
> public class MyAntTask extends MatchingTask {
>
> FileSet sourceFiles;
>
> /** Creates a new instance of MyAntTask */
> public MyAntTask() {
> }
> 
> public void addFileset(FileSet fs)
> {
> sourceFiles = fs;
> }
> 
> public void execute() throws BuildException
> {
> log("Walking tree");
>
> DirectoryScanner scanner = 
> sourceFiles.getDirectoryScanner(getProject());
>
> scanner.scan();
>
> String[] files = scanner.getIncludedFiles();
> for (int i = 0; i < files.length; i++) {
> //System.out.println(files[i]);
> log(files[i]);
> }
>
> }
>
> }
> 
> 
> 
> -
> 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 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 10:46 ---
I am afraid that I have to mark this as invalid.
The class-path entry is valid.

I have just tried in my project with a similar manifest:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7alpha
Created-By: Blackdown-1.4.2-rc1 (Blackdown Java-Linux Team)
Main-Class: com.corvil.probesim.ProbeSim
Class-Path: /usr/local/preilly/src/probesim/lib/dom4j-full.jar /usr/lo
 cal/preilly/src/probesim/lib/log4j.jar


And this works fine.

Please see: http://java.sun.com/products/jdk/1.2/docs/guide/jar/manifest.html

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

Re: FYI: Blog "Complex build systems need a real language" found

[Peter Reilly]

According to the last entry, they are currently
using a 45,000 line ant script =-O
which one of the team is reducing to ~700 lines by
using a custom dependency task.
Peter
[EMAIL PROTECTED] wrote:
FYI.
Jan

http://www.theserverside.com/news/thread.jsp?thread_id=23426
Opinion: Complex build systems need a real language
Posted By: Dion Almaer on January 20, 2004 @ 11:13 AM
Jon Tirsen talks about a Java project that he was working on that had a very
complicated build system. He started off with Ant, even writing a tool that
took his project information and generated the ant build, and then tried
Maven. 

He ended up realising that for this kind of build system he really wanted a
real language. He happened to choose Ruby as the implementation of choice,
but others could have be chosen. 

Using Ruby to build Java systems [1]
-
Opinion: Complex build systems need a real language
Posted By: graham o'regan on January 20, 2004 @ 01:51 PM in response to
Message #107651 1 replies in this thread
Would you say that part of the problem is not the complexity of the build
script produced (afterall, only the Ant has to read it), but the complexity
of the XSLT which does have to be maintained? I read an interesting article
on Martin Fowler's site recently where he claimed to be using Ruby in place
of XSLT too. 

-
Ant == poop
Posted By: Dave C on January 20, 2004 @ 02:58 PM in response to Message
#107670 0 replies in this thread
I find it baffling that people use the weakest scripting language ever
concieved to maintain highly complex systems using an advanced programming
language. 

If anyone is unhappy with ant's complete inflexibility and backwards way of
approaching everyting (not to mention complete mis-use of XML), check out
AAP [2], which is a python-based build system. The rib is that you can use
it's builtin facilities (like make or ant), but you can easily embed real
python code wherever you need it for things that are complex. 

[1]
http://blogs.codehaus.org/people/jutopia/archives/000562_using_ruby_to_build
_java_systems.html
[2] http://www.a-a-p.org/
-
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: [VOTE] Bug Tracking System

[Steve Loughran]

Gus Heck wrote:
My non-non commiter vote:
[ ] +1 Bugzilla sucks - go to Jira
[x] -1 BugZilla rocks - if it ain't broke, don't fix it.
 

Oh, this is good.
I agree with you; bug entry is critical.
When we used Rational ClearQuest, I once spent 30 minutes filling in 
some inordinately complex form describing a hard to replicate problem, 
with all the test data, etc.

Then I hit submit, and got
"session timed out"
needless to say, I was not happy - we moved to bugzilla shortly 
thereafter, showing that usability comes above seamless integration with 
SCM tools.

Doesn't it figure. I read a similar commons thread, and wrote a long 
email about why I think bugzilla is friendlier to the novice user than 
both JIRA and Scarab then I come here and see the same issue. Apparently 
I should have wrote it here... That is what I get for reading the other 
mail first :)  One of the biggest strengths of Ant (and any OSS project) 
is the user feedback from both experienced and novice users... Here is 
most of what I posted (minus a question that has already been answered 
there), which I think we should consider here too. (I don't beleive it 
is likely to have hit the archives yet or I would link it).

I sometimes think that there is an aspect of the ASF bug tracking 
systems that gets forgotten... How easy it is to learn to use them. As a 
contributer to Ant, and an operator of my own bugzilla, I have been very 
satisfied with bugzilla in this repsect. The first time I ever used 
bugzilla I had no trouble figuring out how to do a query, or fill in a 
bug form. The query form seemed a bit disorganized, but there were lots 
of explanatory links and with a little looking I found the submit button 
without too much trouble. I have not once had to explain details of how 
to use bugzilla to users of my bugzilla, nor have I recieved complaints 
about it. Some of the users are introductory programming students who 
have never used any bug tracker before.

In contrast, I don't like scarab. I have several times found issues in 
OJB (relating to JDO implementations), but they use Scarab. Scarab I 
regret to say is quite difficult to use (at least if you don't already 
know how to use it, or maybe only if you are used to using bugzilla, I 
don't know which). It entirely fails to document itself clearly. 
Bugzilla has explanitory links all over it's bug creation and query 
forms, which is something I beleive to be critical to a bug tracking 
system that will be accessed by users who are not already familiar with 
it. I have several times tried to use Scarab, and each time it has 
failed, or it has eaten all my plain text formatting by coalescing all 
the whtiespace (that makes stack traces really fun to read), or whatnot. 
I am sure it is user error on my part, but so far I really haven't had 
time to find out where to read up on how to properly use Scarab. Another 
annoyance is that after you sign up for an account with scarab it tells 
you you must "request" membership in a project, which seems to imply 
that you might be rejected. Really not a very welcoming start.

The systems used at apache should (IMHO) be transparent, user friendly 
and self explanitory. If they want users to report bugs in their 
software, it should be easy to learn the system. The current result with 
Scarab and me, is if I see that a project uses scarab, I only report 
bugs on their mailing list. I suppose if I decide I want to become a 
direct contriubuter to a project that uses Scarab, or I have some free 
time and think of it, I will take the time do the research to figure out 
how to enter bugs properly in Scarab.

So I wrote the above mostly based on the gut reaction, oh no not another 
bug system to fight with...

After looking at Jelly's JIRA as linked from their project pages 
(http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10012), it 
is clear that there are some nice features, it looks nicer than both 
bugzilla and scarab and is and friendlier than scarab, but I do see one 
major usability glitch. Nowhere did I see a link for Entering a bug. 
This is the main reason people come to a bug database. How can there not 
be a link on the front page for it!?!? I have a strong suspeicion that 
such a link would have appeared had I created an account and logged in, 
but there was no link for that either... just a log in link. (now I 
think it is vairly likely if I followed the log in link it would 
eventually get me to an account creation link, but) Only my existing 
knowledge of how web apps and bug trackers tend to work tells me that. 
Nothing on the page helps you enter a bug. (unless I am blind or stupid, 
both of which happen occasionally). It could use more explanitory links 
too, but at least there was a help link (once I saw the really tiny 
bubble thing in the upper right) that led to a detailed manual (though 
that manual didn't have a "Enter a bug" section). I didn't have time to 
browse the manual deeply, but this is still infer

RE: Help creating a MatchingTask

[Jan . Materne]

Maybe the second tutorial (not finished yet) would help you.
Tutorial on [1] and sources on [2]. Especially the part about filesets [3].

Jan

[1]
http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/tutorial-tasks-
filesets-properties.html?content-type=text%2Fplain
[2]
http://cvs.apache.org/viewcvs.cgi/ant/docs/manual/tutorial-tasks-filesets-pr
operties.zip?only_with_tag=HEAD
[3]
http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/docs/manual/tutorial-tasks-
filesets-properties.html?content-type=text%2Fplain#filesets

> -Original Message-
> From: Mark McKay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 21, 2004 10:43 AM
> To: Ant Developers List
> Subject: Re: Help creating a MatchingTask
> 
> 
> Conor MacNeill wrote:
> 
> >Mark,
> >
> >Peter and Jan look to have figured out your compile issue. I 
> would recommend, 
> >however, that you reconsider using MatchingTask. It was the 
> way early Ant 
> >tasks were implements but it is not ideal. A better approach 
> would be to use 
> >an addFileset(FileSet fs) method and process that fileset 
> (or multiple 
> >filesets) in your execute method.
> >
> >Your task then has an explicit fileset
> >
> >
> >  
> >
> >
> >It's a cleaner approach overall.
> >
> >Conor
> >  
> >
> 
> Thanks for all the help offered so far.  I've modified my code and 
> getting better results, but am still error prone. 
> 
> I can build my ant task now; however, when I try to use it I get:
> 
> build.xml [18] The  data type doesn't support the nested 
> "includes" element.
> BUILD FAILED
> 
> I'm assuming this means that 'fileset' is seen as an ordinary nested 
> element, and not the special FileSet facility provided by Ant.
> 
> I've included my task and code.  Any further help would be great!
> 
> Mark McKay
> 
> =
> 
> 
> 
> 
>   classname="com.kitfox.anttask.MyAntTask"
>  classpath="${ant.project.name}.jar"/>
> 
> 
> >
> 
> 
> 
> 
> 
> public class MyAntTask extends MatchingTask {
>
> FileSet sourceFiles;
>
> /** Creates a new instance of MyAntTask */
> public MyAntTask() {
> }
> 
> public void addFileset(FileSet fs)
> {
> sourceFiles = fs;
> }
> 
> public void execute() throws BuildException
> {
> log("Walking tree");
>
> DirectoryScanner scanner = 
> sourceFiles.getDirectoryScanner(getProject());
>
> scanner.scan();
>
> String[] files = scanner.getIncludedFiles();
> for (int i = 0; i < files.length; i++) {
> //System.out.println(files[i]);
> log(files[i]);
> }
>
> }
>
> }
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Re: Help creating a MatchingTask

[Mark McKay]

Conor MacNeill wrote:
Mark,
Peter and Jan look to have figured out your compile issue. I would recommend, 
however, that you reconsider using MatchingTask. It was the way early Ant 
tasks were implements but it is not ideal. A better approach would be to use 
an addFileset(FileSet fs) method and process that fileset (or multiple 
filesets) in your execute method.

Your task then has an explicit fileset

 

It's a cleaner approach overall.
Conor
 

Thanks for all the help offered so far.  I've modified my code and 
getting better results, but am still error prone. 

I can build my ant task now; however, when I try to use it I get:
   build.xml [18] The  data type doesn't support the nested 
"includes" element.
   BUILD FAILED

I'm assuming this means that 'fileset' is seen as an ordinary nested 
element, and not the special FileSet facility provided by Ant.

I've included my task and code.  Any further help would be great!
Mark McKay
=

   
   
   
   
   >
   
   
   
public class MyAntTask extends MatchingTask {
  
   FileSet sourceFiles;
  
   /** Creates a new instance of MyAntTask */
   public MyAntTask() {
   }

   public void addFileset(FileSet fs)
   {
   sourceFiles = fs;
   }
   public void execute() throws BuildException
   {
   log("Walking tree");
  
   DirectoryScanner scanner = 
sourceFiles.getDirectoryScanner(getProject());
  
   scanner.scan();
  
   String[] files = scanner.getIncludedFiles();
   for (int i = 0; i < files.length; i++) {
   //System.out.println(files[i]);
   log(files[i]);
   }
  
   }
  
}


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

FYI: Blog "Complex build systems need a real language" found

[Jan . Materne]

FYI.

Jan



http://www.theserverside.com/news/thread.jsp?thread_id=23426

Opinion: Complex build systems need a real language
Posted By: Dion Almaer on January 20, 2004 @ 11:13 AM
Jon Tirsen talks about a Java project that he was working on that had a very
complicated build system. He started off with Ant, even writing a tool that
took his project information and generated the ant build, and then tried
Maven. 

He ended up realising that for this kind of build system he really wanted a
real language. He happened to choose Ruby as the implementation of choice,
but others could have be chosen. 

Using Ruby to build Java systems [1]

-

Opinion: Complex build systems need a real language
Posted By: graham o'regan on January 20, 2004 @ 01:51 PM in response to
Message #107651 1 replies in this thread
Would you say that part of the problem is not the complexity of the build
script produced (afterall, only the Ant has to read it), but the complexity
of the XSLT which does have to be maintained? I read an interesting article
on Martin Fowler's site recently where he claimed to be using Ruby in place
of XSLT too. 

-

Ant == poop
Posted By: Dave C on January 20, 2004 @ 02:58 PM in response to Message
#107670 0 replies in this thread
I find it baffling that people use the weakest scripting language ever
concieved to maintain highly complex systems using an advanced programming
language. 

If anyone is unhappy with ant's complete inflexibility and backwards way of
approaching everyting (not to mention complete mis-use of XML), check out
AAP [2], which is a python-based build system. The rib is that you can use
it's builtin facilities (like make or ant), but you can easily embed real
python code wherever you need it for things that are complex. 


[1]
http://blogs.codehaus.org/people/jutopia/archives/000562_using_ruby_to_build
_java_systems.html
[2] http://www.a-a-p.org/

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

Re: Help creating a MatchingTask

[Conor MacNeill]

On Wed, 21 Jan 2004 07:44 pm, Mark McKay wrote:
> I'm trying to create a custom ant task that I can call from my build
> scripts.  Right now I'm just trying to figure out how to write a task
> that can accept a fileset and iterate through all valid files.  My best
> guess so far is below.
>

Mark,

Peter and Jan look to have figured out your compile issue. I would recommend, 
however, that you reconsider using MatchingTask. It was the way early Ant 
tasks were implements but it is not ideal. A better approach would be to use 
an addFileset(FileSet fs) method and process that fileset (or multiple 
filesets) in your execute method.

Your task then has an explicit fileset


  


It's a cleaner approach overall.

Conor



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

Re: Help creating a MatchingTask

[Peter Reilly]

Mark McKay wrote:
I'm trying to create a custom ant task that I can call from my build 
scripts.  Right now I'm just trying to figure out how to write a task 
that can accept a fileset and iterate through all valid files.  My 
best guess so far is below.

Unfortunately, this is giving me errors that I have not encountered in 
Java before.  What does 'cannot be applied to ()' mean?  Could anyone 
suggest what I could do to fix my program?

Thanks.
Mark McKay
=
Error:
com/kitfox/anttask/MyAntTask.java [26:1] 
getDirectoryScanner(org.apache.tools.ant.Project) in 
org.apache.tools.ant.types.AbstractFileSet cannot be applied to ()
   DirectoryScanner scanner = fs.getDirectoryScanner();
You need to do:
 DirectoryScanner scanner = fs.getDirectoryScanner(getProject());
Peter
^
1 error
Errors compiling MyAntTask.
=
package com.kitfox.anttask;
import org.apache.tools.ant.*;
import org.apache.tools.ant.taskdefs.*;
import org.apache.tools.ant.types.*;
/**
*
* @author  kitfox
*/
public class MyAntTask extends MatchingTask {
 /** Creates a new instance of MyAntTask */
   public MyAntTask() {
   }
 public void execute() throws BuildException
   {
   FileSet fs = getImplicitFileSet();
   DirectoryScanner scanner = fs.getDirectoryScanner();
 scanner.scan();
 String[] files = scanner.getIncludedFiles();
   for (int i = 0; i < files.length; i++) {
   System.out.println(files[i]);
   }
   }
  }

-
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: Help creating a MatchingTask

[Jan . Materne]

Means that there is no method with your signature. Provided method is:
public DirectoryScanner getDirectoryScanner(Project p)

I recommend downloading the src-distro and looking into the sources while
programming
tasks.


Jan


> -Original Message-
> From: Mark McKay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 21, 2004 9:45 AM
> To: [EMAIL PROTECTED]
> Subject: Help creating a MatchingTask
> 
> 
> 
> I'm trying to create a custom ant task that I can call from my build 
> scripts.  Right now I'm just trying to figure out how to write a task 
> that can accept a fileset and iterate through all valid 
> files.  My best 
> guess so far is below.
> 
> Unfortunately, this is giving me errors that I have not 
> encountered in 
> Java before.  What does 'cannot be applied to ()' mean?  Could anyone 
> suggest what I could do to fix my program?
> 
> Thanks.
> 
> Mark McKay
> 
> 
> =
> 
> Error:
> 
> com/kitfox/anttask/MyAntTask.java [26:1] 
> getDirectoryScanner(org.apache.tools.ant.Project) in 
> org.apache.tools.ant.types.AbstractFileSet cannot be applied to ()
> DirectoryScanner scanner = fs.getDirectoryScanner();
>  ^
> 1 error
> Errors compiling MyAntTask.
> 
> 
> =
> 
> 
> package com.kitfox.anttask;
> 
> import org.apache.tools.ant.*;
> import org.apache.tools.ant.taskdefs.*;
> import org.apache.tools.ant.types.*;
> 
> /**
>  *
>  * @author  kitfox
>  */
> public class MyAntTask extends MatchingTask {
>
> /** Creates a new instance of MyAntTask */
> public MyAntTask() {
> }
>
> public void execute() throws BuildException
> {
> FileSet fs = getImplicitFileSet();
> DirectoryScanner scanner = fs.getDirectoryScanner();
>
> scanner.scan();
>
> String[] files = scanner.getIncludedFiles();
> for (int i = 0; i < files.length; i++) {
> System.out.println(files[i]);
> }
> }
>
> }
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Help creating a MatchingTask

[Mark McKay]

I'm trying to create a custom ant task that I can call from my build 
scripts.  Right now I'm just trying to figure out how to write a task 
that can accept a fileset and iterate through all valid files.  My best 
guess so far is below.

Unfortunately, this is giving me errors that I have not encountered in 
Java before.  What does 'cannot be applied to ()' mean?  Could anyone 
suggest what I could do to fix my program?

Thanks.
Mark McKay
=
Error:
com/kitfox/anttask/MyAntTask.java [26:1] 
getDirectoryScanner(org.apache.tools.ant.Project) in 
org.apache.tools.ant.types.AbstractFileSet cannot be applied to ()
   DirectoryScanner scanner = fs.getDirectoryScanner();
^
1 error
Errors compiling MyAntTask.

=
package com.kitfox.anttask;
import org.apache.tools.ant.*;
import org.apache.tools.ant.taskdefs.*;
import org.apache.tools.ant.types.*;
/**
*
* @author  kitfox
*/
public class MyAntTask extends MatchingTask {
  
   /** Creates a new instance of MyAntTask */
   public MyAntTask() {
   }
  
   public void execute() throws BuildException
   {
   FileSet fs = getImplicitFileSet();
   DirectoryScanner scanner = fs.getDirectoryScanner();
  
   scanner.scan();
  
   String[] files = scanner.getIncludedFiles();
   for (int i = 0; i < files.length; i++) {
   System.out.println(files[i]);
   }
   }
  
}


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

DO NOT REPLY [Bug 26299] - Using sshexec to run ant remotely - Using ant to run sshexec

[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=26299

Using sshexec to run ant remotely - Using ant to run sshexec





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 08:20 ---
Hi,
I think you want to "source" your login script on the remote machine before
starting ant.
Try this


(. .profile would be the way to explicitly source your profile under ksh.
For csh, it would be "source .cshrc" I believe.

Hopes this helps,

Antoine

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

RE: [ANN] Cocoon Task

[Jan . Materne]

Corrected 

Jan

> -Original Message-
> From: Upayavira [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 20, 2004 2:51 PM
> To: Ant Developers List
> Subject: Re: [ANN] Cocoon Task
> 
> 
> [EMAIL PROTECTED] wrote:
> 
> >Done.
> >  
> >
> Fab. But (and I see that this was my mistake) - there's a 
> typo: "sties" 
> should be "sites" in the first paragraph. Sorry for the mistake!
> 
> Thanks. Upayavira
> 
> >Jan
> >
> >  
> >
> >>-Original Message-
> >>From: Upayavira [mailto:[EMAIL PROTECTED]
> >>Sent: Friday, January 16, 2004 5:03 PM
> >>To: [EMAIL PROTECTED]
> >>Subject: [ANN] Cocoon Task
> >>
> >>
> >>I've now completed and tested my Cocoon Ant task. I've 
> >>finished the docs
> >>for it (URL shown below), they just need to be uploaded to the site
> >>(which I don't yet know how to do :-(
> >>
> >>I must say, I rather like this task, and I think that it 
> could/should
> >>become the recommended way to access Cocoon's offline functionality,
> >>because of the range of functionality available in Ant that 
> >>can be used
> >>to augment the work that Cocoon does.
> >>
> >>Please add it to your external tasks page.
> >>
> >>Regards, Upayavira
> >>
> >>
> >>
> >> This task allows the generation of static web pages and
> >>sties using Apache Cocoon in off-line mode.   
> >> It allows the configuration information for Cocoon to be
> >>included within the Ant build file, and is thus
> >>able to take advantage of Ant properties.
> >> The task shares its code with the Cocoon Command 
> >>Line, which
> >>means that this task will instantly take
> >>advantage of any new functionality added there.
> >>
> >>   
> >> 
> >>   Compatibility:
> >>   Ant 1.5.3 and above
> >> 
> >> 
> >>   URL:
> >>>>href="http://cocoon.apache.org/2.1/";>http://cocoon.apache.org/
> >>2.1/
> >> 
> >> 
> >>   Documentation:
> >>>>href="http://cocoon.apache.org/2.1/userdocs/offiline/ant.html";
> >>
> >>
> >>>http://cocoon.apache.org/2.1/userdocs/offline/ant.html 
> >>>  
> >>>
> >> 
> >> 
> >>   Contact:
> >>   mailto:users.at.cocoon.apache.org";>users at
> >>cocoon.apache.org
> >> 
> >> 
> >>   License:
> >>   Apache Software License
> >> 
> >>   
> >> 
> >>
> >>
> >>
> >>
> -
> >>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/docs external.html

[jhm]

jhm 2004/01/20 22:55:58

  Modified:xdocsTag: ANT_16_BRANCH external.xml
   docs Tag: ANT_16_BRANCH external.html
  Log:
  Sync with HEAD: Typo in CocoonTask
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.100.2.5 +1 -1  ant/xdocs/external.xml
  
  Index: external.xml
  ===
  RCS file: /home/cvs/ant/xdocs/external.xml,v
  retrieving revision 1.100.2.4
  retrieving revision 1.100.2.5
  diff -u -r1.100.2.4 -r1.100.2.5
  --- external.xml  20 Jan 2004 06:49:25 -  1.100.2.4
  +++ external.xml  21 Jan 2004 06:55:58 -  1.100.2.5
  @@ -359,7 +359,7 @@
   
 
   This task allows the generation of static web pages and
  -sties using Apache Cocoon in off-line mode.
  +sites using Apache Cocoon in off-line mode.
   It allows the configuration information for Cocoon to be
   included within the Ant build file, and is thus
   able to take advantage of Ant properties.
  
  
  
  No   revision
  No   revision
  1.136.2.6 +1 -1  ant/docs/external.html
  
  Index: external.html
  ===
  RCS file: /home/cvs/ant/docs/external.html,v
  retrieving revision 1.136.2.5
  retrieving revision 1.136.2.6
  diff -u -r1.136.2.5 -r1.136.2.6
  --- external.html 20 Jan 2004 06:49:25 -  1.136.2.5
  +++ external.html 21 Jan 2004 06:55:58 -  1.136.2.6
  @@ -797,7 +797,7 @@
   Cocoon Task
 
   This task allows the generation of static web 
pages and
  -sties using Apache Cocoon in off-line mode.
  +sites using Apache Cocoon in off-line mode.
   It allows the configuration information 
for Cocoon to be
   included within the Ant build file, and is thus
   able to take advantage of Ant properties.
  
  
  

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

cvs commit: ant/docs external.html

[jhm]

jhm 2004/01/20 22:50:55

  Modified:xdocsexternal.xml
   docs external.html
  Log:
  Typo in CocoonTask
  
  Revision  ChangesPath
  1.114 +1 -1  ant/xdocs/external.xml
  
  Index: external.xml
  ===
  RCS file: /home/cvs/ant/xdocs/external.xml,v
  retrieving revision 1.113
  retrieving revision 1.114
  diff -u -r1.113 -r1.114
  --- external.xml  20 Jan 2004 06:40:44 -  1.113
  +++ external.xml  21 Jan 2004 06:50:55 -  1.114
  @@ -359,7 +359,7 @@
   
 
   This task allows the generation of static web pages and
  -sties using Apache Cocoon in off-line mode.
  +sites using Apache Cocoon in off-line mode.
   It allows the configuration information for Cocoon to be
   included within the Ant build file, and is thus
   able to take advantage of Ant properties.
  
  
  
  1.154 +1 -1  ant/docs/external.html
  
  Index: external.html
  ===
  RCS file: /home/cvs/ant/docs/external.html,v
  retrieving revision 1.153
  retrieving revision 1.154
  diff -u -r1.153 -r1.154
  --- external.html 20 Jan 2004 06:40:44 -  1.153
  +++ external.html 21 Jan 2004 06:50:55 -  1.154
  @@ -800,7 +800,7 @@
   Cocoon Task
 
   This task allows the generation of static web 
pages and
  -sties using Apache Cocoon in off-line mode.
  +sites using Apache Cocoon in off-line mode.
   It allows the configuration information 
for Cocoon to be
   included within the Ant build file, and is thus
   able to take advantage of Ant properties.
  
  
  

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

DO NOT REPLY [Bug 26299] - Using sshexec to run ant remotely - Using ant to run sshexec

[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=26299

Using sshexec to run ant remotely - Using ant to run sshexec





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 06:34 ---
Nice idea - I thought about something like that for myself.

Try the following:
- upload all things (with Ant; should work as you said)
- run the  in verbose mode and notice the command which is executed
- use ssh to login _manually_ on the remote machine
- try the command noticed earlier _manually_

If it fails: something on the machine is wrong (e.g. no installed java).
If it´s ok: somewhere else ... (maybe in Ant)

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

DO NOT REPLY [Bug 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 05:59 ---
The problem arises because there's no empty line before Class-Path.
If you simply add and repackage by hand it will surely work!

It should work if produced MANIFEST.MF looks like (between == ):

==
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.0
Created-By: 1.4.2_02-b03 (Sun Microsystems Inc.)
Main-Class: com.foo.MainClass

Class-Path: JCalendar4.jar MDateSelector.jar forms-1.0.2.jar j2ee.jar 
 jboss-client.jar jboss-common-client.jar jboss-j2ee.jar jbosssx-clien
 t.jar jnp-client.jar log4j.jar
==

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

DO NOT REPLY [Bug 26300] - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries





--- Additional Comments From [EMAIL PROTECTED]  2004-01-21 00:12 ---
Created an attachment (id=10040)
generated manifest for executable jar

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

DO NOT REPLY [Bug 26300] New: - manifest task munges classpath entries

[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=26300

manifest task munges classpath entries

   Summary: manifest task munges classpath entries
   Product: Ant
   Version: 1.6.0
  Platform: PC
OS/Version: Windows NT/2K
Status: NEW
  Severity: Major
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When creating an executable JAR, the resultant classpath entry in the manifest 
is unreadable by the JDK/JRE.

I've seen the bug reports that have been marked as being invalid due to the 
spec, but it's still not being handled correctly.  I'm not sure if it's a case 
of missing the right line continuation, or the word breaking.

here's the task snippet









   


 ${client.classpath} 

 

  


  


I will attempt to attach the physical file, but just in case, I've pasted it 
here, placing an asterisk at the end of the line for each line:

Manifest-Version: 1.0*
Ant-Version: Apache Ant 1.6.0*
Created-By: 1.4.2_02-b03 (Sun Microsystems Inc.)*
Main-Class: com.foo.MainClass*
Class-Path: JCalendar4.jar MDateSelector.jar forms-1.0.2.jar j2ee.jar *
 jboss-client.jar jboss-common-client.jar jboss-j2ee.jar jbosssx-clien*
 t.jar jnp-client.jar log4j.jar*



output from java -version:

java version "1.4.2_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4
Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)

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