Quantcast

Target unless question

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Target unless question

Scot P. Floess-2
All:

I was under the impression that using an unless attribute on a target will
not run the target if that property is set...  However, if there are is a
depends attribute defined, the targets in the depend are run regardless?

Is this correct?

For example consider the following:

<project default="C">
     <target name="A">
         <echo message = "A"/>
     </target>

     <target name="B">
         <echo message = "B"/>
     </target>

     <target name="C" unless = "stop" depends="A, B"/>
</project>

When I run as either:

ant -Dstop="true"

-or-

ant -Dstop=true

I get the following results:

Buildfile: build.xml

A:
      [echo] A

B:
      [echo] B

C:

In reading the online docs, it gave me the impression the atarget would
not run:  "A target also has the ability to perform its execution if (or
unless) a property has been set."

So, the question is - is depends taking precedence over unless?

Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-890-8117 (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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Target unless question

Shawn Castrianni
The if/unless apply to the target they are specified on ONLY.  They do not have any effect on the depends targets.  I don't like this either.  I posted about this very subject earlier this year.  Here is a link to it:

http://www.nabble.com/ANT-enhancements-td24028826.html


---
Shawn Castrianni


-----Original Message-----
From: Scot P. Floess [mailto:[hidden email]]
Sent: Thursday, August 13, 2009 2:09 PM
To: [hidden email]
Subject: Target unless question

All:

I was under the impression that using an unless attribute on a target will
not run the target if that property is set...  However, if there are is a
depends attribute defined, the targets in the depend are run regardless?

Is this correct?

For example consider the following:

<project default="C">
     <target name="A">
         <echo message = "A"/>
     </target>

     <target name="B">
         <echo message = "B"/>
     </target>

     <target name="C" unless = "stop" depends="A, B"/>
</project>

When I run as either:

ant -Dstop="true"

-or-

ant -Dstop=true

I get the following results:

Buildfile: build.xml

A:
      [echo] A

B:
      [echo] B

C:

In reading the online docs, it gave me the impression the atarget would
not run:  "A target also has the ability to perform its execution if (or
unless) a property has been set."

So, the question is - is depends taking precedence over unless?

Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-890-8117 (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: [hidden email]
For additional commands, e-mail: [hidden email]

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Target unless question

Scot P. Floess-2

Shawn:

Thanks a bunch...

So, I just refactored some of my targets - I have some
preprocess/process/postprocess targets and a "catch all" that depends on
the aforementioned.  I was "hoping" to selectively skip the processing
assuming a property was set - oh well.  Guess I'll add a depends where
appropriate - arg :(

Anyway - thanks for the prompt reply...  I thought as much...but wanted to
double check ;)

Flossy

On Thu, 13 Aug 2009, Shawn Castrianni wrote:

> The if/unless apply to the target they are specified on ONLY.  They do not have any effect on the depends targets.  I don't like this either.  I posted about this very subject earlier this year.  Here is a link to it:
>
> http://www.nabble.com/ANT-enhancements-td24028826.html
>
>
> ---
> Shawn Castrianni
>
>
> -----Original Message-----
> From: Scot P. Floess [mailto:[hidden email]]
> Sent: Thursday, August 13, 2009 2:09 PM
> To: [hidden email]
> Subject: Target unless question
>
> All:
>
> I was under the impression that using an unless attribute on a target will
> not run the target if that property is set...  However, if there are is a
> depends attribute defined, the targets in the depend are run regardless?
>
> Is this correct?
>
> For example consider the following:
>
> <project default="C">
>     <target name="A">
>         <echo message = "A"/>
>     </target>
>
>     <target name="B">
>         <echo message = "B"/>
>     </target>
>
>     <target name="C" unless = "stop" depends="A, B"/>
> </project>
>
> When I run as either:
>
> ant -Dstop="true"
>
> -or-
>
> ant -Dstop=true
>
> I get the following results:
>
> Buildfile: build.xml
>
> A:
>      [echo] A
>
> B:
>      [echo] B
>
> C:
>
> In reading the online docs, it gave me the impression the atarget would
> not run:  "A target also has the ability to perform its execution if (or
> unless) a property has been set."
>
> So, the question is - is depends taking precedence over unless?
>
> Scot P. Floess
> 27 Lake Royale
> Louisburg, NC  27549
>
> 252-478-8087 (Home)
> 919-890-8117 (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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> ----------------------------------------------------------------------
> This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-890-8117 (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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Target unless question

David Weintraub
In reply to this post by Scot P. Floess-2
On Thu, Aug 13, 2009 at 3:09 PM, Scot P. Floess <[hidden email]> wrote:

>
> I was under the impression that using an unless attribute on a target will
> not run the target if that property is set...  However, if there are is a
> depends attribute defined, the targets in the depend are run regardless?
>

Remember: Ant is not a programming language, but a build system that uses a
dependency matrix to determine the build order. Unlike a programming
language, you do not specify the actual build order of your targets.
Instead, you merely state that one target depends upon another. Ant then
uses this information to actually determine the build order. Ant builds this
dependency matrix first before even looking at what is required to execute
the targets.

Your example, although is an excellent test, isn't that realistic since you
are passing the "stop" property on the command line itself. More likely, the
property is set by a previous dependent target execution.

However, let's assume that I do want to use that property on the command
line to determine whether or not to execute a specific target. Let's say
that my build file looks like this:

<project>
    <target name="compile"/>
    <target name="package
        depends="compile"/>
    <target name="compress"
        unless="dont-compress"
        depends="package"/>
    <target name="deploy"
        depends="compress"/>
</project>

In this example, I want to execute my "deploy" target. Normally, I want to
do my compress step which removes debugging information from my software
package.

However, sometimes, for debugging purposes, I need to install my package
with debugging information. I could execute this:

$ ant -Ddont-compress deploy

In this case, I do want to execute my "compile" and "package" targets before
I do my deployment. However, I don't want the compress target to execute. If
I pre-tested my property "dont-compress" and because of that, I decided not
to execute my compile and package, the deploy target would fail.

--
David Weintraub
[hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Target unless question

Scot P. Floess-2

David:

Thanks - I know all this :)

I didn't go into much explanation - just simplified it down...

But, to be specific - I have this build environment with many empty
targets that are later defined (by scripts who import this one) that do processing
specific to the target - for example I have the following targets:

release-source.preprocess (empty target), release-source.process (has a
default implementation to release source),
release-source.post-process (empty target) and finally release-source
(depends on release-source.preprocess, release-source.process and
release-source.postprocess).  I also like to include a SKIP property that
if set, will skip a target.  I had the unless on, for example,
the release-source target (hoping it'd skip the 3 depends)...

The idea with the pre/post process targets are - if you like the default
implementation of process but need to add some additional functionality
either before or after - one provides the targets accordingly.

Anyway - thanks for the reply - you always have great explanations :)

Flossy


On Thu, 13 Aug 2009, David Weintraub wrote:

> On Thu, Aug 13, 2009 at 3:09 PM, Scot P. Floess <[hidden email]> wrote:
>
>>
>> I was under the impression that using an unless attribute on a target will
>> not run the target if that property is set...  However, if there are is a
>> depends attribute defined, the targets in the depend are run regardless?
>>
>
> Remember: Ant is not a programming language, but a build system that uses a
> dependency matrix to determine the build order. Unlike a programming
> language, you do not specify the actual build order of your targets.
> Instead, you merely state that one target depends upon another. Ant then
> uses this information to actually determine the build order. Ant builds this
> dependency matrix first before even looking at what is required to execute
> the targets.
>
> Your example, although is an excellent test, isn't that realistic since you
> are passing the "stop" property on the command line itself. More likely, the
> property is set by a previous dependent target execution.
>
> However, let's assume that I do want to use that property on the command
> line to determine whether or not to execute a specific target. Let's say
> that my build file looks like this:
>
> <project>
>    <target name="compile"/>
>    <target name="package
>        depends="compile"/>
>    <target name="compress"
>        unless="dont-compress"
>        depends="package"/>
>    <target name="deploy"
>        depends="compress"/>
> </project>
>
> In this example, I want to execute my "deploy" target. Normally, I want to
> do my compress step which removes debugging information from my software
> package.
>
> However, sometimes, for debugging purposes, I need to install my package
> with debugging information. I could execute this:
>
> $ ant -Ddont-compress deploy
>
> In this case, I do want to execute my "compile" and "package" targets before
> I do my deployment. However, I don't want the compress target to execute. If
> I pre-tested my property "dont-compress" and because of that, I decided not
> to execute my compile and package, the deploy target would fail.
>
> --
> David Weintraub
> [hidden email]
>

Scot P. Floess
27 Lake Royale
Louisburg, NC  27549

252-478-8087 (Home)
919-890-8117 (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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

exec on batch file causes build to hang

Scott Stark-3
I'm not sure if this is an Ant problem or a batch file problem, so I'll
start here -- apologies if it's inappropriate.

I'm using an Ant build file to execute a Windows XP batch file using the
exec command. My target looks something like this:

      <exec executable="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"
                  dir="${VCC_CBU_ICdir_root}"
                  failonerror="${failonerror}"
                  failifexecutionfails="${failifexecutionfails}"
                  spawn="true"
                  >
        </exec>

The problem is, spawn="true" results in an error:

      spawn does not allow attributes related to input, output, error,
result
      spawn also does not allow timeout
      finally, spawn is not compatible with a nested I/O <redirector>,

      BUILD FAILED
      C:\working\stop_restart.xml:78: You have used an attribute or nested
element which is not compatible with spawn

However, if I remove spawn="true", the control never gets returned to the
Ant build file (the batch file starts up a java process that never actually
completes unless the process is killed), so the build hangs and never
completes.

I've used this exact syntax on other batch files running similar java
processes, and it works perfectly. I'm not sure what's causing this one to
hang, and I don't understand the spawn error messages. Any thoughts?

thanks,

Scott
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

exec on batch file causes build to hang

David Weintraub
You need to read the section about the <exec> task for Windows users.
You cannot execute a Batch command directly. You have to call
command.exe and use the /c parameter.

The following is from the <exec> task's page:

Windows Users

The <exec> task delegates to Runtime.exec which in turn apparently
calls ::CreateProcess. It is the latter Win32 function that defines
the exact semantics of the call. In particular, if you do not put a
file extension on the executable, only ".EXE" files are looked for,
not ".COM", ".CMD" or other file types listed in the environment
variable PATHEXT. That is only used by the shell.

Note that .bat files cannot in general by executed directly. One
normally needs to execute the command shell executable cmd using the
/c switch.

<target name="help">
  <exec executable="cmd">
    <arg value="/c"/>
    <arg value="ant.bat"/>
    <arg value="-p"/>
  </exec>
</target>
Cygwin Users



On 8/14/09, Scott Stark <[hidden email]> wrote:

> I'm not sure if this is an Ant problem or a batch file problem, so I'll
> start here -- apologies if it's inappropriate.
>
> I'm using an Ant build file to execute a Windows XP batch file using the
> exec command. My target looks something like this:
>
>       <exec executable="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"
>                   dir="${VCC_CBU_ICdir_root}"
>                   failonerror="${failonerror}"
>                   failifexecutionfails="${failifexecutionfails}"
>                   spawn="true"
>                   >
>         </exec>
>
> The problem is, spawn="true" results in an error:
>
>       spawn does not allow attributes related to input, output, error,
> result
>       spawn also does not allow timeout
>       finally, spawn is not compatible with a nested I/O <redirector>,
>
>       BUILD FAILED
>       C:\working\stop_restart.xml:78: You have used an attribute or nested
> element which is not compatible with spawn
>
> However, if I remove spawn="true", the control never gets returned to the
> Ant build file (the batch file starts up a java process that never actually
> completes unless the process is killed), so the build hangs and never
> completes.
>
> I've used this exact syntax on other batch files running similar java
> processes, and it works perfectly. I'm not sure what's causing this one to
> hang, and I don't understand the spawn error messages. Any thoughts?
>
> thanks,
>
> Scott
>


--
David Weintraub
[hidden email]


--
David Weintraub
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

Scott Stark-3

Hi David, thank you kindly for the pointer about running batch files on Windows. However, I get the same results when running my build file from the command line: the batch file executes (and starts the java process), but never returns control to the build file, so I have to hit control-C to exit the batch file.

<exec executable="cmd"
failonerror="${failonerror}"
failifexecutionfails="${failifexecutionfails}"
dir="${VCC_CBU_ICdir_root}">
<arg value="/c"/>
<arg value="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"/>
</exec>


Does this sound like something is going on in the batch file? Perhaps it's looping or something...

Scott


David Weintraub <[hidden email]>



> You need to read the section about the <exec> task for Windows users.
> You cannot execute a Batch command directly. You have to call
> command.exe and use the /c parameter.






Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

David Weintraub
Can you run the batch file outside of Ant from the command line without the
process hanging?

Do you have echo turned on or off in the Batch file? I don't use a Windows
system, so I don't know if the commands echo if echo is on. However, you
sound like you're pretty sure that its the Java task that's dying or
hanging.  Maybe you could run the Java profiler (-Xprof) option? It could be
a memory problem with Ant not giving enough memory to the Java process.
Remember that Ant, exec, and your Java process are all running in the same
memory footprint. Ant, by default, only runs under 64mb. You can use the
ANT_OPTS environment variable to set Ant to run with more memory
(ANT_OPTS=-Xmx512m for example). See if that helps.

I know that Windows doesn't seem to support "spawn" in the <exec> task. Have
you tried the <java> task if you're just running a Java program anyway? You
might have more luck with that.

On Fri, Aug 14, 2009 at 9:11 PM, Scott Stark <[hidden email]> wrote:

> Hi David, thank you kindly for the pointer about running batch files on
> Windows. However, I get the same results when running my build file from the
> command line: the batch file executes (and starts the java process), but
> never returns control to the build file, so I have to hit control-C to exit
> the batch file.
>
> <exec executable="cmd"
> failonerror="${failonerror}"
> failifexecutionfails="${failifexecutionfails}"
>
> dir="${VCC_CBU_ICdir_root}">
> <arg value="/c"/>
> <arg value="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"/>
> </exec>
>
>
> Does this sound like something is going on in the batch file? Perhaps it's
> looping or something...
>
> Scott
>
>
> [image: Inactive hide details for David Weintraub <[hidden email]>]David
> Weintraub <[hidden email]>
>
>
>
> > You need to read the section about the <exec> task for Windows users.
> > You cannot execute a Batch command directly. You have to call
> > command.exe and use the /c parameter.
>
>
>
>
>
>
>


--
David Weintraub
[hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

Scott Stark-3

> Can you run the batch file outside of Ant from the command line without
the
> process hanging?

Hi David, technically, yes. But the process (batch file) doesn't "hang"; it
executes a java tool and holds that state ("running") until the process is
terminated by another batch file. In other words, the java process is
running correctly, but even within the batch file, control is not returned
to the command line, which is why I was hoping to "spawn" it (which I can
do with other batch/java processes). Unfortunately I didn't write the batch
file or the java tool so I'm unclear what's happening.

I might look into running it from the <java> task -- thanks for the tip.

Scott
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

David Weintraub
On Mon, Aug 17, 2009 at 11:00 AM, Scott Stark <[hidden email]> wrote:

>
> > Can you run the batch file outside of Ant from the command line without
> the
> > process hanging?
>
> Hi David, technically, yes. But the process (batch file) doesn't "hang"; it
> executes a java tool and holds that state ("running") until the process is
> terminated by another batch file. In other words, the java process is
> running correctly, but even within the batch file, control is not returned
> to the command line, which is why I was hoping to "spawn" it (which I can
> do with other batch/java processes). Unfortunately I didn't write the batch
> file or the java tool so I'm unclear what's happening.
>
> I might look into running it from the <java> task -- thanks for the tip.


Another possibility is to surround the <exec> task with the <waitfor> task.
The <waitfor> task will terminate the <exec> task after a certain period of
time. I don't know how well it works on Windows.


--
David Weintraub
[hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

Scott Stark-3
> Another possibility is to surround the <exec> task with the <waitfor>
task.
> The <waitfor> task will terminate the <exec> task after a certain period
of
> time. I don't know how well it works on Windows.

Nice idea, but:

BUILD FAILED
C:\working\informix\stop_restart.xml:95: waitfor doesn't support the nested
"exec" element.

Scott
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: exec on batch file causes build to hang

Scott Stark-3
In reply to this post by David Weintraub

David Weintraub wrote:
>
> > Can you run the batch file outside of Ant from the command line without
> the
> > process hanging?
>

I've discovered that running "start IC_start.bat" from the command line
opens the process in a new window and returns control to the executing
window (on Windows XP). So this does what I want. However, when I try and
do this from an Ant task, I get this error:

BUILD FAILED
C:\working\informix\stop_restart.xml:98: Execute failed:
java.io.IOException: CreateProcess: start C:\VCC\IC_start.bat error=2

Any idea what "error=2" means, and how I can fix it?

Here's my task FYI:

      <exec executable="start"
                  failonerror="${failonerror}"
                  failifexecutionfails="${failifexecutionfails}"
                  dir="${VCC_CBU_ICdir_root}">
          <arg value="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"/>
        </exec>

thanks!

Scott
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

AW: exec on batch file causes build to hang

Sascha Ernst
Hello,

Perhaps this helps....
       <exec executable="cmd"
         dir="${VCC_CBU_ICdir_root}">
          <arg line="/c start cmd /c
                     &quot;IC_start.bat&quot;" />
       </exec>

This opens a new window, starts your program in this windows and continues
With the build script.
If you change the 2nd /c to /k the buildscripts stops until your program stops and
the windows closes.

BUT: because of the non-existing coupling between the buildscript and the called
program, you cannot use failonerror and stuff like that (shure, you can use it,
but not to monitor/react on the exit code of your program)

The &quot;s are usefull, if you have more complex arg lines.
In your case they are not needed.

Feel free to fiddle around with more or less cmd and start commands....

Ein Gruss von der Saar

--
Sascha Ernst
Dipl. Inform.
Head of Software Quality Management


Telefon: + 49 (0)681 - 302 - 5133
Telefax: + 49 (0)681 - 302 - 5109
E-Mail: [hidden email]
Website: http://www.living-e.com


Living-e AG
Campus D3 2
66123 Saarbrücken


Vorstand: Guido Polko
Aufsichtsratsvorsitzender: Uwe Feuersenger
Amtsgericht: Mannheim, HRB 111323

Besuchen Sie uns auf dem 10. ÖV-Symposium am 20.08.2009, Stand 14, Ruhrfestspielhaus, Recklinghausen.



-----Ursprüngliche Nachricht-----
Von: Scott Stark [mailto:[hidden email]]
Gesendet: Dienstag, 18. August 2009 16:16
An: Ant Users List
Betreff: Re: exec on batch file causes build to hang


David Weintraub wrote:
>
> > Can you run the batch file outside of Ant from the command line without
> the
> > process hanging?
>

I've discovered that running "start IC_start.bat" from the command line
opens the process in a new window and returns control to the executing
window (on Windows XP). So this does what I want. However, when I try and
do this from an Ant task, I get this error:

BUILD FAILED
C:\working\informix\stop_restart.xml:98: Execute failed:
java.io.IOException: CreateProcess: start C:\VCC\IC_start.bat error=2

Any idea what "error=2" means, and how I can fix it?

Here's my task FYI:

      <exec executable="start"
                  failonerror="${failonerror}"
                  failifexecutionfails="${failifexecutionfails}"
                  dir="${VCC_CBU_ICdir_root}">
          <arg value="${VCC_CBU_ICdir_root}${file.separator}IC_start.bat"/>
        </exec>

thanks!

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AW: exec on batch file causes build to hang

Scott Stark-3

Sascha Ernst wrote:

> Perhaps this helps....
       <exec executable="cmd"
         dir="${VCC_CBU_ICdir_root}">
          <arg line="/c start cmd /c
                     &quot;IC_start.bat&quot;" />
       </exec>

Wow, that's some crazy code there! :-) Well, it does open a new window, but
unfortunately the original build still doesn't complete in the first
window. Sigh... I'm going to go after the developer who wrote this crazy
java program. Thanks to everyone for your ideas.

Scott
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Articles on Ant tips & tricks!!!

Bob Aiello-5
In reply to this post by David Weintraub
Hi Everyone,

I am looking for people who are interested in sharing best practices
for using Ant, Maven and Make. The articles will appear in CM Basics
(www.cmcrossroads.com).

We have 60,000+ readers with lots of existing articles and forums on
build engineering.

Please contact me directly if you are interesting in submitting an article!

Bob Aiello
[hidden email]
Editor in Chief
CM Crossroads
http://www.linkedin.com/in/BobAiello



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...