I went and glanced at the cdeploy docs and I pretty much do what
Robert mentioned. In my project I have an environments/x directory
(where x = local, development, testing, production, etc) which
contains my environment-specific settings and my ant task copies those
over after doing a build, but before creating the jar/war. I
obviously have separate tasks for the environment-specific builds, but
I think you get the idea.
mrg
On Wed, Apr 15, 2009 at 1:55 AM, Robert Zeigler
<robert.zeigle..oxanemy.com> wrote:
> I've never used it, although looking at it now, it could potentially be
> useful.
> Still, I think the common paradigm for handling the situation cdeploy is
> supposed to handle is to setup your build to put the appropriate resource
> files into the jar to begin with, rather than modifying an existing jar.
> *shrug*
>
> I'm fine with either keeping or dropping it.
>
> Robert
>
> On Apr 14, 2009, at 4/141:15 AM , Andrus Adamchik wrote:
>
>> I never found "cdeploy" Ant task all that useful. Any objections to
>> deprecating it in 3.0, with the goal to remove in 3.1?
>>
>> Andrus
>
>
This archive was generated by hypermail 2.0.0 : Wed Apr 15 2009 - 09:15:30 EDT