[Building Sakai] unnecessary POM changes

[Steve Swinsburg]

Hi Charles,

Many of these changes have been made to projects which are now on an independent release cycle (Profile2, Site Stats, Message Centre, Samigo et al). The POM changes were made to bring the repository into line with the Maven coordinate naming conventions:
http://maven.apache.org/guides/mini/guide-naming-conventions.html
http://maven.apache.org/pom.html#Maven_Coordinates

These changes mean that the artifacts are now all grouped together in the repository. See also:
http://steve-on-sakai.blogspot.com/2009/10/binary-deployment-of-your-sakai-tool.html

In addition, a number of service API's have been bundled together into framework packages, in order to rationalise the dependency tree: Common (SakaiPerson, Archive, Privacy etc) and Edu-Services (CourseManagement, Gradebook, Sections). This was announced in October 2009:
http://n2.nabble.com/2-7-Framework-commons-and-edu-servise-1-0-0-beta01-released-td3834287.html

cheers,
Steve



On 03/04/2010, at 2:23 AM, Charles Hedrick wrote:

> Rutgers is about finished producing a local version of 2.7. We use several contrib and local tools. Most of the time spent moving to 2.7 has been unscrambling changes to POM files that seem completely unnecessary. group names and artifact names have been changed by adding or deleting sakai-, and other changes that have no obvious functional purpose. The changes are easy, but finding them in a package with which you aren't familiar can take a while. I'd like to ask developers not to make changes that will break POM files unless there's a really good reason.
> 
> _______________________________________________
> 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"