Hi,

Will those antlibs be bundled with the package, or do picture them as a
separate download?
Reason I ask is because I think SCM tasks are commonly used in buildscripts.

Cheers,

Remie


On Mon, Nov 3, 2008 at 2:15 PM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> I'd like to move those tasks (see subject) that don't get tested but
> released with Ant into separate Antlibs and deprecate them in trunk.
> My current candidate list consists of all SCM tasks (including CVS)
> and all vendor specific EJB tasks - one Antlib per task (or family of
> tasks in the case of CVS).
>
> Of course we couldn't deprecate the tasks in trunk unless the
> corresponding Antlib has been released.
>
> Before I start doing the work I'd like to get a feel for whether you
> agree that it is a good idea and whether you'd be willing to vote for
> a release of such an Antlib.  Kevin tried to do something like this
> for the VSS Antlib and failed, so before I put any work into it, I'd
> like to be sure, it wouldn't be wasted.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to