[ http://jira.codehaus.org/browse/MNG-1886?page=comments#action_54344 ]
Vincent Massol commented on MNG-1886: ------------------------------------- I'm talking about sharing configuration elements (fields). Here's an example: <configuration> <cloverDatabase>...</cloverDatabase> <jdk>...</jdk> [...] Is there any doc on the plugin context? I don't think this is what I'm after though. Try writing a plugin which has both reporting mojos and main mojos and you'll see what I mean. Alternatively you could have a look at the clover plugin. Search for MNG-1886 in the code and you'll find the places where it's awkward and would ideally require a better design. This is an issue about code duplication, maintenance and consistency in general. I think the issue's title can be changed to; "How to share configuration elements between mojos when inheritance is not possible". The example you give about the MavenArchiveConfiguration require the introduction of another level of configuration for users. I'm talking about sharing the top level. Thanks > Need way to share code between report mojos and main build mojos > ---------------------------------------------------------------- > > Key: MNG-1886 > URL: http://jira.codehaus.org/browse/MNG-1886 > Project: Maven 2 > Type: Improvement > Components: Plugin API > Versions: 2.0.1 > Reporter: Vincent Massol > Assignee: Brett Porter > > > For example in the clover plugin i have both report mojos and main build > mojos. They need to share lots of configuration elements and common methods > but it's not easy to do so because each type needs to extend either > AbstractMavenReport or AbstractMojo. Of course I could not extend > AbstractMavenReport and instead implement the interface but then I'll have to > reimplement all its methods. -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
