[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52072 ]
Barry Kaplan commented on MNG-1605: ----------------------------------- If [in the non-broke state] the sources will be used if they exists even without the flag, then running with the flag once in a while should be fine. Much simpler than adding dependency-level complexity, and agree with the "wont-fix". But when you say "remote" repository, do you mean anything other then the local cache? Or are repositories explictly defined considered non-remote also? > Allow eclipse source to be specified at the dependency level > ------------------------------------------------------------ > > Key: MNG-1605 > URL: http://jira.codehaus.org/browse/MNG-1605 > Project: Maven 2 > Type: New Feature > Components: maven-eclipse-plugin > Versions: 2.0 > Reporter: Barry Kaplan > > > Many (most?) projects do not have sources uploaded. And in any case, most > projects only need a small subset of the sources. Source downloading, even > (especially?) for sources that don't exist, is very time consuming. > Therefore, it would be nice to specify this eclipse plugin specific option as > the dependency level. Maybe something like: > <dependency> > <groupId>backport-util-concurrent</groupId> > <artifactId>backport-util-concurrent</artifactId> > <version>2.0_01_pd</version> > <scope>runtime</scope> > <properties> > <property name="eclipse.downloadSources" value="true"/> > </properties> > </dependency> > (For this to be general, it would of course require a much different model > than the simple plugin-level property injection. ) -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
