[Contrib: Evaluation System] versions in 1.3.x pom's

[Jim Eng]

That sounds good, David.  Does that mvn goal set the sakai version (and update dependencies) or the evalsys version?

Jim

 
On Sep 8, 2010, at 10:23 AM, David Horwitz wrote:

> I will happily fix this if there is consensus on what the version should by.
> 
> FYI the quick way to do this:
> 
> #mvn versions:set -DnewVersion=[versionnumber]
> 
> D
> 
> On 09/08/2010 04:07 PM, Jim Eng wrote:
>> The EVALSYS version in the pom.xml files in the 1.3.x branch are still 1.2.2.  This can lead to errors (or at least confusion) if a developer works with 1.3.x and already has 1.2.2 artifacts in the maven repo.  Any plans to update those versions soon?
>> 
>> Also, was a decision reached about using sakai 2.6.x or later as the parent for 1.3.x? Or maybe using profiles to facilitate building/deploying with 2.5, 2.6 or 2.7 without having to migrate pom's locally each time?  
>> 
>> Thanks.
>> 
>> Jim
>> _______________________________________________
>> evaluation mailing list
>> evaluation at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/evaluation
>> 
>> TO UNSUBSCRIBE: send email to evaluation-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
> _______________________________________________
> evaluation mailing list
> evaluation at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/evaluation
> 
> TO UNSUBSCRIBE: send email to evaluation-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
>