Second step done:1. change master pom to use the new repo, release it and use it in all pax projects 2. change other ops4j poms that were using the maven2 repo for release.
On Fri, May 22, 2009 at 3:10 PM, Alin Dreghiciu <adreghi...@gmail.com>wrote: > First step done: > Created a new repository: http://repository.ops4j.org/mvn-releases/ which > now contains only ops4j related artifacts. > The "old" http://repository.ops4j.org/maven2 has now a symbolic link to > the new repo for org/ops4j. > > next: > 1. change master pom to use the new repo, release it and use it in all pax > projects > 2. change other ops4j poms that were using the maven2 repo for release. > > -- > Alin Dreghiciu > Software Developer - Looking for new projects! > My profile: http://www.linkedin.com/in/alindreghiciu > My blog: http://adreghiciu.blogspot.com > http://www.ops4j.org - New Energy for OSS Communities - Open Participation > Software. > http://www.qi4j.org - New Energy for Java - Domain Driven Development. > -- Alin Dreghiciu Software Developer - Looking for new projects! My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.blogspot.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development.
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
