Hello all!
The decompiler produces the exact same output every time (both for Ant-Javac
and "command line"-Javac) and the Ant-Javac output it always different
from the "command-line"-Javac
Brian Pontarelli wrote:
>
> I would think it would produce the exact same output each time unles
Hi,
Perhaps I'm missing something, well, I must be. I've tried a variety
of things and I keep scanning the docs but I can't seem to make this
work.
I want to do the equivalent of
chmod `find -type d`
so as to apply the chmod to only directories, no files.
In ant I currently have:
What I have is the the following
haltonfailure="no" haltonerror="no"
failureproperty="tests.failures" errorproperty="tests.errors"
>
On 21 Nov 2009, at 18:20, glenn opdycke-
it appears that the name of the property being set is different than what is
being checked:
On Sat, Nov 21, 2009 at 12:12, Ben Cuthbert wrote:
> Strange thing is, if I set this property in the top of the file
>
>
>
> And then in my target put
>
>
>
> I get and error
>
> build-common.xml:347:
Dear ant users,
i have a problem using the ant's Scp in my custom ant task.
When executing my custom ant task (via ant) i get a
ClassNotFoundException: com/jcraft/jsch/UserInfo.
But the class is definitely in the classpath. Using this class in my
custom task directly (before accessing Scp) gi
Strange thing is, if I set this property in the top of the file
And then in my target put
I get and error
build-common.xml:347: Test failed!!!
On 21 Nov 2009, at 16:33, Ben Cuthbert wrote:
Yes so I have the following line in the same target at the end, I
see the unit test error but th
I set those and nothing, still unit test fails but the build passes.
In the verbose log I just see
[junit] 'filtertrace=true'
[junit] 'haltOnError=false'
[junit] 'haltOnFailure=false'
[junit] 'showoutput=false'
[junit]
'formatter
=org.apache.tools.ant.taskdefs.optional.jun
What if you change the halton* to "no" ?
I would run it with verbose set on in order to get more details.
--glenn
On Sat, Nov 21, 2009 at 02:43, Ben Cuthbert wrote:
> failureproperty="tests.failures" errorproperty="tests.errors">
>
Strange thing is, if I set this property in the top of the file
And then in my target put
I get and error
build-common.xml:347: Test failed!!!
On 21 Nov 2009, at 16:33, Ben Cuthbert wrote:
Yes so I have the following line in the same target at the end, I
see the unit test error but th
I would think it would produce the exact same output each time unless it is
using some type of system dependent code or timestamps.
-bp
On Nov 21, 2009, at 6:41 AM, Ziggy wrote:
> I would have thought that the decompiling is the reason they are different.
> Do you get the same result when you
Yes so I have the following line in the same target at the end, I see
the unit test error but the build does not stop
On 21 Nov 2009, at 10:05, Greg Roodt wrote:
I am trying to run the Mail sample application from the Google Web
Toolkit. I get the following...
C:\gwt-windows-1.7.1\samples\Mail>ant -noclasspath hosted
C:\Program Files\Java\JDK5
Unable to locate tools.jar. Expected to find it in C:\Program
Files\Java\jre6\lib\tools.jar
Buildfile: build
I would have thought that the decompiling is the reason they are different.
Do you get the same result when you decompile the same file twice?
I am not an expert but i think the decompiler can produce different code
that achieves the same thing. Try to decompile the same file twice and see
if the
Are you picking up your tests.failures property somewhere to fail the build?
e.g.
On Sat, Nov 21, 2009 at 8:43 AM, Ben Cuthbert wrote:
> When one of my unit tests fail the build is still successful. But in my ant
> config I have the following
>
> failureproperty="tests.failures" errorpropert
When one of my unit tests fail the build is still successful. But in
my ant config I have the following
failureproperty="tests.failures" errorproperty="tests.errors">
15 matches
Mail list logo
