PLDoc Project Changes

New Release Process

Sometime after August of last year the legacy automated background process that synchronised PLDoc releases on Sourceforge to the Maven Central repository was turned off. Since then there have been several releases which did not appear in http://search.maven.org.

We have just got around to changing the projects to use the recommended approach to pushing releases to Maven Central: they now go via the Sonatype OSS repository. The backlog of invisible releases has been released manually and the Maven projects are currently being altered to deploy to the OSS Maven repository.

New Project Format

At the same time we are taking advantage of the opportunity to migrate the PLDoc project to Sourceforge's new project format. As the migration involves relocation of the Subversion source code repositories, any developers should check out the source code again, using this command line (or equivalent settings):-


svn checkout --username=username svn+ssh://username@svn.code.sf.net/p/pldoc/code/ pldoc-code


For more information on how to switch your Subversion repository please read https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/.