[Building Sakai] maven v2.2.1

[Steve Swinsburg]

Yes, I was going to do something similar but like:

/tags/1.1.0_2.5.x
/tags/1.1.0_2.6.x
/tags/1.2.0_2.5.x
/tags/1.2.0_2.6.x

etc. ie without the extra directory.

Possibly even matching up with a specific point release as well:
/tags/1.1.0_2.5.5
/tags/1.1.0_2.5.6
/tags/1.1.0_2.6.0
/tags/1.1.0_2.6.1

just to save people editing the POM. The only difference would be the  
POM version in all of these. The only issue I have with doing this is  
you need to make a dozen tags every time you make a new release of the  
tool. That's why I'd like to move to binary releases so you can just  
drop in an updated version number in your deploy POM and it's all done  
(assuming the new version doesn't depend on new features not available  
in older versions of Sakai).

cheers,
Steve

On 14/11/2009, at 10:05 AM, Thomas Amsler wrote:

> Please see inline comment bellow:
>
> On Fri, Nov 13, 2009 at 2:30 PM, Steve Swinsburg
> <steve.swinsburg at gmail.com> wrote:
>> I'm using 2.0.9 on my Macbook Pro and the build profile technique  
>> works for
>> me (if I build from the top level). It doesn't seem to work under the
>> following:
>> 1. If your app is being included in a larger build, like the whole  
>> for
>> Sakai/
>> 2. If you descend into a submodule and try to build, it will fail.
>>
>> I'm not sure if this is version related or not though. I'm going to  
>> upgrade
>> Maven on this machine soon so we'll see.
>>
>> Nevertheless I'm eventually ditching the build profiles in favour  
>> of cutting
>> tags aimed at specific versions of Sakai (for source releases), and  
>> pushing
>> the binary deployment of tools so its easier for everyone to add an  
>> app to
>> the mix:
>> http://steve-on-sakai.blogspot.com/2009/10/binary-deployment-of-sakai.html
>> http://steve-on-sakai.blogspot.com/2009/11/binary-deployment-of-your-sakai-tool.html
>
> That makes sense. How do indicate which version of your tool is
> compatible with what Sakai version.
>
> So if you have a v1.1.0, 1.2.0, etc., how do you indicate/document
> Sakai version compatibility?
>
> I was thinking of use some folder naming convention. So if we have our
> standard setup:
>
> /trunk
> /branches
> /tags
>
> I would add:
> /tags/2.5.x/1.1.0
> /tags/2.6.x/1.2.0
> /tags/2.6.x.1.2.1
> etc.
>
> Best,
> -- Thomas
>
>>
>> cheers,
>> Steve
>>
>> On 14/11/2009, at 5:22 AM, Thomas Amsler wrote:
>>
>>> Thank you for the information.
>>>
>>> I am using your approach to make the pom.xml files compatable with
>>> pre-K1/K1 as described here:
>>> http://bit.ly/3FWrwT
>>>
>>> Do you know what version of maven is required to support that? I  
>>> tried
>>> v2.0.9 but it didn't work.
>>>
>>>
>>> Best,
>>> -- Thomas
>>>
>>>
>>>
>>>
>>> On Thu, Nov 12, 2009 at 8:51 PM, Steve Swinsburg
>>> <steve.swinsburg at gmail.com> wrote:
>>>>
>>>> I've also been using 2.2.1 but I believe the recommended version  
>>>> is at
>>>> least
>>>> 2.0.9.
>>>> The master/pom.xml has
>>>> <prerequisites>
>>>>        <maven>2.0.6</maven>
>>>>   </prerequisites>
>>>> although the kernel has 2.0.10 as its pre-req if you build that
>>>> separately.
>>>> After 2.0.9 though there aren't any bugs or features we need a  
>>>> higher
>>>> version for so far since I also build happily on 2.0.9 on a  
>>>> different
>>>> machine. There *was* an issue that we were essentially working  
>>>> around
>>>> below
>>>> this version though, and it was on list back around Easter this  
>>>> year (it
>>>> was
>>>> an issue with the Common build).
>>>> cheers,
>>>> Steve
>>>>
>>>> On Fri, Nov 13, 2009 at 3:42 PM, Thomas Amsler <tpamsler at ucdavis.edu 
>>>> >
>>>> wrote:
>>>>>
>>>>> I have been using maven v2.2.1 to build both Sakai v2.5.x and  
>>>>> v2.6.x.
>>>>> So far, I haven't seen any issues using v2.2.1 to build Sakai.  
>>>>> What is
>>>>> currently the recommended maven version to build Sakai?
>>>>>
>>>>> Best,
>>>>> -- Thomas
>>>>> _______________________________________________
>>>>> 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"
>>>>
>>>>
>>
>>