deprecate cdeploy?

[Andrus Adamchik <an...@objectstyle.org>]

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

Re: deprecate cdeploy?

[Andrus Adamchik <an...@objectstyle.org>]

Deprecation committed.


On Apr 14, 2009, at 9: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
>

Re: deprecate cdeploy?

[Michael Gentry <mg...@masslight.net>]

I've never used it, either.  It might be better to ask on user instead
of dev, though.

mrg


On Tue, Apr 14, 2009 at 2:15 AM, Andrus Adamchik <an...@objectstyle.org> 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
>

Re: deprecate cdeploy?

[Mike Kienenberger <mk...@gmail.com>]

I either used JNDI or manually specified an alternate config file name
and had multiple config files.

On Tue, Apr 14, 2009 at 2:15 AM, Andrus Adamchik <an...@objectstyle.org> 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
>

Re: deprecate cdeploy?

[Michael Gentry <mg...@masslight.net>]

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
<ro...@roxanemy.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
>
>

Re: deprecate cdeploy?

[Andrus Adamchik <an...@objectstyle.org>]

On Apr 15, 2009, at 8:55 AM, Robert Zeigler wrote:

> 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.

Exactly. This is why I think it is badly designed. In fact I hope  
Cayenne 3.1 will have a better approach to handling mapping "libraries".

Andrus

Re: deprecate cdeploy?

[Robert Zeigler <ro...@roxanemy.com>]

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

Re: deprecate cdeploy?

[Tore Halset <ha...@pvv.ntnu.no>]

Hello.

I have never used cdeploy. I mainly use jndi to configure the data  
sources and sometimes just plain dbcp.

Regards,
  - Tore.

On Apr 14, 2009, at 8:15 , 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
>