2013/1/27 Robert Scholte <[email protected]>
> mvn site should do the trick. (works on my machine with this project)
> I noticed that the version of the m-site-plugin is locked on 3.0-beta-3,
> which means it'll only work with M3.0+
>
I've had a look at the parent pom hierarchy, and this actually seems to
come from a profile in org.codehaus:codehaus-parent:4 that'll activate that
version of the site plugin only when using Maven 3.x.
*<profile>*
* <id>maven-3</id>*
* <activation>*
* <file>*
* <!-- This employs that the basedir expression is only recognized
by Maven 3.x (see MNG-2363) -->*
* <exists>${basedir}</exists>*
* </file>*
* </activation>*
* <properties>*
* <!-- MLICENSE-26 : maven-site-plugin 3.0 has some problem... -->*
* <sitePluginVersion>3.0-beta-3</sitePluginVersion>*
* </properties> *
Without it, it keeps using 2.3
Cheers
> Robert
> ------------------------------
> From: [email protected]
> Date: Sun, 27 Jan 2013 17:10:47 +0100
> To: [email protected]
> Subject: [mojo-dev] Unable to generate mojo documentation (using java5
> annotations)
>
>
> Hi all,
>
> I'm working on the templating-m-p in the sandbox. I'm trying to generate
> the standard documentation of the mojo.
> I've already added the site folder and some files based on what I can see
> in some others plugin, but I'm still unable to generate any other mojo
> documentation than the HelpMojo one (which is configured in the POM).
>
> I had a look at the last m-resources-p version to see how it was doing
> that, but don't see what I'm missing.
>
> Is there any public doc about this?
> If not, I guess I'll volunteer to improve this since as Stephen said
> recently, we might want to push people start using java5 mojos?
>
> Thanks a lot for any hint.
> PS: Just committed the current state.
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor ! nbsp;!
>
