Hi Saminda,

Looking at the build history it doesn't seem too surprising that there 
hasn't been a build since Dec. 14, as there are days where there is no 
build available. I had assumed builds were only produced when changes were 
introduced in the repository.

Can you tell me how the lack of builds from the 15-17 of Dec. has caused 
breakage in your build? (Is this an Axis2 build?) Is the break because you 
responded to a change that is not yet available in the Woden nightly 
build?

AFAIK no change has been made to the Woden nightly distribution location 
is the last 3 days so you should have the correct location.

I'll bring up these issues on tomorrow's Woden status call [1] and should 
have an answer for you after the call if someone else doesn't pipe up with 
one before then.

[1] http://incubator.apache.org/woden/dev/index.html#Weekly+Status+Call

Lawrence




"Saminda Abeyruwan" <[EMAIL PROTECTED]> 
12/17/2007 02:13 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Status of nightly build







Hi Devs,

Looking at the distributionManagement of pom.xml, it says that the nightly 
builds for Woden should be available in 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/woden/{artifact_id}/1.0-incubating-SNAPSHOT/
 


Unfortunately, the latest SNAPSHOTs available in these locations have been 
created on 14 Dec 2007 22:07 hrs. This has cause lots of Woden dependent 
on-line builds to fail as their has been a API change after prior 
SNAPSHOT. 

Please be kind enough to  fix the nightly builds. 

Most of build system look for Apache related SNAPSHOTs in 
http://people.apache.org/repo/m2-snapshot-repository . If Woden nightly 
builds are available in repository other than listed herewith, please be 
kind enough to point me to the correct location.

Thank you

Saminda 
-- 
Saminda Abeyruwan

Senior Software Engineer 
WSO2 Inc. - www.wso2.org 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to