[Building Sakai] Building Sakai on MacOS X Server

Mon Apr 20 04:59:26 PDT 2009

FWIW, the Sakai Install Guide recommends the latest Maven 2 version,  
and does not explicitly tie to Maven 2.0.6. In fact it even mentions  
2.0.8:
If you have not installed Maven, download the latest Maven 2.0 build  
from http://maven.apache.org/download.html and extract the  
distribution archive into your installation directory of choice, e.g. / 
opt/maven-2.0.8.

ref: http://bugs.sakaiproject.org/confluence/display/DOC/Install+Guide+-+Source+Install+%282.5%29#InstallGuide-SourceInstall%282.5%29-sourceinstall

In addition, the Development Environment Setup Walkthrough doesn't  
place a requirement on 2.0.6, and mentions 2.0.9:
Download Maven 2.0.x (minimum 2.0.6) - http://maven.apache.org/download.html
Extract to /opt (should create maven-2.0.9 folder)
Set environment variable: MAVEN2_HOME=/opt/maven-2.0.9
ref: http://bugs.sakaiproject.org/confluence/display/BOOT/Development+Environment+Setup+Walkthrough

So I'm not sure where the strict requirement for supporting the buggy  
2.0.6 came from. See the other thread regarding upgrading Maven  
required version.

--Steve

On 20 Apr 2009, at 12:16, Steve Swinsburg wrote:

> Ok this should be fixed and committed as r60268. I can successfully  
> build common on Maven 2.0.6 now. If anyone has any issues let me know.
>
>
> cheers,
> Steve
>
> ---
> Steve Swinsburg
> Portal Systems Developer
> Centre for e-Science
> Lancaster University
> Lancaster
> LA1 4YT
>
> email: s.swinsburg at lancaster.ac.uk
> phone: +44 (0) 1524 594870
>
>
>
>
>
>
>
> On 19 Apr 2009, at 09:53, David Horwitz wrote:
>
>> It raises an interesting question though if any of our nightly/qa  
>> instances are being built by maven 2.0.6? i suspect most are using  
>> at least 2.0.9
>>
>> D
>>
>> Aaron Zeckoski wrote:
>>>
>>> The quick summary is that using a scope other than provided in
>>> dependency management causes that dependency to fail when used in  
>>> any
>>> poms that inherit the DM. If you want to know more details about the
>>> failure then the previous threads on sakai-dev have some pretty good
>>> ones. Here is the issue ticket:
>>> http://jira.codehaus.org/browse/MNG-2919
>>>
>>> It is a known bug and this was known when the issue was discussed  
>>> last
>>> time but the community vote was to support 2.0.6. If you would  
>>> like to
>>> spearhead a vote to change the required version of maven in the poms
>>> and update the documentation to explain to OSX users how to upgrade
>>> maven then I think it is worth starting a new thread about it. I am
>>> pretty sure this needs to wait until after 2.6 is fully released and
>>> would have to be maintained separately from the 2.6.x code as well.
>>>
>>> -AZ
>>>
>>>
>>> On Sat, Apr 18, 2009 at 11:26 PM, Stephen Swinsburg
>>> <s.swinsburg at lancaster.ac.uk> wrote:
>>>
>>>> Sure. I'm still away though. After the previous issues I thought  
>>>> someone may
>>>> have already updated the poms. I'll do it when I get back in a  
>>>> few days if
>>>> no one else gets to it first.
>>>>
>>>> One point I'd like to raise, if the issue is that the scope  
>>>> cannot be
>>>> inherited from the project's main pom in Maven 2.0.6, ie from the
>>>> dependencyManagement block, and if this is a bug in Maven, then  
>>>> we need to
>>>> vote to use a newer Maven version and not support workarounds for  
>>>> bugs. I'm
>>>> not sure if it is a bug in the old versions or a feature from the  
>>>> later
>>>> versions (and can't look it up, the net connection here is too  
>>>> dodgy).
>>>>
>>>> +1 for a vote!
>>>>
>>>> cheers,
>>>> Steve
>>>>
>>>>
>>>>
>>>> On 18/04/2009, at 10:24 PM, Aaron Zeckoski wrote:
>>>>
>>>>
>>>>> Stephen,
>>>>> As you are the maintainer of this project, could you please  
>>>>> update it
>>>>> to work with maven 2.0.6. It is a small change and until the  
>>>>> community
>>>>> can vote to move support to a higher version of maven the trunk of
>>>>> sakai needs to build with 2.0.6. I can atest to this being a pain
>>>>> since I hit this problem first but asking everyone to upgrade was
>>>>> rejected as a solution at the time by the community.
>>>>>
>>>>> We could potentially vote on upgrading the supported maven  
>>>>> version but
>>>>> until then this should really be fixed.
>>>>> -AZ
>>>>>
>>>>>
>>>>> On Sat, Apr 18, 2009 at 8:16 AM, Stephen Swinsburg
>>>>> <s.swinsburg at lancaster.ac.uk> wrote:
>>>>>
>>>>>> Hi Tony,
>>>>>> If you update your Maven it should build. This project had been  
>>>>>> reworked
>>>>>> for
>>>>>> later versions of Maven.
>>>>>> As a general comment regarding updating Maven (as this issue  
>>>>>> came up last
>>>>>> week as well), I don't see why we need to rely on an older  
>>>>>> version of
>>>>>> Maven
>>>>>> (ie 2.0.6). Manually updating it on a Mac is simple. We should  
>>>>>> keep up to
>>>>>> date with this as we do with the other major dependencies like  
>>>>>> Tomcat and
>>>>>> JVM.
>>>>>>
>>>>>>
>>>>>> cheers,
>>>>>> Steve
>>>>>> ---
>>>>>> Steve Swinsburg
>>>>>> Portal Systems Developer
>>>>>> Centre for e-Science
>>>>>> Lancaster University
>>>>>> Lancaster
>>>>>> LA1 4YT
>>>>>>
>>>>>> email: s.swinsburg at lancaster.ac.uk
>>>>>> phone: +44 (0) 1524 594870
>>>>>> On 18/04/2009, at 4:38 AM, Tony Mendoza Rosa wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The Build Procedure of Sakai version 2.5.x failed while trying to
>>>>>>  Building
>>>>>> Sakai Common API Composite Component. At this point the SAKAI  
>>>>>> Deployment
>>>>>> stops because it can't find package org.hibernate, package
>>>>>> org.apache.commons.logging, package  
>>>>>> org.sakaiproject.api.common.type,
>>>>>> package org.sakaiproject.id.cover, and package
>>>>>> org.springframework.orm.hibernate3. Attached to this mail you  
>>>>>> will find
>>>>>> the
>>>>>> details of the errors.
>>>>>>
>>>>>> OS: Mac OS X Server 10.5.6
>>>>>> Hardware:  Dual PPC G5
>>>>>>
>>>>>> Maven Version: 2.0.6
>>>>>> Java Version:
>>>>>> java version "1.5.0_16"
>>>>>> Java(TM) 2 Runtime Environment, Standard Edition (build  
>>>>>> 1.5.0_16-b06-284)
>>>>>> Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode)
>>>>>>
>>>>>> Tomcat Version:  5.5.26
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>>
>>>>>> Tony Mendoza Rosa
>>>>>> University of Puerto Rico
>>>>>> Rio Piedras Campus
>>>>>>
>>>>>> < 
>>>>>> sakai_installation_error20090417 
>>>>>> .txt>_______________________________________________
>>>>>> 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"
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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"
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> Aaron Zeckoski (aaronz at vt.edu)
>>>>> Senior Research Engineer - CARET - Cambridge University
>>>>> [http://bugs.sakaiproject.org/confluence/display/~aaronz/]
>>>>> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
>>>>>
>>>>
>>>
>>>
>>>
>>>
>
> _______________________________________________
> 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/20090420/7234bc8a/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2437 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20090420/7234bc8a/attachment.bin 