You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/07/04 19:01:13 UTC
[jira] Updated: (MECLIPSE-292) Behaviour for sources and Javadoc
attachement for dependencies should be consistent
[ http://jira.codehaus.org/browse/MECLIPSE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MECLIPSE-292:
-------------------------------
Fix Version/s: (was: 2.4)
> Behaviour for sources and Javadoc attachement for dependencies should be consistent
> -----------------------------------------------------------------------------------
>
> Key: MECLIPSE-292
> URL: http://jira.codehaus.org/browse/MECLIPSE-292
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: dependency resolution
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.6, maven-eclipse-plugin 2.4-20070628.215652-24
> Reporter: Denis Cabasson
> Priority: Minor
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Why couldn't we have a consistent behaviour for javadoc and sources jar attachment?
> Why not adding a downloadJavadoc property, which, when set to true, would download and attach the javadoc to the dependency.
> I don't really see why javadoc should be a fallback if sources are not available.
> Some developpers might prefer to have javadoc linked, some sources linked and some both. Shouldn't the eclipse plugin allow for all the possiblities instead of stating that the preferred option is always to get the sources instead of the Javadoc?
--
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