Hi,
I've been looking at the use of commons logging in exec. Coming from
ant dev, it would be nice to refactor ant to use the commons-exec
package, but Ant has it's own logging mechanism (using logging
listeners), and I'm pretty sure that the ant code base will not change
to using
Just in case you don't want to use Maven ;). Eventually got some time
to play with OS dev again (w00t).
Kev
?xml version=1.0 encoding=UTF-8?
!--
===
Apache Commons-Exec build file
Copyright (c) 2005 The Apache
Brett Porter wrote:
Hi Kev,
Glad you've got some time to play :)
I had a look at this and all the functionality except for
parameterisation of the debug/deprecated/optimize variables seems to be
included in the build.xml file I created - what was the reason for
replacing it?
Sorry I was
Niklas Gustavsson wrote:
Kev Jackson wrote:
I'm not a fan of maven, so I'll write up a quick build file for it,
I'll also look into javadoc/unit tests as soon as I have some time
(perhaps tomorrow)
Great! With regards for the unit tests I personally think that the
first step should
(This email with a .zip attachment does not seem to get through to the
list. And since there's no component for exec in bugzilla, I've
uploaded the file to
http://www.protocol7.com/tmp/commons-exec-initial-20050802.zip
instead. If I should send it somehow different, please enlighten me.)
This is a very short description of the cleaned up Ant exec task design:
* Exec: the former Ant task class used to create and configure Execute
instances. Now mainly a convience class for starting new Execute
instances.
* Execute: the main class for running one process. Handles creation
Scope of the package
The package shall create and maintain a process execution package
written in the Java language to be distributed under the ASF license.
The Java code might also be complemented with scripts (e.g. Perl
scripts) to fully enable
