[
http://jira.codehaus.org/browse/MGROOVY-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166988#action_166988
]
Jason Dillon commented on MGROOVY-188:
--------------------------------------
I believe that is because the stubs are generated into
target/generated-sources/groovy/** and the stub generation goals automatically
add the generated-sources directories to the build roots. ATM I'm not sure how
to fix this...
> Can't build site for plugin project because mojos are not detected
> ------------------------------------------------------------------
>
> Key: MGROOVY-188
> URL: http://jira.codehaus.org/browse/MGROOVY-188
> Project: GMaven
> Issue Type: Bug
> Components: compile
> Reporter: Dave Syer
> Assignee: Jason Dillon
>
> Can't build site for plugin project because mojos are not detected. Create a
> mojo project, and add the standard reporting stanza to the pom:
> {code}
> <reporting>
> <plugins>
> <plugin>
> <artifactId>maven-plugin-plugin</artifactId>
> </plugin>
> </plugins>
> </reporting>
> {code}
> Then do "mvn site" and watch the big warning on the console. The generated
> site has no information about the plugins (a plugin-info.html might be
> generated, but there's nothing useful in it).
> Looks like the site goal is not able to compile the groovy code into proper
> Mojo classes?
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
