Re: svn commit: r440862 - /maven/plugins/trunk/maven-changes-plugin/pom.xml

2006-09-12 Thread Brett Porter
I suggest using '3' for the release (which has the problem), then republishing the site with the new version. See my separate thread on moving the plugin tools for fixing this properly. On 13/09/2006, at 2:22 AM, Dennis Lundberg wrote: Vincent, I can confirm this on my setup as well. The

Re: svn commit: r440862 - /maven/plugins/trunk/maven-changes-plugin/pom.xml

2006-09-12 Thread Dennis Lundberg
Vincent, I can confirm this on my setup as well. The reason for bumping the version of the parent was to prepare for a release (see separate vote thread). From what I understand a release cannot be made if there are any SNAPSHOT-dependencies. Let's see I get this... When I fixed (updated to a

Re: svn commit: r440862 - /maven/plugins/trunk/maven-changes-plugin/pom.xml

2006-09-10 Thread Brett Porter
Yes, we require the snapshot of the plugin-plugin to do that. - Brett On 11/09/2006, at 6:35 AM, Vincent Siveton wrote: Hi Dennis, When calling mvn site, this bump seems to overwrite the generated index.html (ie from index.apt) by a default index. Works a treat with maven-plugins:2-SNAPSHOT o

Re: svn commit: r440862 - /maven/plugins/trunk/maven-changes-plugin/pom.xml

2006-09-10 Thread Vincent Siveton
Hi Dennis, When calling mvn site, this bump seems to overwrite the generated index.html (ie from index.apt) by a default index. Works a treat with maven-plugins:2-SNAPSHOT or 4-SNAPSHOT I used maven-site-plugin:2.0-beta-5 Cheers, Vincent 2006/9/6, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: Autho