[Building Sakai] problems building trunk -- sakai-full

[Steve Swinsburg]

No it's just that the snapshot artifacts need to be in the repo. 2.9 and trunk use the new release method. 

Sent from my iPhone

On 23/05/2012, at 4:25, Jim Eng <jimeng at umich.edu> wrote:

> So next I tried https://source.sakaiproject.org/svn/sakai/branches/sakai-2.9.x-all, and that has the roughly same outcome. At least I was able to build kernel in the 2.9.x branch, but the rest of sakai is seriously ill.  Was this the result of an attack by hackers trying to bring down sakai?  
> 
> Jim
> 
> 
> On May 22, 2012, at 8:49 AM, Jim Eng wrote:
> 
>> I have tried building with maven-2.  I tried building kernel first.  Neither worked for me (yet).  
>> 
>> I'd like to ask one question:  Why not check in pom's with relative paths if that builds and the current pom's are failing for everyone?  Wouldn't it make sense to have what's in subversion work, rather than having everybody work through the same large set of issues?  And then once the long-range issues are worked out, the pom changes could be reverted?
>> 
>> Just an idea.  
>> 
>> Jim
>> 
>> 
>> 
>> 
>> On May 21, 2012, at 3:37 PM, Matthew Jones wrote:
>> 
>>> Hi Jim,
>>> 
>>> This is an error we are going to talk about at the release meeting this week that also has come up for some other of us.
>>> 
>>> Basically the quick fix solution is to either build with Maven 2 or to build kernel then master first separately. (If you want to use Maven 3) The build fails right now if kernel and master aren't in the local repository (you start with a clean repo)
>>> 
>>> Like
>>> cd kernel && mvn clean install
>>> cd ../master && mvn clean install
>>> 
>>> (Then you're good to go)
>>> 
>>> The problem is that in Maven 3, it does dependency resolution on the parents, and the parents either have to have a relativePath defined or they have to be in a repository. Since we removed all of the repositories sections (as well as removed the snapshot artifacts) they won't be in repositories. Adding in relativePath would cause the indies to break.
>>> 
>>> What I think will happen (medium term) is kernel/master will need to go back into the snapshot repo, and a repositories section will be added. Long term, api version will split from impl and all apis will will actually be released to maven central so we don't need a repositories section again.
>>> 
>>> However this is some "brand new" research, and might not even be needed 
>>> 
>>> On Mon, May 21, 2012 at 3:18 PM, Jim Eng <jimeng at umich.edu> wrote:
>>> I have a fresh checkout from here:
>>> 
>>>        https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-all
>>> 
>>> I am trying to build/deploy with maven 3.0.4.  I get errors right away.  I have tried just using the clean goal, and get the same errors.  I have also tried just using the install goal, without the clean goal, to make sure it wasn't some problem with the clean goal.  I still get the same error. I am including the complete trace below.
>>> 
>>> It's worth noting that trunk is building on nightly2, so it's likely this is a local error for me, but I'm confused about what to try next.
>>> 
>>> Suggestions appreciated.
>>> 
>>> Thanks.
>>> 
>>> Jim
>> 
> 
> _______________________________________________
> 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/20120523/ff40b0ad/attachment.html