Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!usenet.goja.nl.eu.org!aioe.org!bofh.it!news.nic.it!robomod
From: Pirate Praveen <praveen@onenetbeyond.org>
Newsgroups: linux.debian.maint.java
Subject: Re: Java packages and autopkgtest
Date: Sat, 05 Dec 2020 19:30:02 +0100
Message-ID: <BiKtI-7KN-11@gated-at.bofh.it>
References: <BiKtI-7KN-13@gated-at.bofh.it> <BiJR0-7hU-27@gated-at.bofh.it> <BiK0F-7lA-3@gated-at.bofh.it>
Old-Return-Path: <praveen@onenetbeyond.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-13; format=flowed
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 20
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:11955



On Sat, Dec 5, 2020 at 18:56, Thorsten Glaser <t.glaser@tarent.de>=20
wrote:
> On Sun, 6 Dec 2020, Roger Shimizu wrote:
>=20
>>  I find java packages with maven-debian-helper can be tested by:
>>=20
>>  =3D=3D=3D=3D
>>  Test-Command: dh_auto_configure; dh_auto_test
> 				   ^^^^^^^^^^^^
>=20
> Doesn=FFt this just call mvn test ?
>=20
> If so, that=FFs not as-installed testing and as such very much
> *not* an autopkgtest.

Though it can still be useful when dependencies change (that is another=20
use case for autopkgtests). autopkgtest regression will block migration=20
to testing.