It should be a strategy that encompases dependencies, artifact publishing, and all IDE plugins as well as fitting in with maven 2.0 plans.
I really don't like this properties syntax. The ID's will match, so I think it may be more of a global link source option, or a "with source" property if it is per dependency.
I'm a bit torn on this - I don't like the verbosity of having to list source deps alongside matching deps (And the fact they should be same), but I don't like the duplicity of ading multiple functions to a dependency.
Best that I sleep on it :) But its about time we started thinking about this one.
- Brett
Eric Pugh wrote:
Hi all,
I have been looking at "http://jira.codehaus.org/browse/MPECLIPSE-26 Add a property to dependencies to link to source". It would be quite easy to add some sort of property to each dependency specifing the name of a file that would be in your repository. Something like:
<dependency> <groupId>commons-lang</groupId> <artifactId>commons-lang</artifactId> <version>2.0</version> <url>http://jakarta.apache.org/commons/lang/</url> <properties> <eclipse.src>commons-lang-src-2.0.zip</eclipse.src> </properties> </dependency>
Then the plugin would expect this file to exist in: $MAVEN_REPO/commons-lang/src/commons-lang/commons-lang-src-1.0.zip
Is this change worth making? While you would have to manually download and install the jars, that way you don't have to configure another Eclipse classpath variable. Is there anything I should be aware of in the next version of Maven that would conflict with this approach?
Eric
--------------------------------------------------------------------- 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]
