Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
MIME-Version: 1.0
In-Reply-To: <001e01d24ecc$f7e23e20$e7a6ba60$@de>
References: <5824107d-d7bb-2b11-6615-de0fa8961bf2@gmail.com> <001e01d24ecc$f7e23e20$e7a6ba60$@de>
From: Gintautas Grigelionis <g.grigelionis@gmail.com>
Date: Mon, 5 Dec 2016 10:56:15 +0100
Message-ID: <CALVNWHWC0LcvrbP3bz2Yw97YGiCqVK5QExKS-k3dd2KJBnmgMA@mail.gmail.com>
Subject: Re: Ivy - any future or is it also going to be retired?
To: Ant Developers List <dev@ant.apache.org>
Content-Type: multipart/alternative; boundary=001a1147d2d872221f0542e64cda
archived-at: Mon, 05 Dec 2016 09:56:22 -0000

--001a1147d2d872221f0542e64cda
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

If you want to push Ivy, you need integrations with IDE. IMHO, IvyDE works
well with Eclipse;
perhaps its release cycle needs to be synced with Ivy release cycle (which
is roughly biannual a this point).
Is there a release plan for Ivy, by the way? When will this
<https://issues.apache.org/jira/browse/IVY-1444> fix be released?

Gintas

2016-12-05 8:55 GMT+01:00 Jan Mat=C3=A8rne (jhm) <apache@materne.de>:

> We see Ivy as a widely used component. We use archiving some components t=
o
> recalibrate our focus.
> I don't think that we want to archive Ivy in the near future. Instead we
> try to push Ivy.
>
> If you want to help with Ivy, you're welcome.
>
> "It's already a challenge to stick with Ivy build system itself given the
> lack of fixes/releases/responses."
> What are the problems you think are resolved with new Ivy releases?
>
>
> Jan
>
>
>
> > -----Urspr=C3=BCngliche Nachricht-----
> > Von: Jaikiran Pai [mailto:jai.forums2013@gmail.com]
> > Gesendet: Montag, 5. Dezember 2016 08:26
> > An: dev@ant.apache.org
> > Betreff: Ivy - any future or is it also going to be retired?
> >
> > I have been following the latest emails on retiring sub projects in
> > Ant.
> > I just see a proposal to retire IvyDE (the Eclipse plugin) for valid
> > reasons (given the lack of any real activity in there). Given this, I
> > would like to understand what the future of Ivy project itself is. I
> > have asked this more than once previously in the dev mailing list
> > during the past year or so and any efforts in reviving the project,
> > which IMO has seen no real activity. I have even tried contacting some
> > of the dev team members to try and see if I can help in any way to keep
> > it active.
> > But unfortunately, that hasn't generated any kind of changes. There's
> > been no real code changes, bug fixes or any consistent
> > help/communication when it comes to user issues.
> >
> > I would like to see some official word on what the future is for Ivy
> > itself. Is it going to be retired too? Seeing that IvyDE itself is
> > being proposed for retirement and the only other IDE plugin is a
> > IntelliJ one (that I know of), asking (some of our internal users) to
> > continue using Ivy is going to be challenge. It's already a challenge
> > to stick with Ivy build system itself given the lack of
> > fixes/releases/responses. If there's an official word on where it
> > stands in terms of projects goals, we can officially move to a
> > different build system.
> >
> > -Jaikiran
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> > commands, e-mail: dev-help@ant.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>

--001a1147d2d872221f0542e64cda--