You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/06/22 19:47:40 UTC

[jira] Updated: (MNG-2198) Add and to plugin metadata

     [ http://jira.codehaus.org/browse/MNG-2198?page=all ]

John Casey updated MNG-2198:
----------------------------

    Fix Version: 2.0.5

Not sure what you mean here...as long as those artifacts are published with a plugin release, you should be able to resolve them...

If you're suggesting we make it mandatory to resolve source/javadoc along with the plugin itself, regardless of whether they're going to be used, then I disagree strongly.

> Add <javadoc/> and <source/> to plugin metadata
> -----------------------------------------------
>
>          Key: MNG-2198
>          URL: http://jira.codehaus.org/browse/MNG-2198
>      Project: Maven 2
>         Type: New Feature

>   Components: Plugin API, Dependencies
>     Reporter: Johann Reyes
>      Fix For: 2.0.5

>
>
> Add to the plugin metadata <javadoc/> and <source/>  support so related source/javadoc are resolved as well along the dependency itself.

-- 
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