Mailing-List: contact chemistry-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chemistry-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jhuebel@opentext.com
 designates 149.235.128.48 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CAEC92.B67B155D"
Subject: Build failure with fresh maven repo
Date: Wed, 5 May 2010 22:36:58 +0200
Message-ID: <267F7EC9C11CCB4C806D30029DA677630E5BE77C@MUCXGC2.opentext.net>
Thread-Topic: Build failure with fresh maven repo
Thread-Index: AcrskrVKwdfwilypSPyHnLY9STHNtQ==
From: =?iso-8859-1?Q?Jens_H=FCbel?= <jhuebel@opentext.com>
To: <chemistry-dev@incubator.apache.org>

------_=_NextPart_001_01CAEC92.B67B155D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Chemistries,

=20

I detected a build failure caused by some outdated dependencies in our =
pom.xmls.=20

=20

It concerns me a bit that these kind of errors remain undetected in our =
complete build and verification chain.

=20

The problem is that after a refactoring the maven repository is not =
cleared and keeps all artifacts that ever have been produced. So all our =
builds internally and on Hudson succeed even if a pom.xml is invalid. If =
someone builds from scratch however the build fails.

=20

It seems to be good idea to manually clear the chemistry branch in the =
maven repository after any change in the dependencies. Perhaps there is =
a better way to address this kind of problem? Is there something like =
mvn uninstall perhaps?

=20

Jens

=20


------_=_NextPart_001_01CAEC92.B67B155D--