On 10/27/06, Danny Vint <[EMAIL PROTECTED]> wrote:
I've brought my files on to a local machine to see if there was anything
I could discover.
In my first attempt, Ant zip, created a file but the build failed due to
memory. The file it actually built was ok - it at least opened and looked
fine. W
On 10/27/06, Dominique Devienne <[EMAIL PROTECTED]> wrote:
On 10/27/06, Jeff Holt <[EMAIL PROTECTED]> wrote:
> The reason I don't want to use is that I have to qualify the
> executable path. Otherwise, for some yet unknown reason, ant executes
> /usr/bin/java rather than the one in the PATH. And
Yes, java.home works. I see that I am definitely not the first person to
experience it.
Thanks, Dom.
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Friday, October 27, 2006 4:15 PM
To: Ant Users List
Subject: Re: java task question for ant 1.6.5
On 10/27/06,
On 10/27/06, Jeff Holt <[EMAIL PROTECTED]> wrote:
The reason I don't want to use is that I have to qualify the
executable path. Otherwise, for some yet unknown reason, ant executes
/usr/bin/java rather than the one in the PATH. And, of course,
/usr/bin/java, is not appropriate.
Both and have
I've brought my files on to a local machine to see if there was anything
I could discover.
In my first attempt, Ant zip, created a file but the build failed due to
memory. The file it actually built was ok - it at least opened and looked
fine. What we discovered was it was missing some files.
The reason I don't want to use is that I have to qualify the
executable path. Otherwise, for some yet unknown reason, ant executes
/usr/bin/java rather than the one in the PATH. And, of course,
/usr/bin/java, is not appropriate.
I gave ${jre.home} a try and it didn't get resolved. I looked but di
If they already know Maven they probably wont go backwards to Ant
The problem with both is the script tasks are very much dynamic so as soon as
you write something down it becomes obsolete..
my 2 sense
M-
This e-mail communication and any attachments may contain confidential and
privileged infor
On 10/27/06, Jeff Holt <[EMAIL PROTECTED]> wrote:
To make my build script a bit less susceptible to environmental errors,
I'd like to rewrite the following task:
Simply replace ${env.JAVA_HOME} by ${jre.home}, and it will use the
same JRE or JDK used by Ant itself. is better than
+ in this c
Ah, yes. I forgot all about that one. It probably will do the trick.
Thanks, Matt.
-Original Message-
From: Matt Benson [mailto:[EMAIL PROTECTED]
Sent: Friday, October 27, 2006 2:57 PM
To: Ant Users List
Subject: Re: java task question for ant 1.6.5
You might look at using ant-contrib's
Does anybody have any tips? on Interview questions on ANT and Mavem2?
**
--
Regards,
Aruna Challapalli
E-mail: [EMAIL PROTECTED]
cell: 512-573-6955
You might look at using ant-contrib's task with
.
-Matt
--- Jeff Holt <[EMAIL PROTECTED]> wrote:
> To make my build script a bit less susceptible to
> environmental errors,
> I'd like to rewrite the following task:
>
>
>
>
>
>
>
>
>
>
>
>
To make my build script a bit less susceptible to environmental errors,
I'd like to rewrite the following task:
Here is something that probably conveys what I want:
--- Vladimir Egorov <[EMAIL PROTECTED]> wrote:
> Hi Ant Users,
>
> I am using FileList to specify collection of files
> one by one. I need to
> ensure that the specified files exist.
There are different things you can do here. Are you
using a predefined "files" attribute, in a property
perhaps?
> -Original Message-
> From: Peter Reilly [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 27, 2006 9:45 AM
> To: Ant Users List
> Subject: Re: a construct to ensure existence of files in collection?
>
> On 10/27/06, Vladimir Egorov <[EMAIL PROTECTED]> wrote:
> > Hi Ant Users,
> >
> > I a
I think I've solved the problem. When I use the "executable" attribute,
it starts complaining that the -source command-line parameter isn't
supported. However, when I remove the source="1.3" and target="1.3"
attributes, it stops complaining; so those parameters must be
incompatible with the J
On 10/27/06, Vladimir Egorov <[EMAIL PROTECTED]> wrote:
Hi Ant Users,
I am using FileList to specify collection of files one by one. I need to
ensure that the specified files exist.
According to FileList doc, "FileLists are useful for specifying files
that may or may not exist". I checked some
I believe that the -source and -target parameters are specific to java 1.5.
If you are using the 1.3 compiler, you don't need to try to ensure
compatibility with 1.3, its automatic.
On 10/25/06, Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote:
Hello Wayne,
you need to set both executable and for
Hi Ant Users,
I am using FileList to specify collection of files one by one. I need to
ensure that the specified files exist.
According to FileList doc, "FileLists are useful for specifying files
that may or may not exist". I checked some other path-like structures,
but did not find a straight-fo
EJ Ciramella wrote:
Honestly, it's developers thinking exec is good enough, but when the
server hangs, all of cruisecontrol hangs. Nothing gets reported and
things just sit there.
Thanks for the tips, I'm going to keep digging.
CC is very brittle.
Why not give exec a timeout?
--
Honestly, it's developers thinking exec is good enough, but when the
server hangs, all of cruisecontrol hangs. Nothing gets reported and
things just sit there.
Thanks for the tips, I'm going to keep digging.
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Friday
EJ Ciramella wrote:
I'm going to try here first before moving over to the cargo mailing
lists. Is anyone using this via ant?
-dont be afraid to talk to them, esp on the #iRC channel. If found them
helpful
To start up the server for integration testing, we use the task
to start/stop the se
I'm going to try here first before moving over to the cargo mailing
lists. Is anyone using this via ant?
To start up the server for integration testing, we use the task
to start/stop the server currently. The bad thing is, if there is a
test failure, the server continues to run and winds up in
I'm wondering if anyone else has seen this problem or has some suggestions
on fixing the problem.
I have a large build process that uses and all over the
place. We are finding at least ion one of these locations that the
resulting zip file has some sort of problem. We have seen the following
Hi...
We've got some CruiseControl projects using Ant that are
chained together. One task is the build task which compiles everything
and packages up a zip of the product. It that works, there's a
dependent CC project that then calls ant to install that software on a
staging serve
I am using IntelliJ and have added a package prefix to my swing project.
If my prefix is "com.mycompany", this means I can have my source in
rather than . At the moment I can't make the
physical change due to source control issues.
An ant build works fine but when I run the applet I get a cons
>>> > bat files are not executable, use cmd.exe instead and the bat as
>>> > argument.
>>> > See FAQ and (1.7) manual.
>>>
>>> I've been thinking about this. Why dont we have Exec complain if we
>>> find a .bat or .cmd at the end of an executable on windows?
>>
>> Because one can execute some ba
Peter Reilly wrote:
On 10/27/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
>> build.bat is called by the buildApp.xml with :
>>> failifexecutionfails="false" failonerror="false">
>
>
> bat files are not executable, use cmd.exe instead and the bat as
> argument.
On 10/27/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote:
>> build.bat is called by the buildApp.xml with :
>>> failifexecutionfails="false" failonerror="false">
>
>
> bat files are not executable, use cmd.exe instead and the bat as
> argument.
> See FAQ and (1.7) m
[EMAIL PROTECTED] wrote:
build.bat is called by the buildApp.xml with :
failifexecutionfails="false" failonerror="false">
bat files are not executable, use cmd.exe instead and the bat as
argument.
See FAQ and (1.7) manual.
I've been thinking about this. Why dont we have Exec complain
Scot P. Floess wrote:
Steve:
Now that I give this some deeper thought...I see now what the intent
is... I got hung up on dual parsing...one by task and one the the
JDBC layer: clearly one has to be able to issue a sql statement - thus
the delimiter attribute - duh on my part :(
I do see
>build.bat is called by the buildApp.xml with :
>failifexecutionfails="false" failonerror="false">
bat files are not executable, use cmd.exe instead and the bat as
argument.
See FAQ and (1.7) manual.
> [exec] BUILD FAILED
> [exec] Target `610 Builds' does not exist in this project.
F
That is the last target/task that was executed.
So just have a look at the output.
Jan
>-Ursprüngliche Nachricht-
>Von: Sentella Cystrunk [mailto:[EMAIL PROTECTED]
>Gesendet: Donnerstag, 26. Oktober 2006 19:48
>An: user@ant.apache.org
>Betreff: Reporting build failures
>
>I'm trying to
Please run the build in debug mode an add the stacktrace.
Jan
>-Ursprüngliche Nachricht-
>Von: anne robert [mailto:[EMAIL PROTECTED]
>Gesendet: Donnerstag, 26. Oktober 2006 11:02
>An: user@ant.apache.org
>Betreff: Problem creating a task to generate java from an EMF model
>
>Hi,
>I am
Hi,
I am running the following code to run this ant file.
private void antRun(){
File buildFile = new File("C:\\Documents and Settings\\tharanga\\My
Documents\\IBM\\wssitedev51\\workspace\\BundleDeployer\\build.xml");
if(buildFile.exists()){
Project p = new Project();
p.setUserProperty("ant.
34 matches
Mail list logo
