Hi Benjamin, In order to promote our maven plugin (scmchangelog-maven-plugin) from >> sandbox to mojo, we are following the Performing a release guide (cf. >> http://mojo.codehaus.org/development/performing-a-release.html) to >> perform >> our first release. >> > > Not sure I understand properly but that sounds strange: AFAIK, graduation > from sandbox happens > a) after a corresponding vote > b) before a first release >
I've put it badly In fact, we know that and we will launch a vote soon. But before we just wanted to be sure that all is ok When we launch the docck:check command, we have the following error : > [ERROR] Cannot reach project site with URL: ' > http://mojo.codehaus.org/mojo-sandbox/scmchangelog-maven-plugin'. > > We wonder why the docck:check goal check if our maven plugin web site > exists. > The motivation might be to catch inconsistencies between site deployment and > project metadata. For instance, the URL > http://mojo.codehaus.org/mojo-sandbox/scmchangelog-maven-plugin > is taken from ${project.url} and is indeed wrong, the site is actually > located at > http://mojo.codehaus.org/scmchangelog-maven-plugin/ > > This particular issue revealed a bug in the Mojo Sandbox Parent which I > just fixed, i.e. after inheriting from mojo-sandbox-parent:5-SNAPSHOT the > project URL should be in sync with the actual deployment location. It works well now, thanks. > Do we have first to deploy our maven plugin web site before to do our >> first >> release ? >> > > Somebody has already deployed a snapshot site, so the URL is already there. > Yes you have right. Thanks, Rémy
