Hi everyone, Thank you for the warm welcome.
Thanks for the link to the developer's page. To clarify my post to the list, cab support is already built into ant. However the optional jar is not built, it has been remove from the build.xml. I want to re-factor cab.java to support M$ new cab file utility, and in that process not violate the established practices and style making ant a great product. This also means to keep the current API and functionality, not to break any regression, back compatibility to existing deployments, and migrations to more modern environments.. The questions I have: 1) Should I keep the cabarc.exe support and detect the new makecab utility or remove existing cabarc.exe support ? 2) Is there a style guidance for build.xml file ? (I don't want to submit something that violates best practices) v/r gary On Sat, Apr 2, 2016 at 10:14 AM, Stefan Bodewig <bode...@apache.org> wrote: > On 2016-04-02, Martin Gainty wrote: > > > one option is to re-factor Cab.java into a Ant Taskdef > > Cab.java already *is* a task that ships with Ant. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
