Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: Jorg Heymans <jh@domek.be>
Subject: Re: [continuum] BUILD FAILURE: Portal Block Implementation
Date: Mon, 01 May 2006 18:55:06 +0200
Lines: 30
Message-ID: <e35eg0$rbp$1@sea.gmane.org>
References: <6922219.1146432979406.JavaMail.maven@cocoon.zones.apache.org>
 <e34i0g$e3$1@sea.gmane.org> <44562CEF.2050302@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
In-Reply-To: <44562CEF.2050302@apache.org>
Sender: news <news@sea.gmane.org>


Carsten Ziegeler wrote:

> 
> Ah, great! This shows how useful tests are. I fixed the bug in the
> implementation and the block should now build fine again.

cool, the next build (around 1am) should pick up that change then and
we'll get notified on the list. We didn't get notified of the initial
build failure in the first place because it occured initially after i
migrated CI to 1.0.3.


> Btw, did you change anything to make the build work again? On my machine
> maven was never able to find the core test jar as the name in the
> repository did not match the name maven searched for.

I found out that Continuum doesn't copy test-jars to it's internal
deployment repository. As i was rsync'ing this internal one with
svn.a.o/maven-snapshot-repository the test-jars got always left out. The
other modules were only able to build because the m2 repository of the
zone maven account happened to have a previous copy of the test-jar
installed. I've cleared out the local repo and did a fresh rsync with
the snapshot repository.

If the problem still persists let me know.


Thanks
Jorg