Nabble - Ant

Re: Ivy svn breaks ant-contrib svn

2008-07-18T08:33:46Z

On Thu, 17 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:

> On Thu, Jul 17, 2008 at 10:00 AM, Stefan Bodewig <bodewig@...> wrote:
>
>> I don't really have an opinion on the particular change but am a
>> strong proponent of not breaking APIs in general (at least not
>> without a deprecation period).
>
> I agree in general, but Ivy 2 has been going in a deep code change, and we
> decided to keep backward compatibility with 1.4 at ant tasks level, but not
> at API level.

Understood.

> We warned the users about that in the release notes, and changing
> code in Ivy for backward compatibility with a beta version (which in
> Ivy language is not a release candidate) sounds not like a good idea
> to me.

That is more tha fine with me.

> But once again I'm alone to decide, and if more people think it
> makes sense, I won't object.

There is no reason to change anything for me.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

Re: Ivy svn breaks ant-contrib svn

2008-07-18T07:35:11Z

On Thu, 17 Jul 2008, Maarten Coene <maarten_coene@...> wrote:

> Just a wild guess, but maybe you could use IvyAntSettings again
> (like your original code was),

I thought so myself and had a quick look, but I'm neither familiar
enough with Ivy nor what the ant-contrib task is trying to do that I
dared to change anything.

I might give it a try sometime later in August.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

Re: svn commit: r677887 - in /ant/core/trunk: CONTRIBUTORS contributors.xml src/main/org/apache/tools/ant/taskdefs/optional/net/RExecTask.java src/main/org/apache/tools/ant/taskdefs/optional/net/TelnetTask.java

2008-07-18T05:50:25Z

On Fri, 18 Jul 2008, <bodewig@...> wrote:

> avoid excessive StringBuffer.toString calls while waiting for a
> response string. PR 34464. Based on patch by Adam Blinkinsop.

I'd appreciate it if anybody who's still running telnet or even rexec
could double check that the patch didn't breal anything. It looks
fine but I haven't run any sort of "integration test" here.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

Re: Logging and synchronization

2008-07-17T17:07:11Z

Stefan Bodewig <bodewig@...> wrote on 07/17/2008 04:01:34 AM: > > I spent a lot of time & effort writing a thread-safe logger for our > > own internal use. > > Sounds as if it was more painful than I had expected.
It's been quite a while, so my memory is a little hazy, but IIRC much of the effort was expended around features that are specific to our own Antlibs; if you strip out that code it's probably easier to do than I remember.

It's going to take a while to get this contribution cleared through IBM's IP attorneys, so don't expect to see anything for a few months.

____________________________________________________________________________________________
Jeffrey E. (Jeff) Care	carej@...
IBM WebSphere Application Server	WAS Release Engineering

From forum: Ant - Dev

Re: [SPAM] Re: Ivy svn breaks ant-contrib svn

2008-07-17T16:21:13Z

On Thu, Jul 17, 2008 at 4:16 PM, Scheper, Erik-Berndt <
erik-berndt.scheper@...> wrote:

> I've been thinking about suggesting this before, but now that the trunk has
> broken (undesired) changes that worked fine in beta-2, it might be a good
> idea to postpone most of the outstanding issues for RC1 to a RC2 and release
> RC1 asap.

Well, IMO a RC should be, well, a release candidate. If you are sure it
won't become a release because there are bugs you absolutely want to get
fixed before the final release, I wouldn't call this a RC. That being said,
maybe we should release a beta 3 now, and still make the best efforts to get
rc1 out with the 18 corresponding issues fixed asap. The only problem I see
is that some committers are currently in vacation, so it will be more
difficult to get the votes for the release. But if enough committers (well,
even PMC members) answer they are ok, I'll try to cut a beta 3 next week
(despite my overloaded planning).

Xavier

>
> That would promote better testing of the 100+ bug-fixes and changes since
> beta-2. Incidentally, beta-2 is now 4 months old, which was also the
> timeframe between beta-1 and beta-2.
>
> Erik-Berndt
>
> ________________________________
>
> Van: Maarten Coene [mailto:maarten_coene@...]
> Verzonden: do 17-7-2008 11:45
> Aan: Ant Developers List
> Onderwerp: [SPAM] Re: Ivy svn breaks ant-contrib svn
>
>
>
> Just a wild guess, but maybe you could use IvyAntSettings again (like your
> original code was), but instead of calling the execute method you can
> register it yourself as Reference in the Project, something like:
>
> IvyAntSettings settings = new IvyAntSettings();
> settings.setXXX...
> getProject().addReference(settingsId, settings);
>
> Maarten
>
>
>
>
> ----- Original Message ----
> From: Stefan Bodewig <bodewig@...>
> To: dev@...
> Sent: Tuesday, July 15, 2008 2:13:10 PM
> Subject: Re: Ivy svn breaks ant-contrib svn
>
> On Tue, 15 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:
>
> > On Tue, Jul 15, 2008 at 9:23 AM, Stefan Bodewig <bodewig@...>
> wrote:
> >
> > > On Tue, 15 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:
> > >
> > > > On Tue, Jul 15, 2008 at 8:53 AM, Stefan Bodewig <bodewig@...>
> > > wrote:
> > > >
> > > > > Ant-contrib also invokes setId() on the task, which works fine with
> > > > > Ivy 2.0.0beta2 but fails with trunk.
> > > > >
> > > > > Could you please re-add the setid method?
> > > >
> > > > setId is now setSettingsId on IvyConfigure, which is more in
> > > > conformance with Ant, since we are not setting the id of the
> > > > task, but of the underneath datatype.
> > >
> > > OK, what can ant-contrib do if it wants to compile against Ivy
> > > 2.0.0beta2 and trunk with the same codebase?
> >
> > This is not straightforward, since we broke the API.
>
> Right, that's why Gump finds it 8-)
>
> Maybe you could throw in a deprecated setId() method that delegated to
> setSettingsId()? At least for the next beta so ant-contrib has a
> stable base to work from without resorting to reflection.
>
> I looked into the code to see what the id is used for. It is later
> used as the argument for IvyCacheFileset.setSettingsRef - this
> wouldn't work with a reference to the task but would require a
> reference to the settings, which now would exactly be what
> setSettingsId creates, right?
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>
>
>
> Disclaimer:
> This message contains information that may be privileged or confidential
> and is the property of Sogeti Nederland B.V. or its Group members. It is
> intended only for the person to whom it is addressed. If you are not the
> intended recipient, you are not authorized to read, print, retain, copy,
> disseminate, distribute, or use this message or any part thereof. If you
> receive this message in error, please notify the sender immediately and
> delete all copies of this message.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

From forum: Ant - Dev

RE: [SPAM] Re: Ivy svn breaks ant-contrib svn

2008-07-17T07:16:36Z

I've been thinking about suggesting this before, but now that the trunk has broken (undesired) changes that worked fine in beta-2, it might be a good idea to postpone most of the outstanding issues for RC1 to a RC2 and release RC1 asap.

That would promote better testing of the 100+ bug-fixes and changes since beta-2. Incidentally, beta-2 is now 4 months old, which was also the timeframe between beta-1 and beta-2.

Erik-Berndt

________________________________

Van: Maarten Coene [mailto:maarten_coene@...]
Verzonden: do 17-7-2008 11:45
Aan: Ant Developers List
Onderwerp: [SPAM] Re: Ivy svn breaks ant-contrib svn

Just a wild guess, but maybe you could use IvyAntSettings again (like your original code was), but instead of calling the execute method you can register it yourself as Reference in the Project, something like:

IvyAntSettings settings = new IvyAntSettings();
settings.setXXX...
getProject().addReference(settingsId, settings);

Maarten

----- Original Message ----
From: Stefan Bodewig <bodewig@...>
To: dev@...
Sent: Tuesday, July 15, 2008 2:13:10 PM
Subject: Re: Ivy svn breaks ant-contrib svn

On Tue, 15 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:

> On Tue, Jul 15, 2008 at 9:23 AM, Stefan Bodewig <bodewig@...> wrote:
>
> > On Tue, 15 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:
> >
> > > On Tue, Jul 15, 2008 at 8:53 AM, Stefan Bodewig <bodewig@...>
> > wrote:
> > >
> > > > Ant-contrib also invokes setId() on the task, which works fine with
> > > > Ivy 2.0.0beta2 but fails with trunk.
> > > >
> > > > Could you please re-add the setid method?
> > >
> > > setId is now setSettingsId on IvyConfigure, which is more in
> > > conformance with Ant, since we are not setting the id of the
> > > task, but of the underneath datatype.
> >
> > OK, what can ant-contrib do if it wants to compile against Ivy
> > 2.0.0beta2 and trunk with the same codebase?
>
> This is not straightforward, since we broke the API.

Right, that's why Gump finds it 8-)

Maybe you could throw in a deprecated setId() method that delegated to
setSettingsId()? At least for the next beta so ant-contrib has a
stable base to work from without resorting to reflection.

I looked into the code to see what the id is used for. It is later
used as the argument for IvyCacheFileset.setSettingsRef - this
wouldn't work with a reference to the task but would require a
reference to the settings, which now would exactly be what
setSettingsId creates, right?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Disclaimer:
This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

Re: Ivy svn breaks ant-contrib svn

2008-07-17T02:45:45Z

Just a wild guess, but maybe you could use IvyAntSettings again (like your original code was), but instead of calling the execute method you can register it yourself as Reference in the Project, something like:

IvyAntSettings settings = new IvyAntSettings();
settings.setXXX...
getProject().addReference(settingsId, settings);

Maarten

----- Original Message ----
From: Stefan Bodewig <bodewig@...>
To: dev@...
Sent: Tuesday, July 15, 2008 2:13:10 PM
Subject: Re: Ivy svn breaks ant-contrib svn

On Tue, 15 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:

From forum: Ant - Dev

Re: Ivy svn breaks ant-contrib svn

2008-07-17T02:24:41Z

On Thu, Jul 17, 2008 at 10:00 AM, Stefan Bodewig <bodewig@...> wrote:

> On Wed, 16 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:
>
> > Yes, I think setSettingsId is the good method to call, 2.0.0-beta2 was
> > broken in that sense. Introducing a setId method for backward
> compatiblity
> > with something broken in concept doesn't sound really nice IMO. We will
> > probably forget to remove it after, I don't like it too much. IMO
> antcontrib
> > should be built either against trunk, or against beta2, but not both.
> >
> > But maybe others have a different opinion?
>
> This is exactly the kind of change that Gump was designed to catch and
> I'm glad it did. I don't really have an opinion on the particular
> change but am a strong proponent of not breaking APIs in general (at
> least not without a deprecation period).

I agree in general, but Ivy 2 has been going in a deep code change, and we
decided to keep backward compatibility with 1.4 at ant tasks level, but not
at API level. We warned the users about that in the release notes, and
changing code in Ivy for backward compatibility with a beta version (which
in Ivy language is not a release candidate) sounds not like a good idea to
me. But once again I'm alone to decide, and if more people think it makes
sense, I won't object.

> Right now ant-contrib doesn't have anything but beta2 to build
> against, so it must use setId.

Indeed.

> Once the next Ivy release is available
> they (we, sometimes it's hard to wear different hats) can switch to
> setSettingsId - or more precisely must. This forces ant-contrib to
> lock step its release plan with Ivy's - if there was such a plan.

Yes, in a way. That's the problem of using a beta version as a dependency.
And that's also a problem of long release cycles, I'd really like to get Ivy
2 final released asap to avoid or at least reduce this kind of problem in
the future.

> I'd avoid using reflection and in this particular case don't really
> care too much, so I will simply keep Gump broken until Ivy has a new
> artifact ant-contrib can build against. It may be something you
> should keep in mind when preparing the release notes of the next Ivy
> release, though.

This sounds like a good option.

Xavier

>
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

From forum: Ant - Dev

Re: Logging and synchronization

2008-07-17T01:01:34Z

On Fri, 11 Jul 2008, Jeffrey E. Care <carej@...> wrote:

> I spent a lot of time & effort writing a thread-safe logger for our
> own internal use.

Sounds as if it was more painful than I had expected.

> If there's sufficient interest I'd be willing to get the ball
> rolling on getting the contribution approved by our internal IP
> folks...

I'd be interested.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

Re: Ivy svn breaks ant-contrib svn

2008-07-17T01:00:26Z

On Wed, 16 Jul 2008, Xavier Hanin <xavier.hanin@...> wrote:

> Yes, I think setSettingsId is the good method to call, 2.0.0-beta2 was
> broken in that sense. Introducing a setId method for backward compatiblity
> with something broken in concept doesn't sound really nice IMO. We will
> probably forget to remove it after, I don't like it too much. IMO antcontrib
> should be built either against trunk, or against beta2, but not both.
>
> But maybe others have a different opinion?

This is exactly the kind of change that Gump was designed to catch and
I'm glad it did. I don't really have an opinion on the particular
change but am a strong proponent of not breaking APIs in general (at
least not without a deprecation period).

Right now ant-contrib doesn't have anything but beta2 to build
against, so it must use setId. Once the next Ivy release is available
they (we, sometimes it's hard to wear different hats) can switch to
setSettingsId - or more precisely must. This forces ant-contrib to
lock step its release plan with Ivy's - if there was such a plan.

I'd avoid using reflection and in this particular case don't really
care too much, so I will simply keep Gump broken until Ivy has a new
artifact ant-contrib can build against. It may be something you
should keep in mind when preparing the release notes of the next Ivy
release, though.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

From forum: Ant - Dev

RE: Pass Quotes to arg line

2008-07-16T08:33:55Z

So, assuming one does this, how would one put quotes in place around
params?

On Wed, 16 Jul 2008, Karr, David wrote:

> As another poster pointed out, the correct solution is to use multiple
> "arg"s with "value" attributes, not trying to figure out how to get
> through the various escaping layers with the "line" attribute.
>
>> -----Original Message-----
>> From: Peters, John [mailto:John.Peters@...]
>> Sent: Tuesday, July 15, 2008 2:27 PM
>> To: user@...
>> Subject: Pass Quotes to arg line
>>
>> Hello,
>> I'm trying to pass quotes to the arg line for a parameter
>> that has spaces in it.
>> I've tried " but that didn't seem to work.
>> Also tried "" \".
>> Any suggestions?
>>
>> <target name="call_tfsbuild" depends="process_proj">
>> <exec executable="${os.tfsbuild}" failonerror="true">
>> <arg line="start ${os.tfsmstr} ${cc.vob} ${cc.proj}
>> /msBuildArguments:/p:LabelComment=Label for Build at
>> ${local.time.start}
>> " />
>> </exec>
>> </target>
>>
>>
>>
>> Blue Cross Blue Shield of Florida, Inc., and its subsidiary
>> and affiliate companies are not responsible for errors or
>> omissions in this e-mail message. Any personal comments made
>> in this e-mail do not reflect the views of Blue Cross Blue
>> Shield of Florida, Inc. The information contained in this
>> document may be confidential and intended solely for the use
>> of the individual or entity to whom it is addressed. This
>> document may contain material that is privileged or protected
>> from disclosure under applicable law. If you are not the
>> intended recipient or the individual responsible for
>> delivering to the intended recipient, please (1) be advised
>> that any use, dissemination, forwarding, or copying of this
>> document IS STRICTLY PROHIBITED; and (2) notify sender
>> immediately by telephone and destroy the document. THANK YOU.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@... For
>> additional commands, e-mail: user-help@...
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>
>

Scot P. Floess
27 Lake Royale
Louisburg, NC 27549

252-478-8087 (Home)
919-754-4592 (Work)

Chief Architect JPlate http://sourceforge.net/projects/jplate
Chief Architect JavaPIM http://sourceforge.net/projects/javapim

Architect Keros http://sourceforge.net/projects/keros

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

From forum: Ant - Users

Re: Trouble executing python script in Unix

2008-07-16T08:23:01Z

Got it :)

Somewhat round-about, but I wrote a small bash script that accepts two
arguments and wraps the first
one in <> and then executes the command:

--------------------------------------------------------
#!/bin/bash

input=$1
output=$2

./jsmin.py <$input>$output
--------------------------------------------------------

It's a little round-about, but it works, finally. I think I learned the same
lesson today.

Thanks André.

-Keith

On Wed, Jul 16, 2008 at 11:04 AM, André Pilz <andre.pilz@...> wrote:

> Hi,
>
> oh, the <|> problem. Today learned: Never ignore funny arguments.
>
> Maybe the output/input attributes of the <exec> task are helpful. In my
> cases I use a self-written ant task.
>
>
> Cheers,
> André
>
> Keith Hughitt schrieb:
>
>> Hi André,
>>
>> Thanks for the suggestion. Python does find the script: Adding a print
>> statement
>> in the python script shows up during the build. Originally I thought that
>> the issue might be
>> due to the script not finding the input file. I now think, however, it may
>> be due to how python
>> interprets the angle brackets.
>>
>> I once again added a "print sys.argv" which prints both the command
>> executed
>> as well
>> as any arguments passed to it. Running the ant build results in:
>>
>> [exec] Executing JSMin... arguments:
>> [exec] ['/var/www/hv/install/jsmin.py', '<proj-all.js>',
>> 'proj-all-min.js']
>>
>> Which I thought is what should be the output. However, running the same
>> script by itself,
>> the output (which actually goes to proj-all-min.js and not the
>> command-line)
>> is:
>>
>> Executing JSMin... arguments:
>> ['./jsmin.py']
>>
>>
>> It looks like what is happening is that angle-brackets and the following
>> argument
>> specify streams to use for input and output, but for some reason when the
>> script
>> is run by ant, they are not interpreted this way. Perhaps the console is
>> still interpreting
>> them as escaped brackets (< and >), instead of actual angle
>> brackets.
>> If that is
>> the case, it looks like I may be out of luck unless I rewrite the script
>> to
>> initiate the filestreams
>> in another way.
>>
>> The same script is available in other languages (Perl, etc), so I will try
>> another version that
>> doesn't make use of the angle-brackets. Then I should be able to tell if
>> this is actually the
>> root of the problem.
>>
>> Thanks for taking the time to take a look at my problem, and for providing
>> feedback André.
>> And sorry for calling you Luis by accident last time.. Got my emails mixed
>> up :P
>>
>> Take care,
>> Keith
>>
>>
>> On Wed, Jul 16, 2008 at 9:47 AM, André Pilz <andre.pilz@...>
>> wrote:
>>
>> Seems like python doesn't find the script (because there is no error
>>> message).
>>>
>>> Possible solutions:
>>>
>>> - use absolute path for script location:
>>> <arg value="${basedir}/install/tools/jsmin.py"/>
>>>
>>> - call script directly (like your working test.py):
>>> <exec executable="${basedir}/install/tools/jsmin.py"
>>> resolveexecutable="true">
>>> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
>>> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
>>> </exec>
>>>
>>> I also note the double slash in the last argument.
>>>
>>>
>>> Cheers,
>>> André
>>>
>>> Keith Hughitt schrieb:
>>>
>>> Hi Luis,
>>>>
>>>> Thanks for the suggestion. I had tried using "ant -v" before, and also
>>>> redirecting the output, but was not aware of the '-d' parameter.
>>>> The script *should* result in a new file, "proj-all-min.js" being
>>>> created.
>>>> The file is only created when I run the script manually, however,
>>>> and not when I call the script during an Ant build.
>>>>
>>>> Here is the relevant section of my build.xml as well as the complete
>>>> output
>>>> from execution:
>>>>
>>>> ========= BEGIN build.xml ===============
>>>> <project name="proj" default="build" basedir="../">
>>>> .
>>>> .
>>>> .
>>>> <target name="build">
>>>>
>>>> 
>>>> <mkdir dir="lib/proj/build"/>
>>>>
>>>> 
>>>> <exec dir="install" executable="test.py"
>>>> resolveexecutable="true"/>
>>>>
>>>> 
>>>> <exec dir="./" executable="python" resolveexecutable="true">
>>>> <arg value="install/tools/jsmin.py"/>
>>>> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
>>>> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
>>>> </exec>
>>>>
>>>>
>>>> ========= END build.xml ===========
>>>>
>>>> Note: Ant is run from /install, and thus "../" points to the project's
>>>> root
>>>> directory.
>>>> The relevant python script is located in /install/tools, and
>>>> "test.py" is a dummy
>>>> script located in /install that I used to test a simple case of
>>>> script execution.
>>>>
>>>> =========BEGIN OUTPUT===========
>>>>
>>>> $:/var/www/hv/install$ ant -d
>>>> Apache Ant version 1.7.0 compiled on August 29 2007
>>>> Buildfile: build.xml
>>>> Adding reference: ant.PropertyHelper
>>>> Detected Java version: 1.6 in: /usr/lib/jvm/java-6-sun-1.6.0.06/jre
>>>> Detected OS: Linux
>>>> Adding reference: ant.ComponentHelper
>>>> Setting ro project property: ant.file -> /var/www/hv/install/build.xml
>>>> Adding reference: ant.projectHelper
>>>> Adding reference: ant.parsing.context
>>>> Adding reference: ant.targets
>>>> parsing buildfile /var/www/hv/install/build.xml with URI =
>>>> file:/var/www/hv/install/build.xml
>>>> Setting ro project property: ant.project.name -> proj
>>>> Adding reference: proj
>>>> Setting ro project property: ant.file.proj ->
>>>> /var/www/hv/install/build.xml
>>>> Project base dir set to: /var/www/hv
>>>> +Target:
>>>> +Target: build
>>>> [antlib:org.apache.tools.ant] Could not load definitions from resource
>>>> org/apache/tools/ant/antlib.xml. It could not be found.
>>>> Attempting to create object of type
>>>> org.apache.tools.ant.helper.DefaultExecutor
>>>> Adding reference: ant.executor
>>>> Build sequence for target(s) `build' is [build]
>>>> Complete build sequence is [build, ]
>>>>
>>>> build:
>>>> [exec] Current OS is Linux
>>>> [exec] Executing '/var/www/hv/install/test.py'
>>>> [exec] The ' characters around the executable and arguments are
>>>> [exec] not part of the command.
>>>> Execute:Java13CommandLauncher: Executing '/var/www/hv/install/test.py'
>>>> The ' characters around the executable and arguments are
>>>> not part of the command.
>>>> [exec] Hello World
>>>> [exec] Current OS is Linux
>>>> [exec] Executing 'python' with arguments:
>>>> [exec] 'install/tools/jsmin.py'
>>>> [exec] '</var/www/hv/lib/proj/build/proj-all.js>'
>>>> [exec] '/var/www/hv/lib/proj//build/proj-all-min.js'
>>>> [exec]
>>>> [exec] The ' characters around the executable and arguments are
>>>> [exec] not part of the command.
>>>> Execute:Java13CommandLauncher: Executing 'python' with arguments:
>>>> 'install/tools/jsmin.py'
>>>> '</var/www/hv/lib/proj/build/proj-all.js>'
>>>> '/var/www/hv/lib/proj//build/proj-all-min.js'
>>>>
>>>> The ' characters around the executable and arguments are
>>>> not part of the command.
>>>>
>>>> BUILD SUCCESSFUL
>>>> Total time: 0 seconds
>>>>
>>>> =========END OUTPUT===========
>>>>
>>>>
>>>> Any ideas?
>>>>
>>>>
>>>> Thanks,
>>>> Keith
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jul 16, 2008 at 5:56 AM, André Pilz <andre.pilz@...>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> need more info to help you. Use "ant -d" to get the command line and
>>>>> the
>>>>> arguments how python is called. How exactly does it not work? Any error
>>>>> message?
>>>>>
>>>>> Cheers,
>>>>> André
>>>>>
>>>>> Keith Hughitt schrieb:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I've just recently started using Ant on Linux, and so far it has been
>>>>>> really
>>>>>> amazing. I've run into
>>>>>> one problem, however, that I haven't been able to get past.
>>>>>>
>>>>>> I would like to call an external script (a python script to minimize
>>>>>> some
>>>>>> JavaScript files),
>>>>>> but have not been able to get it to execute properly. I searched
>>>>>> around
>>>>>> some, and found
>>>>>> an earlier thread (http://marc.info/?l=ant-user&m=115078380228196&w=2
>>>>>> )
>>>>>> where someone with a similar problem was able to fix things setting
>>>>>> "resolveexecutable" to true.
>>>>>> This works for me when I try running a dummy script with no arguments,
>>>>>> e.g:
>>>>>>
>>>>>> ...
>>>>>> <exec dir="./" executable="test.py" resolveexecutable="true"/>
>>>>>> ...
>>>>>>
>>>>>> [exec] Hello World
>>>>>>
>>>>>>
>>>>>> When I try and do something requiring command-line arguments though I
>>>>>> can't
>>>>>> get it to work:
>>>>>>
>>>>>> <exec dir="./" executable="python" resolveexecutable="true">
>>>>>> <arg value="install/tools/jsmin.py"/>
>>>>>> <arg value="<${libs}/build/test.js>"/>
>>>>>> <arg value="${libs}/build/testl-min.js"/>
>>>>>> </exec>
>>>>>>
>>>>>> I've tried executing both "python" (and passing the scripts name as an
>>>>>> argument), and the script itself.
>>>>>> Nothing seems to work. The command executes fine from the
>>>>>> command-line,
>>>>>> and
>>>>>> what even more, when
>>>>>> I print the arguments passed to the python script using argv, and then
>>>>>> string them together and run them
>>>>>> it works fine, but still no luck when I try to get it working through
>>>>>> ant.
>>>>>>
>>>>>> Anyone have any suggestions as to what might be the problem?
>>>>>>
>>>>>> Any help would be greatly appreciated.
>>>>>>
>>>>>> Thanks,
>>>>>> Keith
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>> To unsubscribe, e-mail: user-unsubscribe@...
>>>>> For additional commands, e-mail: user-help@...
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@...
>>> For additional commands, e-mail: user-help@...
>>>
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>
>

From forum: Ant - Users

RE: Pass Quotes to arg line

2008-07-16T08:17:35Z

As another poster pointed out, the correct solution is to use multiple
"arg"s with "value" attributes, not trying to figure out how to get
through the various escaping layers with the "line" attribute.

> -----Original Message-----
> From: Peters, John [mailto:John.Peters@...]
> Sent: Tuesday, July 15, 2008 2:27 PM
> To: user@...
> Subject: Pass Quotes to arg line
>
> Hello,
> I'm trying to pass quotes to the arg line for a parameter
> that has spaces in it.
> I've tried " but that didn't seem to work.
> Also tried "" \".
> Any suggestions?
>
> <target name="call_tfsbuild" depends="process_proj">
> <exec executable="${os.tfsbuild}" failonerror="true">
> <arg line="start ${os.tfsmstr} ${cc.vob} ${cc.proj}
> /msBuildArguments:/p:LabelComment=Label for Build at
> ${local.time.start}
> " />
> </exec>
> </target>
>
>
>
> Blue Cross Blue Shield of Florida, Inc., and its subsidiary
> and affiliate companies are not responsible for errors or
> omissions in this e-mail message. Any personal comments made
> in this e-mail do not reflect the views of Blue Cross Blue
> Shield of Florida, Inc. The information contained in this
> document may be confidential and intended solely for the use
> of the individual or entity to whom it is addressed. This
> document may contain material that is privileged or protected
> from disclosure under applicable law. If you are not the
> intended recipient or the individual responsible for
> delivering to the intended recipient, please (1) be advised
> that any use, dissemination, forwarding, or copying of this
> document IS STRICTLY PROHIBITED; and (2) notify sender
> immediately by telephone and destroy the document. THANK YOU.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@... For
> additional commands, e-mail: user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

From forum: Ant - Users

How to pass an unset property with inheritall=false

2008-07-16T08:06:20Z

Hello,

I want to use antcall together with inheritall=false:
<antcall target="junittests" inheritall="false" >
<param name="paramsometimesunset" value="${paramsometimesunset}" />
</antcall>

There are some targets that dont run, when paramsometimesunset is unset.
If I pass the parameter like this and paramsometimesunset is unset, it is set in the called target.
But I want it to be just the same value (either unset or some value)

Any ideas?

--
Jürgen Knuplesch

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

From forum: Ant - Users

Re: Trouble executing python script in Unix

2008-07-16T08:04:59Z

Hi,

oh, the <|> problem. Today learned: Never ignore funny arguments.

Maybe the output/input attributes of the <exec> task are helpful. In my
cases I use a self-written ant task.

Cheers,
André

Keith Hughitt schrieb:

> Hi André,
>
> Thanks for the suggestion. Python does find the script: Adding a print
> statement
> in the python script shows up during the build. Originally I thought that
> the issue might be
> due to the script not finding the input file. I now think, however, it may
> be due to how python
> interprets the angle brackets.
>
> I once again added a "print sys.argv" which prints both the command executed
> as well
> as any arguments passed to it. Running the ant build results in:
>
> [exec] Executing JSMin... arguments:
> [exec] ['/var/www/hv/install/jsmin.py', '<proj-all.js>', 'proj-all-min.js']
>
> Which I thought is what should be the output. However, running the same
> script by itself,
> the output (which actually goes to proj-all-min.js and not the command-line)
> is:
>
> Executing JSMin... arguments:
> ['./jsmin.py']
>
>
> It looks like what is happening is that angle-brackets and the following
> argument
> specify streams to use for input and output, but for some reason when the
> script
> is run by ant, they are not interpreted this way. Perhaps the console is
> still interpreting
> them as escaped brackets (< and >), instead of actual angle brackets.
> If that is
> the case, it looks like I may be out of luck unless I rewrite the script to
> initiate the filestreams
> in another way.
>
> The same script is available in other languages (Perl, etc), so I will try
> another version that
> doesn't make use of the angle-brackets. Then I should be able to tell if
> this is actually the
> root of the problem.
>
> Thanks for taking the time to take a look at my problem, and for providing
> feedback André.
> And sorry for calling you Luis by accident last time.. Got my emails mixed
> up :P
>
> Take care,
> Keith
>
>
> On Wed, Jul 16, 2008 at 9:47 AM, André Pilz <andre.pilz@...> wrote:
>
>> Seems like python doesn't find the script (because there is no error
>> message).
>>
>> Possible solutions:
>>
>> - use absolute path for script location:
>> <arg value="${basedir}/install/tools/jsmin.py"/>
>>
>> - call script directly (like your working test.py):
>> <exec executable="${basedir}/install/tools/jsmin.py"
>> resolveexecutable="true">
>> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
>> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
>> </exec>
>>
>> I also note the double slash in the last argument.
>>
>>
>> Cheers,
>> André
>>
>> Keith Hughitt schrieb:
>>
>>> Hi Luis,
>>>
>>> Thanks for the suggestion. I had tried using "ant -v" before, and also
>>> redirecting the output, but was not aware of the '-d' parameter.
>>> The script *should* result in a new file, "proj-all-min.js" being created.
>>> The file is only created when I run the script manually, however,
>>> and not when I call the script during an Ant build.
>>>
>>> Here is the relevant section of my build.xml as well as the complete
>>> output
>>> from execution:
>>>
>>> ========= BEGIN build.xml ===============
>>> <project name="proj" default="build" basedir="../">
>>> .
>>> .
>>> .
>>> <target name="build">
>>>
>>> 
>>> <mkdir dir="lib/proj/build"/>
>>>
>>> 
>>> <exec dir="install" executable="test.py" resolveexecutable="true"/>
>>>
>>> 
>>> <exec dir="./" executable="python" resolveexecutable="true">
>>> <arg value="install/tools/jsmin.py"/>
>>> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
>>> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
>>> </exec>
>>>
>>>
>>> ========= END build.xml ===========
>>>
>>> Note: Ant is run from /install, and thus "../" points to the project's
>>> root
>>> directory.
>>> The relevant python script is located in /install/tools, and
>>> "test.py" is a dummy
>>> script located in /install that I used to test a simple case of
>>> script execution.
>>>
>>> =========BEGIN OUTPUT===========
>>>
>>> $:/var/www/hv/install$ ant -d
>>> Apache Ant version 1.7.0 compiled on August 29 2007
>>> Buildfile: build.xml
>>> Adding reference: ant.PropertyHelper
>>> Detected Java version: 1.6 in: /usr/lib/jvm/java-6-sun-1.6.0.06/jre
>>> Detected OS: Linux
>>> Adding reference: ant.ComponentHelper
>>> Setting ro project property: ant.file -> /var/www/hv/install/build.xml
>>> Adding reference: ant.projectHelper
>>> Adding reference: ant.parsing.context
>>> Adding reference: ant.targets
>>> parsing buildfile /var/www/hv/install/build.xml with URI =
>>> file:/var/www/hv/install/build.xml
>>> Setting ro project property: ant.project.name -> proj
>>> Adding reference: proj
>>> Setting ro project property: ant.file.proj ->
>>> /var/www/hv/install/build.xml
>>> Project base dir set to: /var/www/hv
>>> +Target:
>>> +Target: build
>>> [antlib:org.apache.tools.ant] Could not load definitions from resource
>>> org/apache/tools/ant/antlib.xml. It could not be found.
>>> Attempting to create object of type
>>> org.apache.tools.ant.helper.DefaultExecutor
>>> Adding reference: ant.executor
>>> Build sequence for target(s) `build' is [build]
>>> Complete build sequence is [build, ]
>>>
>>> build:
>>> [exec] Current OS is Linux
>>> [exec] Executing '/var/www/hv/install/test.py'
>>> [exec] The ' characters around the executable and arguments are
>>> [exec] not part of the command.
>>> Execute:Java13CommandLauncher: Executing '/var/www/hv/install/test.py'
>>> The ' characters around the executable and arguments are
>>> not part of the command.
>>> [exec] Hello World
>>> [exec] Current OS is Linux
>>> [exec] Executing 'python' with arguments:
>>> [exec] 'install/tools/jsmin.py'
>>> [exec] '</var/www/hv/lib/proj/build/proj-all.js>'
>>> [exec] '/var/www/hv/lib/proj//build/proj-all-min.js'
>>> [exec]
>>> [exec] The ' characters around the executable and arguments are
>>> [exec] not part of the command.
>>> Execute:Java13CommandLauncher: Executing 'python' with arguments:
>>> 'install/tools/jsmin.py'
>>> '</var/www/hv/lib/proj/build/proj-all.js>'
>>> '/var/www/hv/lib/proj//build/proj-all-min.js'
>>>
>>> The ' characters around the executable and arguments are
>>> not part of the command.
>>>
>>> BUILD SUCCESSFUL
>>> Total time: 0 seconds
>>>
>>> =========END OUTPUT===========
>>>
>>>
>>> Any ideas?
>>>
>>>
>>> Thanks,
>>> Keith
>>>
>>>
>>>
>>>
>>> On Wed, Jul 16, 2008 at 5:56 AM, André Pilz <andre.pilz@...>
>>> wrote:
>>>
>>> Hi,
>>>> need more info to help you. Use "ant -d" to get the command line and the
>>>> arguments how python is called. How exactly does it not work? Any error
>>>> message?
>>>>
>>>> Cheers,
>>>> André
>>>>
>>>> Keith Hughitt schrieb:
>>>>
>>>> Hi all,
>>>>
>>>>> I've just recently started using Ant on Linux, and so far it has been
>>>>> really
>>>>> amazing. I've run into
>>>>> one problem, however, that I haven't been able to get past.
>>>>>
>>>>> I would like to call an external script (a python script to minimize
>>>>> some
>>>>> JavaScript files),
>>>>> but have not been able to get it to execute properly. I searched around
>>>>> some, and found
>>>>> an earlier thread (http://marc.info/?l=ant-user&m=115078380228196&w=2)
>>>>> where someone with a similar problem was able to fix things setting
>>>>> "resolveexecutable" to true.
>>>>> This works for me when I try running a dummy script with no arguments,
>>>>> e.g:
>>>>>
>>>>> ...
>>>>> <exec dir="./" executable="test.py" resolveexecutable="true"/>
>>>>> ...
>>>>>
>>>>> [exec] Hello World
>>>>>
>>>>>
>>>>> When I try and do something requiring command-line arguments though I
>>>>> can't
>>>>> get it to work:
>>>>>
>>>>> <exec dir="./" executable="python" resolveexecutable="true">
>>>>> <arg value="install/tools/jsmin.py"/>
>>>>> <arg value="<${libs}/build/test.js>"/>
>>>>> <arg value="${libs}/build/testl-min.js"/>
>>>>> </exec>
>>>>>
>>>>> I've tried executing both "python" (and passing the scripts name as an
>>>>> argument), and the script itself.
>>>>> Nothing seems to work. The command executes fine from the command-line,
>>>>> and
>>>>> what even more, when
>>>>> I print the arguments passed to the python script using argv, and then
>>>>> string them together and run them
>>>>> it works fine, but still no luck when I try to get it working through
>>>>> ant.
>>>>>
>>>>> Anyone have any suggestions as to what might be the problem?
>>>>>
>>>>> Any help would be greatly appreciated.
>>>>>
>>>>> Thanks,
>>>>> Keith
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@...
>>>> For additional commands, e-mail: user-help@...
>>>>
>>>>
>>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@...
>> For additional commands, e-mail: user-help@...
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...

From forum: Ant - Users

Re: Trouble executing python script in Unix

2008-07-16T07:51:08Z

Hi André,

Thanks for the suggestion. Python does find the script: Adding a print
statement
in the python script shows up during the build. Originally I thought that
the issue might be
due to the script not finding the input file. I now think, however, it may
be due to how python
interprets the angle brackets.

I once again added a "print sys.argv" which prints both the command executed
as well
as any arguments passed to it. Running the ant build results in:

[exec] Executing JSMin... arguments:
[exec] ['/var/www/hv/install/jsmin.py', '<proj-all.js>', 'proj-all-min.js']

Which I thought is what should be the output. However, running the same
script by itself,
the output (which actually goes to proj-all-min.js and not the command-line)
is:

Executing JSMin... arguments:
['./jsmin.py']

It looks like what is happening is that angle-brackets and the following
argument
specify streams to use for input and output, but for some reason when the
script
is run by ant, they are not interpreted this way. Perhaps the console is
still interpreting
them as escaped brackets (< and >), instead of actual angle brackets.
If that is
the case, it looks like I may be out of luck unless I rewrite the script to
initiate the filestreams
in another way.

The same script is available in other languages (Perl, etc), so I will try
another version that
doesn't make use of the angle-brackets. Then I should be able to tell if
this is actually the
root of the problem.

Thanks for taking the time to take a look at my problem, and for providing
feedback André.
And sorry for calling you Luis by accident last time.. Got my emails mixed
up :P

Take care,
Keith

On Wed, Jul 16, 2008 at 9:47 AM, André Pilz <andre.pilz@...> wrote:

> Seems like python doesn't find the script (because there is no error
> message).
>
> Possible solutions:
>
> - use absolute path for script location:
> <arg value="${basedir}/install/tools/jsmin.py"/>
>
> - call script directly (like your working test.py):
> <exec executable="${basedir}/install/tools/jsmin.py"
> resolveexecutable="true">
> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
> </exec>
>
> I also note the double slash in the last argument.
>
>
> Cheers,
> André
>
> Keith Hughitt schrieb:
>
>> Hi Luis,
>>
>> Thanks for the suggestion. I had tried using "ant -v" before, and also
>> redirecting the output, but was not aware of the '-d' parameter.
>> The script *should* result in a new file, "proj-all-min.js" being created.
>> The file is only created when I run the script manually, however,
>> and not when I call the script during an Ant build.
>>
>> Here is the relevant section of my build.xml as well as the complete
>> output
>> from execution:
>>
>> ========= BEGIN build.xml ===============
>> <project name="proj" default="build" basedir="../">
>> .
>> .
>> .
>> <target name="build">
>>
>> 
>> <mkdir dir="lib/proj/build"/>
>>
>> 
>> <exec dir="install" executable="test.py" resolveexecutable="true"/>
>>
>> 
>> <exec dir="./" executable="python" resolveexecutable="true">
>> <arg value="install/tools/jsmin.py"/>
>> <arg value="</var/www/hv/lib/proj/build/proj-all.js>"/>
>> <arg value="/var/www/hv/lib/proj//build/proj-all-min.js"/>
>> </exec>
>>
>>
>> ========= END build.xml ===========
>>
>> Note: Ant is run from /install, and thus "../" points to the project's
>> root
>> directory.
>> The relevant python script is located in /install/tools, and
>> "test.py" is a dummy
>> script located in /install that I used to test a simple case of
>> script execution.
>>
>> =========BEGIN OUTPUT===========
>>
>> $:/var/www/hv/install$ ant -d
>> Apache Ant version 1.7.0 compiled on August 29 2007
>> Buildfile: build.xml
>> Adding reference: ant.PropertyHelper
>> Detected Java version: 1.6 in: /usr/lib/jvm/java-6-sun-1.6.0.06/jre
>> Detected OS: Linux
>> Adding reference: ant.ComponentHelper
>> Setting ro project property: ant.file -> /var/www/hv/install/build.xml
>> Adding reference: ant.projectHelper
>> Adding reference: ant.parsing.context
>> Adding reference: ant.targets
>> parsing buildfile /var/www/hv/install/build.xml with URI =
>> file:/var/www/hv/install/build.xml
>> Setting ro project property: ant.project.name -> proj
>> Adding reference: proj
>> Setting ro project property: ant.file.proj ->
>> /var/www/hv/install/build.xml
>> Project base dir set to: /var/www/hv
>> +Target:
>> +Target: build
>> [antlib:org.apache.tools.ant] Could not load definitions from resource
>> org/apache/tools/ant/antlib.xml. It could not be found.
>> Attempting to create object of type
>> org.apache.tools.ant.helper.DefaultExecutor
>> Adding reference: ant.executor
>> Build sequence for target(s) `build' is [build]
>> Complete build sequence is [build, ]
>>
>> build:
>> [exec] Current OS is Linux
>> [exec] Executing '/var/www/hv/install/test.py'
>> [exec] The ' characters around the executable and arguments are
>> [exec] not part of the command.
>> Execute:Java13CommandLauncher: Executing '/var/www/hv/install/test.py'
>> The ' characters around the executable and arguments are
>> not part of the command.
>> [exec] Hello World
>> [exec] Current OS is Linux
>> [exec] Executing 'python' with arguments:
>> [exec] 'install/tools/jsmin.py'
>> [exec] '</var/www/hv/lib/proj/build/proj-all.js>'
>> [exec] '/var/www/hv/lib/proj//build/proj-all-min.js'
>> [exec]
>> [exec] The ' characters around the executable and arguments are
>> [exec] not part of the command.
>> Execute:Java13CommandLauncher: Executing 'python' with arguments:
>> 'install/tools/jsmin.py'
>> '</var/www/hv/lib/proj/build/proj-all.js>'
>> '/var/www/hv/lib/proj//build/proj-all-min.js'
>>
>> The ' characters around the executable and arguments are
>> not part of the command.
>>
>> BUILD SUCCESSFUL
>> Total time: 0 seconds
>>
>> =========END OUTPUT===========
>>
>>
>> Any ideas?
>>
>>
>> Thanks,
>> Keith
>>
>>
>>
>>
>> On Wed, Jul 16, 2008 at 5:56 AM, André Pilz <andre.pilz@...>
>> wrote:
>>
>> Hi,
>>>
>>> need more info to help you. Use "ant -d" to get the command line and the
>>> arguments how python is called. How exactly does it not work? Any error
>>> message?
>>>
>>> Cheers,
>>> André
>>>
>>> Keith Hughitt schrieb:
>>>
>>> Hi all,
>>>
>>>> I've just recently started using Ant on Linux, and so far it has been
>>>> really
>>>> amazing. I've run into
>>>> one problem, however, that I haven't been able to get past.
>>>>
>>>> I would like to call an external script (a python script to minimize
>>>> some
>>>> JavaScript files),
>>>> but have not been able to get it to execute properly. I searched around
>>>> some, and found
>>>> an earlier thread (http://marc.info/?l=ant-user&m=115078380228196&w=2)
>>>> where someone with a similar problem was able to fix things setting
>>>> "resolveexecutable" to true.
>>>> This works for me when I try running a dummy script with no arguments,
>>>> e.g:
>>>>
>>>> ...
>>>> <exec dir="./" executable="test.py" resolveexecutable="true"/>
>>>> ...
>>>>
>>>> [exec] Hello World
>>>>
>>>>
>>>> When I try and do something requiring command-line arguments though I
>>>> can't
>>>> get it to work:
>>>>
>>>> <exec dir="./" executable="python" resolveexecutable="true">
>>>> <arg value="install/tools/jsmin.py"/>
>>>> <arg value="<${libs}/build/test.js>"/>
>>>> <arg value="${libs}/build/testl-min.js"/>
>>>> </exec>
>>>>
>>>> I've tried executing both "python" (and passing the scripts name as an
>>>> argument), and the script itself.
>>>> Nothing seems to work. The command executes fine from the command-line,
>>>> and
>>>> what even more, when
>>>> I print the arguments passed to the python script using argv, and then
>>>> string them together and run them
>>>> it works fine, but still no luck when I try to get it working through
>>>> ant.
>>>>
>>>> Anyone have any suggestions as to what might be the problem?
>>>>
>>>> Any help would be greatly appreciated.
>>>>
>>>> Thanks,
>>>> Keith
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@...
>>> For additional commands, e-mail: user-help@...
>>>
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@...
> For additional commands, e-mail: user-help@...
>
>

From forum: Ant - Users