[Building Sakai] Most indies broken in Jenkins

[david.horwitz@uct.ac.za]

Central will only help in the case of released artifacts. I'm still unclear why this info was removed ...

Sent from my HTC

----- Reply message -----
From: "Steve Swinsburg" <steve.swinsburg at gmail.com>
To: "David Horwitz" <david.horwitz at uct.ac.za>
Cc: <sakai-dev at collab.sakaiproject.org>
Subject: [Building Sakai] Most indies broken in Jenkins
Date: Thu, Feb 2, 2012 10:33 am


Yep, unless the master pom is in central then the indies need the Sakai repo listed so that they can find their parent.

Have we got these poms into central yet? I know there was talk of that happening.

cheers,
Steve



On 02/02/2012, at 8:41 PM, David Horwitz wrote:

> Hi All,
> 
> it seems that most indies in jenkins are broken. Their looking for the 
> 2.10 master and not finding it as it they have had the repository 
> definitions removed. I'm not sure why these were removed - they were 
> there for a reason. Could we have them back please?
> 
> David
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120202/37c46ed1/attachment.html