MavenAndSourceforge

...

<issueManagement>
  <system>sourceforge</system><!--don't care-->
  <url>http://sourceforge.net/tracker/?atid=497982&amp;group_id=61302</url>
</issueManagement>

(Note the & instead of &)Do not forget to set your own sourceforge group_id.

Then add the changes plugin to the reports:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-changes-plugin</artifactId>
  <inherited>false</inherited>
  <reportSets>
    <reportSet>
      <reports>
        <report>changes-report</report>
      </reports>
    </reportSet>
  </reportSets>
  <configuration>
    <issueLinkTemplate>%URL%<issueLinkTemplate>http:/index.php?func=detail&amp;aid=%ISSUE%&amp;group_id=61302&amp;atid=497982</sourceforge.net/support/tracker.php?aid=%ISSUE%</issueLinkTemplate>
  </configuration>
</plugin>

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% = by replacing %ISSUE% with issue attribut value. (With the previous example: http://sourceforge.net/support/tracker/.php?atid=497982&group_id=61302
%ISSUE% = 1554148The only problem I have with this configuration is I can't add a link for feature requests or patches (only bugsaid=1554148)

Deploy the site

• Add a distribution management section to your pom.xml:

  Code Block
  <distributionManagement> <site> <id>sourceforge.net</id> <url>scp://shell.sourceforge.net/home/groups/v/vi/vigilog/htdocs</url> </site> </distributionManagement>

  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.

...