Can you run Ant in -verbose or -debug mode and post the execution command?
Maybe you could try that generated command directly on command line.
Jan
> -Ursprüngliche Nachricht-
> Von: Barry Pape [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 18. Januar 2008 01:52
> An: Ant Users List
> B
Howdy Ant Friends,
I am having an issue with running a deploy script on a remote server.
This command works beautifully:
ssh -t myserver.net /usr/local/bin/sudo -u myuser
/path/to/deploy_build.sh
But when I invoke this command using exec in ant the '-t' argument does
not get used. Otherwise the
Hi,
> Thanks DD -- we are mostly an MS shop, but we do have a mixed set of
> developers. I'm actually part of a dev group doing Java and we are already
> using Ant for our build process (javac, junit, javadocs, deployment, even
> some 3rd party tasks for compiling Adobe Flex code and remote ssh
>
Thanks DD -- we are mostly an MS shop, but we do have a mixed set of
developers. I'm actually part of a dev group doing Java and we are already
using Ant for our build process (javac, junit, javadocs, deployment, even
some 3rd party tasks for compiling Adobe Flex code and remote ssh
connections to
+1.
I like the idea of having an xsl to do this (I'm a little embarrassed that I
didn't think of it before). I'd be happy to help you work on it or test it.
I had written an ant task to do the same sort of thing, but XSL would be a lot
simpler.
-Original Message-
From: Nicolas Lalev
I understand everybody frustration here, and that's why I take time to
fix IvyDE.
Maybe to tackle users frustrations we can provide a simple XSL that
transform Ivy's resolve report into Eclipse classpath ?
We loose the easy of use of IvyDE, the cool editor, but at least it
will integrate Iv
On Jan 17, 2008 2:00 PM, Jack J. Woehr <[EMAIL PROTECTED]> wrote:
> Many ways to do this. One naive algorithm:
>
> 1. Pass in list of solutions as an ant Property
> * i.e., string with some internal delimiter repeated between
> solutions
> 2. Use AntContrib's 'forea
On Jan 17, 2008, at 12:34 PM, weiji wrote:
The first issue is to figure out how to pass this
list of solutions into Ant.
Many ways to do this. One naive algorithm:
1. Pass in list of solutions as an ant Property
* i.e., string with some internal delimiter repeated bet
On Jan 17, 2008 1:34 PM, weiji <[EMAIL PROTECTED]> wrote:
> Our current build process involves a DOS batch file to loop through a list
> of solutions that we want to build, and invoking the command line Visual
> Studio client to build each one. We are interested in Ant as a replacement,
> since we
Hi,
Our current build process involves a DOS batch file to loop through a list
of solutions that we want to build, and invoking the command line Visual
Studio client to build each one. We are interested in Ant as a replacement,
since we believe the logic control/conditional execution of targets
The mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 10:49 AM
To: Ant Users List
Subject: Re: using to check for tool availability
On Jan 17, 2008 9:20 AM, Buck, Robert <[EMAIL PROTECTED]> wrote:
> Does anyone have any better suggestions for how to check for tool
> existence in Ant?
On Jan 17, 2008 9:20 AM, Buck, Robert <[EMAIL PROTECTED]> wrote:
> Does anyone have any better suggestions for how to check for tool
> existence in Ant?
But you need to know the exact file name (dot or dot.exe), and
env.PATH is not always portable because of case on Windows, where it
can be Pat
Hello,
I have a problem I am trying to solve that I need some help with. What
I'd like to do is check for the availability of an executable tool on
the system path. If the tool is available, then allow extra (secret
sauce) features to be enabled. Otherwise the extra (non-essential) build
features
Thanks. I didn't mean to start a flame thread, though I figured it would
probably happen.
The response I expected was, "it's open source, if you don't like it fix it",
which is completely valid.
I've checked out the source of IVYDE and attempted a few modifications, but I'm
admittedly not th
> -Original Message-
> From: Steve Loughran [mailto:[EMAIL PROTECTED]
> Sent: jeudi 17 janvier 2008 12:24
> To: Ant Users List
> Subject: Re: Redirecting compile errors
>
> Peter Reilly wrote:
> > On Jan 17, 2008 9:52 AM, Peter Reilly <[EMAIL PROTECTED]> wrote:
> >> On Jan 17, 2008 9:37
Hi,
> >>> and Java 1,3-compatible language features...it has to compile on older
> >>> versions. What we can do is have a directory of java6+ code that isnt
> >>> built on Java <6.
> >> I do not think that the ability to compile ant on < java5 is necessary.
> >>
> > The reaon I think this is that t
Peter Reilly wrote:
On Jan 17, 2008 9:52 AM, Peter Reilly <[EMAIL PROTECTED]> wrote:
On Jan 17, 2008 9:37 AM, Steve Loughran <[EMAIL PROTECTED]> wrote:
Peter Reilly wrote:
On Jan 17, 2008 12:37 AM, James Abley <[EMAIL PROTECTED]> wrote:
What is the base target version for ant development thes
On Jan 17, 2008 9:52 AM, Peter Reilly <[EMAIL PROTECTED]> wrote:
> On Jan 17, 2008 9:37 AM, Steve Loughran <[EMAIL PROTECTED]> wrote:
> > Peter Reilly wrote:
> > > On Jan 17, 2008 12:37 AM, James Abley <[EMAIL PROTECTED]> wrote:
> >
> > >> What is the base target version for ant development these d
On Jan 17, 2008 9:37 AM, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Peter Reilly wrote:
> > On Jan 17, 2008 12:37 AM, James Abley <[EMAIL PROTECTED]> wrote:
>
> >> What is the base target version for ant development these days? Java 5?
> >>
> > It is java5, however, the ant jars need to be able to
Peter Reilly wrote:
On Jan 17, 2008 12:37 AM, James Abley <[EMAIL PROTECTED]> wrote:
What is the base target version for ant development these days? Java 5?
It is java5, however, the ant jars need to be able to work gracefully in
a java1.3 and java1.4 env (i.e. support what can be supported)
20 matches
Mail list logo
