[Building Sakai] unnecessary POM changes

Matthew Buckett matthew.buckett at oucs.ox.ac.uk
Wed Apr 7 02:10:42 PDT 2010


On 3 April 2010 15:11, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

Creating 2.7 versions of the pom.xml files with relocation elements to
the new groupId/artifactIds would help local deployers with this
transition:

http://maven.apache.org/guides/mini/guide-relocation.html
http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_relocation

As with a relocation POM maven will just go and find the actual
artifact and then we could maybe drop this in 2.8?

A bit like deprecation in Java, you create the new thing  and leave
the old one in place (with a note pointing to the new version), then
after most people have caught up you delete the old one.

-- 
  Matthew Buckett
  VLE Developer, LTG, Oxford University Computing Services


More information about the sakai-dev mailing list