[
https://issues.apache.org/jira/browse/MECLIPSE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15475316#comment-15475316
]
dw yu commented on MECLIPSE-292:
--------------------------------
That's really cool. I would be interested in seeing more graphs of different
information you pull from these logs.
http://pokemongozoner.com/
http://hybridsfilm.com/pokemongohack
> Behaviour for sources and Javadoc attachement for dependencies should be
> consistent
> -----------------------------------------------------------------------------------
>
> Key: MECLIPSE-292
> URL: https://issues.apache.org/jira/browse/MECLIPSE-292
> Project: Maven Eclipse Plugin (RETIRED)
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.4
> Environment: Windows XP, Maven 2.0.6, maven-eclipse-plugin
> 2.4-20070628.215652-24
> Reporter: Denis Cabasson
> Assignee: Brian Fox
> Priority: Minor
> Fix For: 2.5
>
> Attachments: MECLIPSE-292-fixbug.patch, MECLIPSE-292-updated.patch,
> MECLIPSE-292.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
