[
http://jira.codehaus.org/browse/MGROOVY-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134685#action_134685
]
Jason Dillon commented on MGROOVY-142:
--------------------------------------
I think the _trick_ is to do something like {{mvn install site}} so that the
normal groovy tasks execute and add the additional paths to the build. I'm
really starting to think about just using src/main/java and src/test/java for
the java+groovy mixed bits, cause maven's lack of support to deal with other
paths (and have other plugins know about them easily) just plain sucks ass.
> Javadoc plugin must be configured to use generated stubs, docs do not specify
> this
> ----------------------------------------------------------------------------------
>
> Key: MGROOVY-142
> URL: http://jira.codehaus.org/browse/MGROOVY-142
> Project: GMaven
> Issue Type: Bug
> Components: site
> Reporter: Luke Daley
> Assignee: Jason Dillon
> Priority: Minor
>
> I can't javadoc to use the stubs unless I specify it manually in the config
> with sourcepath. If this is the intended behaviour, it should be documented
> in the wiki (which I am happy to do), but the current documentation
> insinuates it should happen automatically.
--
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
