Skip to end of metadata
Go to start of metadata

Maven and Sourceforge

This page is a starting point for anyone that uses Maven and The intention is to provide a step-by-step guide on deploying your site and your files using Maven onto

Upload the website

SCM information

  • Download and install putty(Easiest is to use the windows installer)
  • Install svn itself (not only tortoiseSVN, otherwise you get an error from the scm plugin)
  • Add the scm information to your pom.xml (see This is an example if you use subversion:
  • Use
    to check your scm information
  • Use
    , just to test the connection to sourceforge. If you get the error
    svn: PROPFIND of '/svnroot/vigilog/trunk': Server certificate verification failed: issuer is not trusted (
    , then run the svn command manually: "svn log -v" and choose "accept permanently". After that, run the maven command again.

Mailinglists and forums

  • If you use mailinglists, you can add them to your pom.xml as follows:
    Of course, you will need to add the maven-project-info-reports-plugin to your <reports/> section.

Change report and issue tracking

In the pom.xml:

Do not forget to set your own sourceforge group_id.

Then add the changes plugin to the reports:

Now in your change.xml, you can put:

This will generate a link for your issue by replacing %ISSUE% with issue attribut value. (With the previous example:

Deploy the site

  • Add a distribution management section to your pom.xml:
    Use the correct directory for your own project. Note that you have to use lowercase for the directories, otherwise the Maven plugin will try to create directories where it has no permissions.
  • Put this section in your settings.xml. Make sure the id's match!
    Replace username and password ofcourse.
    Sidenote: the "775" means owning user can do anything, all users of the owning group
    can do anything, anybody else can read and execute. This is important if you want others (besides yourself) to be able to update the website.
  • Deploy your website by using "mvn site:deploy"
    You will get a warning "The authenticity of host '' can't be established.", but just type "yes" to continue.


  1. Instead of putting your sourceforge user in the pom (could be a problem when sharing with multiple developpers), you can put it in settings.xml:

  2. Hi, thank you very much for the instructions!

    It would be nice to learn also how to publish artifacts to a public Maven repository. The only way I've found so far is to use Sonatype's repository hosting for open-source projects, mvn deploy to their repository and let them push the artifacts to the Central repository. I'm just exploring this for my project