About this link, why couldn't we have a consistent behaviour for javadoc and sources jar?
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? To be followed in : http://jira.codehaus.org/browse/MECLIPSE-292 Denis. > -----Message d'origine----- > De : Mark Hobson [mailto:[EMAIL PROTECTED] > Envoyé : Tuesday, July 03, 2007 4:08 PM > À : Maven Developers List > Objet : Re: [VOTE] Configure IDE plugins to download sources > by default within Maven projects > > On 03/07/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > +1 to Javadoc > > > > -1 to sources (just a vote, not a veto :) > > In the eclipse plugin, the downloadSources flag controls them both: > http://maven.apache.org/plugins/maven-eclipse-plugin/faq.html# > import-javadoc > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
