Hi Ole, Well, the questions you ask seems quite antithetic to me. I mean, if you want maven to manage sources, then those sources will be present locally, after having been downloaded. Now, the thing is: if what you want is just no to have to do it manually on each developer machine, then yes, it's possible.
The simplest way seems to select the "Download Artifact Sources" checkbox, in Window/Preferences/Maven. This way, if the jars you're using also provide their sources (for artifact-version.jar, it must be named artifact-version-sources.jar). Then m2e (this is not a "core" maven feature) will download and link those sources with the corresponding jars. Outside Eclipse, using the CLI, you can also do mvn dependency:sources in your project root. That will try and download all artifact sources (transitively, sure). Then it will display a summary of which sources could not be found. This is what we sometimes use to find projects that miss sources jars to manually deploy those sources in our corporate maven repo. HTH Cheers. PS : if you have very M2E specific questions, then you might prefer using the M2E users mailing list instead (see http://m2eclipse.codehaus.org/mail-lists.html). 2008/9/17 Ole Laurisch <[EMAIL PROTECTED]> > Hello all, > > I'm using Maven 2 and the m2eclipse Maven integration for Eclipse. > How can I attach a source zip to a jar (let's say jface.jar) without > having to have this source zip locally stored on every developers machine? > Is there a way to let the source zips be managed by Maven too? > > Thanks in advance, > Ole > > -- engram GmbH > Konsul-Smidt-Straße 8r > 28217 Bremen > Germany > Tel.: +49-[0]421-620298-0 > Fax: +49-[0]421-620298-999 > Handelsregister Bremen HRB 20782 > Geschäftsführer: Jens Wünderlich > Aufsichtsratsvorsitzender: Ralf Paslack -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
