Well, the site plugin uses the previous version of itself for its own site plugin. I've seen another site-related plugin use its own version. It noted in the comments that it needed to be installed before the site could be built.
I'll investigate further. -K On Apr 3, 2010, at 3:38 AM, Stephen Connolly wrote: > In general, a project cannot consume any maven plugins that it produces (as > the plugins which have not been built yet could have an unknown effect on > the build plan) > > I wonder if the same applies to extensions and wagons > > -Stephen > > On 3 April 2010 04:54, Kathryn Huxtable <kath...@kathrynhuxtable.org> wrote: > >> So I've deployed this crude hack of wagon-scm to >> >> http://github.com/khuxtable/wagon-gitsite >> >> and I thought it would be cool if it deployed its own documentation there. >> So I added the extensions to the POM and generated the site and did a >> site:deploy and got: >> >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Unsupported protocol: 'gitsite' >> >> Embedded error: Cannot find wagon which supports the requested protocol: >> gitsite >> Component descriptor cannot be found in the component repository: >> org.apache.maven.wagon.Wagongitsite. >> >> The wagon-gitsite artifact build and installed successfully. It works in my >> test project. >> >> What gives? And what's the org.apache.maven.wagon.Wagongitsite reference >> doing there? The artifact coordinates are >> >> org.kathrynhuxtable.maven:wagon.wagon-gitsite:0.1-SNAPSHOT >> >> Any ideas? >> >> -K, who deployed the site manually. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
