Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of clement.escoffier@gmail.com
 designates 209.85.220.210 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=WK8RF6VrJa9PaPadUEsuWyhWdk+hiBMooQlQZhCT6I44C2qnI6pw8KkF+VonoHQtxv
         kxv7+CvjVTA3jv260RN6VmNmGPHfSl149syc2YSZtaP9LRQybJfcjLXkO+MPjGBFEWUz
         eQP3v4QU15l1i2Hhyuj5a1EBQYiFd0k/QpzNo=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: trunk still does not build
From: Clement Escoffier <clement.escoffier@gmail.com>
In-Reply-To: <C40613C0-E790-4F4E-92C6-80593990A2EC@luminis.nl>
Date: Fri, 26 Mar 2010 17:29:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5483986B-06B8-49A8-8D75-AAE94FC1B6C1@gmail.com>
References: <4BAB0049.8070902@Sun.COM>
 <b23ecedc1003250532r9a172b7s6f6442b36254f250@mail.gmail.com>
 <8203224e1003250551s3b6f4ed9lf9744a2e2eb62b46@mail.gmail.com>
 <8203224e1003250619t7b5ec89ew9b3b64b337a14b1@mail.gmail.com>
 <b23ecedc1003250728k27ebedcdl3b868c306969cfc4@mail.gmail.com>
 <8203224e1003251528j37b4e58bk5a4813cc03ecbb6e@mail.gmail.com>
 <b23ecedc1003260127r3a764353r88acd50fe2ecbfa@mail.gmail.com>
 <b23ecedc1003260702i32b0ca58gd16119cf10304bf2@mail.gmail.com>
 <8203224e1003260723i14c8df91n7ee24c174a04c696@mail.gmail.com>
 <4BACCB9E.30602@Sun.COM>
 <b23ecedc1003260819h52007583k611e886828284e03@mail.gmail.com>
 <C40613C0-E790-4F4E-92C6-80593990A2EC@luminis.nl>
To: dev@felix.apache.org

Hi,


On 26.03.2010, at 17:23, Marcel Offermans wrote:

> On Mar 26, 2010, at 8:19 , Guillaume Nodet wrote:
>> On Fri, Mar 26, 2010 at 15:58, Sahoo <Sahoo@sun.com> wrote:
>>> Pierre De Rop wrote:
>>>> However, the -Dmaven.test.skip=3Dtrue option still has to be used =
because
>>>> there is one pending issue in the DependencyManager junit tests, =
which has
>>>> to be fixed. This is a known issue, and it's referenced here:
>>>> http://issues.apache.org/jira/browse/FELIX-2078.
>>>=20
>>>=20
>>> Why don't we exclude the test until it is fixed? That will keep CI =
server
>>> to function as well.
>>>=20
>>=20
>=20
>> That's a good idea ;-)
>=20
> Whilst I don't mind too much doing that, I'm wondering why our build =
cannot support subprojects that have failing tests? I mean as long as =
I'm not releasing anything, a project that is in flux might have a few =
test cases that are broken, right? That should not affect our whole =
build in a way that it makes life hard on everybody else.
>=20
> Is it really not possible to have a solution where having tests that =
fail is not a problem?
>=20
> If not, then just disable that test for now.

There is several things that are possible:
- setting 'testFailureIgnore=3Dtrue' ignore test failures (not sure =
about errors).=20
- executing the tests only when a 'test' profile is enabled. That was my =
choice for iPOJO because of the number of tests.

Regards,

Clement


>=20
> Greetings, Marcel
>=20