[ http://jira.codehaus.org/browse/MCHANGELOG-47?page=comments#action_73598 ] Dennis Lundberg commented on MCHANGELOG-47: -------------------------------------------
This plugin has not yet been released. That's why it is not available from ibiblio. If you want to try it out please read this document: http://maven.apache.org/guides/development/guide-testing-development-plugins.html "The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does not exist or no valid version could be found" This simply means that the plugin is not installed on you machine and is not available from the repos that you have defined. This is explained in the document mentioned above. The plugin uses maven-scm to handle the communication with your SCM. IIRC it doesn't support passing the password as a parameter. > Cannot find .cvspass file. Documentation not up-to-date. > --------------------------------------------------------- > > Key: MCHANGELOG-47 > URL: http://jira.codehaus.org/browse/MCHANGELOG-47 > Project: Maven 2.x Changelog Plugin > Issue Type: Bug > Affects Versions: 2.0-beta-1 > Environment: Maven2 on Windows in Eclipse with CVS (anonymous pserver) > Maven2 on GenToo in CruiseControl with CVS (anonymous pserver) > Reporter: Paul R. Saxman > > I've run into a few issues while using this plugin, which are as follows: > - When I try to run the Maven 2 changelog plugin in Eclipse or using > CruiseControl, I get an error that the file .cvspass cannot be found. > - I've found a reference to the .cvspass file on the Maven 1 plugin > documentation, but not in the Maven 2 documentation. > - The Maven 2 documentation specifies to use the groupId > org.apache.maven.plugins for the plugin, which doesn't exist on ibiblio. The > plugin actually exists at org.codehaus.mojo; HOWEVER, it is not documented as > being part of Mojo at http://mojo.codehaus.org. > - When I follow the Maven 1 instructions to generate the .cvspass file, I get > the error "The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does > not exist or no valid version could be found". > - Passing in a password (which doesn't really exist since I'm using an > anonymous pserver) using the Maven 2 plugin "password" parameter has no > effect, which is consistent with the documentation. Is there any way to not > bother with a password or to specify an empty password? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
