Well simply adding ant-apache-bsf-1.7.0.jar to my libs seemed to do
the trick, so thanks!
I am now happily scripting in ant.
Francisco
On Dec 31, 2007, at 6:05 PM, David Weintraub wrote:
Java on Leopard is version 1.5 (which is one of the big complaints).
The error message is saying that
"o
Hi All,
Just to inform the list about the problem mentioned in subject line, as
mentioned to Freeman, I found later that it was not the valid reaons for the
problem, but reaon I found was big paths in javac task which caused the
problems... which took me a while to investigae.
I shortened the p
I am not sure what your complaint is. It looks like it is performing
as expected as far as I can tell. It looks like everything is working
according to the output of the debug.
* Are you expecting something specific?
* What is ${model-helper-source.path} being set to? Is it any chance
"**/com/**/
Java on Leopard is version 1.5 (which is one of the big complaints).
The error message is saying that
"org.apache.tools.ant.util.optional.ScriptRunner" is not found. This
class isn't found in bsf.jar, but in ant-apache-bsf-1.7.0.jar which I
found at http://www.ibiblio.org/maven/org.apache.ant/jars
I created a simple build.xml based upon what you gave:
I created two jar files in the classpath, foo.jar and bar.jar. When I
run ant, I get the following output:
/Users/david$ ant
Buildfile: build.xml
compile:
[echo] b
Hello Francisco, isn't Leopard new to Java 6? There are known problems with
Leopard and Java 6 see: javalobby article:
http://www.javalobby.org/java/forums/t102936.html
What is the JDK version?
run: ant -debug
What echo message do you get from ${env.CLASSPATH} ?
Francisco Tolmasky wrote ..
> He
Hello, I am attempting to use JavaScript within ant and am running
into a few difficulties.
I used to be able to do the following in Mac OS X Tiger just fine:
/* whatever */
However, since moving to Mac OS X Leopard, I get the following error:
java.lang.Clas
Hello ant dev, commit, gurus and users, I have a strange element in a
build.xml file. The element is included below. Regardless of what I do to
remedy the situation the path is constructed with the single directory file
path token: webapps. For example if the project property basedir="." and th
Anybody have any ideas if this is expected behavior, a bug or a feature?
Troy
> -Original Message-
> From: Daniels, Troy (US SSA)
> Sent: Tuesday, December 18, 2007 3:11 PM
> To: user@ant.apache.org
> Subject: Properties for include in fileset
>
> At several places, I need to build a f
