Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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:
    Ofcourse, you will need to add the maven-project-info-reports-plugin to your <reports/> section.

Change report and issue tracking

In the pom.xml:

(Note the & instead of &)

Then add the changes plugin to the reports:

You need to customize atid, group_id, aid for your project.

group_id refers to your project
atid refers to the section (bugs, feature request or patch)
aid refers to the issue number

Now in your change.xml, you can put:

This will generate a link for your issue like this:
%URL% =;group_id=61302
%ISSUE% = 1554148

The only problem I have with this configuration is I can't add a link for feature requests or patches (only bugs)

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.
  • No labels