History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MNG-2198
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Johann Reyes
Votes: 3
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Maven 2

Add <javadoc/> and <source/> to plugin metadata

Created: 01/Apr/06 04:49 PM   Updated: 21/May/08 07:41 AM
Component/s: Plugin API, Dependencies
Affects Version/s: None
Fix Version/s: 2.0.x

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Complexity: Intermediate


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

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
John Casey - 22/Jun/06 12:46 PM
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.


Johann Reyes - 22/Jun/06 01:26 PM
This is more for IDEs like Idea or eclipse to be able to download sources/javadocs for dependencies, right now these two projects uses some hacks to download the dependencies, since there is no method they can invoke to download sources or javadocs. Maybe not make it mandatory, but add a new method so these other dependencies (sources/javadocs) can be resolved in a standard way along with dependecy itself.

Michael Osipov - 21/May/08 07:41 AM
I'd agree to John Casey, this is a won't fix. If you want to integrate source and Javadoc into Eclipse, use me2eclipse, check the checkbox and m2eclipse pull sources and javadoc integrates into your invironment.

From this point of view this has nothing to do with maven and is a won't fix.