The tasks are mainly used to deploy a java application to
the AS400. So you have a PC running the OS dujour it FTP's
the jar to the AS400 then you can use the ANT task to use
the static compiler (CRTJVAPGM) on the AS400. So the <exec>
task couldn't cut it unless we added parms for AS400 system
name, password, current library... Can this be done? As I
think about it it is an elegant solution to be able to say
<exec dir="${src}" os="AS400" output="dir.txt"
as400="big_iron">
<arg line="dsplibl *print"/>
</exec>
The thing is that the <exec> wouldn't be running on the
machine that was running ANT but it would do in essence an
RPC call to the AS400.
regards,
Glen
On Wed, 27 Mar 2002 16:31:29 -0500
"Erik Hatcher" <[EMAIL PROTECTED]> wrote:
> *This message was transferred with a trial version of
> CommuniGate(tm) Pro*
>
> ----- Original Message -----
> From: "Glen Marchesani" <[EMAIL PROTECTED]>
> To: "Ant Developers List" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 27, 2002 4:21 PM
> Subject: procedure for submitting a new task for
> optional.jar
>
>
> > I have created a couple AS400 related tasks that are
> quite
> > useful if you are working with AS400's and ANT. I would
> like
> > to submit them for inclusion in optional.jar. What is
> the
> > procedure for this?
> >
> > The as400 tasks are
> > -run a command on an AS400
>
> Can this be done as a patch to <exec> so that we have a
> single "run a
> command" task that deals with the platform issues
> underneath?
>
> You can submit via Bugzilla as enhancements and attach
> files there. Please
> also supply documentation files and patches to link them
> in to our existing
> documentation - also, don't forget about patches to
> defaults.properties and
> WHATSNEW! :)
>
> Erik
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
