On 1/3/07, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
A month ago with 1.7.0RC1 my BSF problems ended when Jacob Kjome wrote:
> On Dec 6, 2006, at 5:33 PM, Peter Reilly wrote:
>
> > You can use bsf 2.4.0 and rhino 1.5r4 but
>
> I definitely have Rhino 1.6.5. I *theenk* I have the 2.4.0 of
>
Antoine,
Sorry for the long delay in response. I'm just back from 3 weeks of
vacation.
I have installed ANT 1.7 and retested with the new template. The good news
is that the new br-replace template does successfully replace newline with
tags. There is an important difference between the resul
Fixed it. (I spent 2 hours on this, and just after I hit send, I realise
that there was one more place to check :)
cruise control has a cruisecontrol/lib directory with ant.jar in it. You
need to ensure that ant.jar, ant-junit.jar and junit.jar are all the
right versions and are all present in thi
I'm currently attempting to set up cruise control just now and I agree
with the high maintainance aspect. My plan once I am finished is to
publish some step-by-step instrctions on getting subversion, CC, ant and
junit all working nicely together under FC6.
I have an issue right now where, if I run
Dear Ant User Group.
I am having a problem to execute Ant via Java. After startAnt()
executed, the Hello.xml was done successfully, but it does not go
though the next step which supports to be printing out the output
"Hello, it is done".
another strange thing is when i run it on Dos comman
Hi,
This issue lies in the nexus of tomcat and ant: jspc fails with this
message when I try to build tomcat from source:
/usr/local/jakarta-tomcat/apache-tomcat-5.5-svn/build/build.xml:429:
No public execute() in class org.apache.jasper.JspC
Why? The source code clearly has an 'execute()' m
A month ago with 1.7.0RC1 my BSF problems ended when Jacob Kjome wrote:
> On Dec 6, 2006, at 5:33 PM, Peter Reilly wrote:
>
> > You can use bsf 2.4.0 and rhino 1.5r4 but
>
> I definitely have Rhino 1.6.5. I *theenk* I have the 2.4.0 of
> BSF but I'll download again to be sure ... that is, I shall
Yes, after reading the CC's manual yesterday, I agree and find it cumbersome
and hight maint too. I will look at lundtbuild. Thanks.
Original Message Follows
From: Steve Loughran <[EMAIL PROTECTED]>
Reply-To: "Ant Users List"
To: Ant Users List
Subject: Re: Odd Behavior
Date: Wed, 03
I'm using the p4label Perforce task and it is properly creating the
label in Perforce but the owner in for that label is not being set. Has
anyone encountered this problem before?
Robert Segal
Sr. Tools Developer
CryptoLogic Inc.
55 St. Clair Ave W., 3rd Floor
Toronto, Ontario
Canada M4V 2Y7
te
Hi Scot. Thanks for the reply. I have sorted it finally after a lot of
hassle. The solution was to go to the build.xml and in the javac part at
source="1.3" and target="1.3" ... seems a little simple! Thanks for the help
Scot P. Floess wrote:
>
> It sounds like an environment issue... Regarding
Rapthor wrote:
Donald McLean wrote:
Really? That sounds like a case of "The cure is worse than the disease."
I can't imagine a single case where something like that would be a
better solution than the three or four techniques for providing static
attributes that I'm already familiar with.
Keith Hatton wrote:
Two more robust solutions spring to mind:
1. You can use Properties.getProperty(String,String) to prevent your
NPE. The first string is the property name, the second is a default
value to be used when the property is not present.
http://java.sun.com/j2se/1.5.0/docs/api/java/u
It sounds like an environment issue... Regarding the class version
error...I think you are correct - it is compiled to 1.3 however, for
some reason, the 1.3 VM is attempting to use the 1.5 version of the Java
classes. You may need to install a 1.3 version of the JDK and "tell"
Eclipse to use
Res Pons wrote:
Thanks for your reply. I was using AnthillOS for a while but I gave up
in frustration. It's a kiddy tool for starters but very easy to use,
however, the developers of it were so agonizingly slow to implement
features, I gave up. Now I'm reading on CruiseControl. I read a bit
Hiya, at that point -- the ant builder run time preferences has a 'global
entries' section which contains tools.jar for jdk 1.5. If I replace it with
1.3 it comes up with those errors (as its still looking for other libraries
in 1.5 folder so there's a mix of java versions). Not sure how to change
I've created a test case that's just like the Ant Wiki code, except
I've specified net.sf.saxon.TransformerFactoryImpl in the
element. But when I do that, I always get
java.lang.ClassNotFoundException. I can work around it by explicitly
putting Saxon's JAR in the -lib command-line parameter, or i
OK I found your original email... It looks like you have a number of
problems... When you get that exception (class version) what is it you
are doing at that time? That doesn't look to me to be a compile time
exception...
Scot P. Floess wrote:
I believe its simply:
You may also have to
I believe its simply:
You may also have to specify using the attribute source="1.3"
When you say "it's still having the problem" - can you refresh my memory
- what is the problem exactly? I deleted my emails :(
m1ke wrote:
Hi ,thanks for the reply. Yeah there is a build.xml, previously t
Hi ,thanks for the reply. Yeah there is a build.xml, previously tried putting
a < target="1.3"> tag in a javac area of the build.xml... perhaps it wasnt
entered correctly as it's still having the problem. Will try again.. what is
the best way to do go about it? (just double-checking entered it cor
If memory serves, the location attribute should be a directory, jar
file, etc. The path attribute is just that...it can contain a path ;)
Alasdair Young wrote:
It worked!!
I used:
instead of
and it worked!
I have no idea why it worked (This is my first major reworking of an
If you need to compile targeted to JDK 1.3, you will need to set your
... I am not an Eclipse user so I can't help you
there... I'm guessing an Ant build.xml is generated that you can edit?
m1ke wrote:
Hi. I am using Ant within Eclipse and need to compile to java 1.3. The
problem is Eclipse
Hi. I am using Ant within Eclipse and need to compile to java 1.3. The
problem is Eclipse is loaded up with 1.5 - and as its loaded up in this, Ant
uses 1.5. All the settings in Eclipse are set to compile to 1.3, but I'm
having a lot of trouble finding how to do this within the Ant settings also.
Two more robust solutions spring to mind:
1. You can use Properties.getProperty(String,String) to prevent your
NPE. The first string is the property name, the second is a default
value to be used when the property is not present.
http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#ge
23 matches
Mail list logo
