[Building Sakai] lesson builder binaries

Steve Swinsburg steve.swinsburg at gmail.com
Fri Feb 10 04:51:12 PST 2012


Why do you need to distribute a binary for 2.8? It sounds like there is a lot of mucking about, just have older versions build from source. Everyone that responded said they were building from source anyway. But you really can't have this fiddling about in a release. I'm not trying to be difficult, but we do need to focus on a stable release for 2.9.

In the pom for the 1.4.0-b02 tag I see these properties for dependency versions, which are not commented out:

<sakai.yaft.version>1.2.1-SNAPSHOT</sakai.yaft.version>
<sakai.mneme.version>1.2-hack</sakai.mneme.version>
<rsfutil.version>0.8-SNAPSHOT</rsfutil.version>
<sakairsf.version>0.8-SNAPSHOT</sakairsf.version>
<sakai.basiclti.version>2.0-SNAPSHOT</sakai.basiclti.version>

I know that these are for optional tools, but even so, a tagged release needs to depend on stable dependencies.

Is there anyway to extract the optional modules into some sort of extension libraries and they can be installed separately? Then you could have a core release with the main functionality and deployers can add in the modules they want (i.e. clog, mneme)

Then you can:

>>  … focus on trunk (which is actually 2.10) and provide instructions for running on 2.8. If people want to run a tool designed for a later version of Sakai, and the binary is incompatible, then building from source is what needs to be done.

And we can deliver binaries for 2.9 onwards from the Sakai maven repo.

regards,
Steve




On 10/02/2012, at 11:26 PM, Hedrick Charles wrote:

> As far as I can see this email does not contain a practical answer to the requests for a binary that will work with 2.8. I have enough trouble now keeping patches in sync with several versions, I don't think it's very attractive to maintain separate branches that differ only in a few lines in the pom file. 
> 
> If you object to having the binary in svn, I can put it on a Rutgers server. I thought it would make more sense to put it where people would normally look.
> 
> 
> On Feb 9, 2012, at 10:52:10 PM, Steve Swinsburg wrote:
> 
>> To target different code to different versions of Sakai you'll need to use a branch. The various releases can then be built from there. 
>> 
>> Alternatively, focus on trunk (which is actually 2.10) and provide instructions for running on 2.8. If people want to run a tool designed for a later version of Sakai, and the binary is incompatible, then building from source is what needs to be done.
>> 
>> This tool is on the list for 2.9, and the 1.4.x branch is where releases are being published from, however those are still including snapshot and other (-hack?) dependencies. This needs to be cleaned up.
>> 
>> In general, the release team handles the releases of projects but you need to get the dependencies in order for that to happen.
>> 
>> cheers,
>> Steve
>> 
>> 
>> 
>> 
>> On 10/02/2012, at 2:01 PM, Hedrick Charles wrote:
>> 
>>> The problem is that the normal build generates binaries for 2.9. I don't think I have permissions to put things anywhere other than svn.
>>> 
>>> Because of limitations in mvn, building a 2.8 version requires changes in the pom.xml file. If you can think of a way to get the release process to build a separate version of code with a separate pom file that would be great.
>>> 
>>> 
>>> On Feb 9, 2012, at 7:15:02 PM, Steve Swinsburg wrote:
>>> 
>>>> Hi Chuck,
>>>> 
>>>> These shouldn't go into SVN. Binaries (ie tomcat overlays) are created as part of the release process and uploaded to the Sakai maven repo. The source is also automatically tagged as part of this process (when releasing actual stable artifacts).
>>>> 
>>>> People can then include a pom block in core-deploy and they are automatilcally retrieved and unpacked, like how the others in there are deployed (profile2, sites stats etc)
>>>> 
>>>> Do you have permissions to do a Maven release? If not, I can check out the source and push a release for you.
>>>> 
>>>> I see a lot of snapshot dependencies in the 1.4 branch though so before a stable release can be tagged and packaged, they need to be stabilised. Instead we can create a snapshot release of the 1.4 branch for now.
>>>> 
>>>> cheers,
>>>> Steve
>>>> 
>>>> 
>>>> On 10/02/2012, at 10:53 AM, Hedrick Charles wrote:
>>>> 
>>>>> I've just uploaded
>>>>> 
>>>>> https://source.sakaiproject.org/svn/lessonbuilder/binaries/lessonbuilder-assembly-1.4-sakai2.8.1-tomcat-overlay.zip
>>>>> 
>>>>> This is a ZIP file with binaries, designed to be unzipped in the main tomcat directory. 
>>>>> 
>>>>> This is the version being run at Rutgers, except using RSF 0.7.5 rather than 0.8-SNAPSHOT. It is built for 2.8.1, but I believe it will work for 2.8 as well. Please tell me if it doesn't and I'll do a separate one.
>>>>> 
>>>>> _______________________________________________
>>>>> 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"
>>>> 
>>> 
>> 
> 



More information about the sakai-dev mailing list