ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <g.grigelio...@gmail.com>
Subject Re: Impact of Java SecurityManager being deprecated for removal post Java 17
Date Sun, 19 Sep 2021 12:28:26 GMT
On Mon, 23 Aug 2021 at 17:39, Stefan Bodewig <bodewig@apache.org> wrote:

> On 2021-08-19, Gintautas Grigelionis wrote:
>
> > On Thu, 19 Aug 2021 at 12:01, Stefan Bodewig <bodewig@apache.org> wrote:
>
> >> I didn't mean the Antlib to be backwards compatible, but rather to offer
> >> it and tell people to switch over to it. It would be the first time we'd
> >> remove a core feature of Ant completely, though, so we may need to
> >> discuss whether there is a better migration path. We have moved some
> >> source code management tool specific tasks to antlibs in the past, but
> >> never a core part.
>
> > Would it make sense to create a "legacy" antlib for, say, JEE (EJB, JSP,
> > etc) and VCS tasks + anything that has been deprecated in JDK?
>
> I'd only do that if it reduces maintenance burden for anybody.
>

Is packaging away unmaintainable code (because of third-party dependencies
etc)
a maintenance burden, or is it a one-off job to make clear what's legacy?
There are about 60 old issues (11+ years) in Bugzilla for these tasks that
would never be actualised again.

Gintas

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message