#81 sourceforge:changes fails under Maven 1.1

[James Dempsey]

I have just upgraded to maven 1.1 and reinstalled the sourceforge plugin (v1.3). The sourceforge:changes goal fails as it is using the plugin directory as the base rather than the project base. The following code works correctly though:

<goal name="sourceforge:changes" prereqs="sourceforge:init"
description="Creates the CHANGES.txt file">

<!-- Generates the changes.txt file -->

<util:available file="${basedir}/xdocs/changes.xml">
<util:file var="inputFile" name="${basedir}/xdocs/changes.xml"/>
<x:parse var="root" xml="${inputFile}" />
<j:set var="version" value="${maven.sourceforge.project.version}" />
<ant:mkdir dir="${maven.dist.dir}" />

<velocity:merge
name="${maven.sourceforge.project.changeNotes}"
basedir="${plugin.resources}/templates"
template="changes.vm"
/>
</util:available>

</goal>

[Jeff Jensen]

Logged In: YES
user_id=498804
Originator: NO

Thanks!

I published a 1.4-SNAPSHOT to the SF snapshot repo (http://maven-plugins.sourceforge.net/snapshot-repository/maven-plugins/) containing your change. Please test and let me know!

Note that Stephen Colebourne had some other corrections in progress in a previous 1.4 snapshot - see bug #1363121:
https://sourceforge.net/tracker/index.php?func=detail&aid=1363121&group_id=61626&atid=497853

It appears the issue was never resolved... I'm surprised 1.3 worked for you after correcting the path, based on Stephen's comments and work to update 1.3 to work with the SF changes.

Did you test your change with your old Maven 1.0 builds? We should know if your suggested change breaks that or not. Please also test that if you can so we can note if 1.4 breaks Maven 1.0 compatibility!

[Stephen Colebourne]

Logged In: YES
user_id=408725
Originator: NO

I had to give up working on this plugin as I have too many other commitments. I also found sourceforge kept changing, and keeping the pugin up to date was difficult (also difficult to test).