根据在Eclipse (Kepler)中查看Maven控制台，如果您试图在编辑器中从上述Maven依赖项打开一个类，而您还没有下载Maven依赖项的源代码，则将自动下载Maven依赖项的源代码。当您不想为所有依赖项获取源代码，但又不知道需要哪些依赖项时(而且您正在使用Eclipse)，这是非常方便的。

我最终使用了@GabrielRamierez的方法，但接下来将使用@PascalThivent的方法。

你可以，如果他们被上传。通常它们被称为“frameworkname-version-source(s)”

为了调试，你也可以使用“Java反编译器”，如:JAD，并在运行中反编译源代码(尽管生成的源代码永远不会与原始源代码相同)。然后将JAD作为插件安装到Eclipse或您喜欢的IDE中。

要下载某些特定的源代码或javadoc，我们需要包括GroupIds -它是一个逗号分隔的值，如下所示

mvn dependency:sources -DincludeGroupIds=com.jcraft,org.testng -Dclassifier=sources

注意，分类器不是用逗号分隔的，要下载javadoc，我们需要使用分类器javadoc再次运行上述命令

mvn dependency:sources -DincludeGroupIds=com.jcraft,org.testng -Dclassifier=javadoc

Maven Micro-Tip: Get sources and Javadocs When you're using Maven in an IDE you often find the need for your IDE to resolve source code and Javadocs for your library dependencies. There's an easy way to accomplish that goal. mvn dependency:sources mvn dependency:resolve -Dclassifier=javadoc The first command will attempt to download source code for each of the dependencies in your pom file. The second command will attempt to download the Javadocs. Maven is at the mercy of the library packagers here. So some of them won't have source code packaged and many of them won't have Javadocs. In case you have a lot of dependencies it might also be a good idea to use inclusions/exclusions to get specific artifacts, the following command will for example only download the sources for the dependency with a specific artifactId: mvn dependency:sources -DincludeArtifactIds=guava

来源:http://tedwise.com/2010/01/27/maven-micro-tip-get-sources-and-javadocs/

文档:https://maven.apache.org/plugins/maven-dependency-plugin/sources-mojo.html

如果您想手动找到任何工件的源jar文件，请转到特定工件的maven存储库位置，并在Files中单击“view All”。你可以找到源jar文件。