Hi,
On Sun, Mar 05, 2017 at 11:32:53AM +0100, Emmanuel Bourg wrote:
> The ant dependency is only used for the excelant tasks [1] (which are
> never used in Debian [2]). Any use of these tasks implicitly means Ant
> is already on the classpath. In this context Ant can be seen as a
> runtime, much
The ant dependency is only used for the excelant tasks [1] (which are
never used in Debian [2]). Any use of these tasks implicitly means Ant
is already on the classpath. In this context Ant can be seen as a
runtime, much like the Servlet API for web based stuff. So I think it
makes sense to remove
Hi,
On Sat, Mar 04, 2017 at 11:40:53AM -0800, tony mancill wrote:
> were causing a serious issue, we could discuss splitting ant into
> something like "ant-bin" (maybe there's a better name) and libant-java,
> so only the latter library package is a dependency of
> libapache-poi-java.
>
> In
On Sat, Mar 04, 2017 at 01:30:47AM +0100, Michael Biebl wrote:
> Source: libapache-poi-java
> Version: 3.10.1-3
> Severity: important
>
> libapache-poi-java is an indirect dependency of libreoffice, so pulled
> in on every desktop installation.
>
> Having a build tool like ant being pulled
Source: libapache-poi-java
Version: 3.10.1-3
Severity: important
libapache-poi-java is an indirect dependency of libreoffice, so pulled
in on every desktop installation.
Having a build tool like ant being pulled because of a library
dependency is unwanted in such a case. Please consider dropping
5 matches
Mail list logo
