blocks|key|3097818|text|虽然这个bug在所有bug+@Sonatype中获得的票数最多，但它还没有得到修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097819|然而，我已经在Eclipse+Bugzilla上填写了一个增强请求，如果你同意这个问题“找不到源码”应该被修复，请投票支持它here。|offset|length|3097820|您可以找到三种变通方法here。|3097821|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.eclipse.org/bugs/show_bug.cgi?id=384065|1|https://stackoverflow.com/a/11452410/695116^0|0|1Q|4|0|0|B|4|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Although this bug had the most votes of all bugs @Sonatype, it hasn't been fixed.

However I have filled an enhancement request on Eclipse Bugzilla and if you agree this issue "Source not found" should be fixed, please vote for it <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=384065" rel="nofollow noreferrer">here</a>.

You can found three workarounds <a href="https://stackoverflow.com/a/11452410/695116">here</a>.

blocks|key|3097916|text|我找到了这个com.ifedorenko.m2e.sourcelookup插件。链接是在"“中提供的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3097917|转到Help+>+Install+New+Software+..并使用|style|CODE|3097918|3097919|+http://ifedorenko.github.com/m2e-extras/|blockquote|3097920|3097921|3097922|来搜索链接。安装这个插件后，我终于能够调试依赖项的源代码了。|3097923|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ifedorenko/com.ifedorenko.m2e.sourcelookup^0|6|V|0|0|2|U|0|0|1|14|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@$A|12|B|13|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|I|3|J|5|K|7|15|8|@$A|16|B|17|F|G]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|18|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

I found this <a href="https://github.com/ifedorenko/com.ifedorenko.m2e.sourcelookup" rel="nofollow noreferrer">com.ifedorenko.m2e.sourcelookup</a> plugin. The link was provided in "<a href="https://stackoverflow.com/questions/9474981/java-debugging-source-not-found">Java Debugging: Source not found</a>".

Go to <code>Help &gt; Install New Software ..</code> and use 

<blockquote>
 <code>http://ifedorenko.github.com/m2e-extras/</code>
</blockquote>

to search for the links. After installing this plugin I was finally able to debug the source code of dependencies.

blocks|key|225166|text|使用外部Maven而不是嵌入在调试配置对话框中的default。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|225167|请参见下面的示例屏幕截图(菜单运行->调试配置...)：|225168|Configure+external+Maven|225169|测试环境：|225170|面向Java开发人员的企业版Eclipse+IDE+:+Oxygen.1a版本(4.7.1a)，64位(来自spring.io)|225171|Oracle+JDK+jdk1.8.0_144，64位|unordered-list-item|225172|Maven:3.5.2|225173|操作系统:+Windows+10企业版N，64位|225174|测试目标hpi:run+(示例詹金斯插件)<代码>H214<代码>F215|CODE|225175|225176|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/D7nHg.png^0|F|4|0|0|0|O|0|0|0|0|0|0|0|4|7|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|J|3|K|5|6|7|1E|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1F|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|R|5|P|7|1H|8|@]|D|@]|E|$]]|$1|S|3|T|5|P|7|1I|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|1J|8|@$9|1K|A|1L|B|W]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

Use External Maven instead of default Embedded in Debug Configurations dialogue.

Please see example screenshot below (menu Run -> Debug Configurations...):

<a href="https://i.stack.imgur.com/D7nHg.png" rel="nofollow noreferrer">Configure external Maven</a>

Tested environment:

<ul>
<li>Eclipse IDE for Java Developers: Oxygen.1a Release (4.7.1a), 64-bit (from spring.io)</li>
<li>Oracle JDK jdk1.8.0_144, 64-bit</li>
<li>Maven: 3.5.2</li>
<li>OS: Windows 10 Enterprise N, 64-bit</li>
<li>Test goal <code>hpi:run</code> (sample Jenkins plugin)</li>
</ul>

blocks|key|230332|text|在我的例子中，问题与"Debug+Configuration“附带的源代码有关，可能是迁移到Maven的一些残留物。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|230333|我通过“调试配置...”解决了这个问题。页面并选择配置，然后在"Sources“选项卡上恢复默认设置，这将添加项目的所有Maven依赖项。|230334|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case the problem was related with the source code attached with the "Debug Configuration", maybe some remnants form a migration to Maven.

I solved it by going to the "Debug Configurations..." page and selecting the configuration in case, then at the "Sources" tab I restored the defaults, which added all the project's Maven dependencies.

blocks|key|2883971|text|窗口->首选项->JBoss工具->源代码查找|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2883972|确保您选中了"Automatically+add+the+JBoss+Maven+source+container+to+all+JBoss+As+launch+configurations“。在“自动配置Java源附件”下，选择“始终”。|2883973|这可以帮助我走出这个问题。|2883974|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Window->Preferences->JBoss Tools->Source Lookup

make sure you have check "Automatically add the JBoss Maven source container to all JBoss As launch configurations".
and under "Automatically configure the Java Source Attachment",
choose "Always".

this helps myself out of the problem.

blocks|key|225123|text|我想我已经通过更新我的Eclipse+m2e修复了这个问题。我想我的版本是1.2，然后在写1.6.2的时候更新到了最新版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|225124|Eclipse+Bug+comments帮我解决了这个问题。|225125|现在我可以调试我的gquery-dnd-bundle-1.0.6了！|225126|entityMap|0|LINK|mutability|MUTABLE|url|https://www.eclipse.org/m2e/index.html|1|https://bugs.eclipse.org/bugs/show_bug.cgi?id=384065#c25^0|B|B|0|0|0|K|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I think I fixed this for myself by updating my <a href="https://www.eclipse.org/m2e/index.html" rel="nofollow">Eclipse m2e</a>.
I think I had version ~1.2, and then updated to latest [as of writing] 1.6.2.

The <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=384065#c25" rel="nofollow">Eclipse Bug comments</a> helped me figure this out.

Now I can debug into my gquery-dnd-bundle-1.0.6!

blocks|key|230373|text|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-source-plugin</artifactId>
++++++++++++<version>${version.maven-source-plugin}</version>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>attach-sources</id>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>jar-no-fork</goal>
++++++++++++++++++++++++<goal>test-jar-no-fork</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|230374|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-source-plugin&lt;/artifactId&gt;
 &lt;version&gt;${version.maven-source-plugin}&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;attach-sources&lt;/id&gt;
 &lt;goals&gt;
 &lt;goal&gt;jar-no-fork&lt;/goal&gt;
 &lt;goal&gt;test-jar-no-fork&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|228684|text|“目标”maven项目应该在“客户端”项目可以访问源代码之前发出它的源代码。我通过在“目标”项目中使用maven-source-pluging解决了这个问题：https://maven.apache.org/plugins/maven-source-plugin/index.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|228685|只需在目标项目的pom.xml文件中使用以下代码片段，进行发布，并在客户端项目的pom.xml文件中使用发布版本。然后eclipse可以自动让你无缝地“跳转”到目标项目：|228686|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-source-plugin</artifactId>
++++++++++++<version>${version.maven-source-plugin}</version>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>attach-sources</id>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>jar-no-fork</goal>
++++++++++++++++++++++++<goal>test-jar-no-fork</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>|code-block|syntax|javascript|228687|entityMap|0|LINK|mutability|MUTABLE|url|https://maven.apache.org/plugins/maven-source-plugin/index.html^0|27|1R|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

The "target" maven project should emit it's source code before the "client" projects can have access to the source code. I solved the issue by using the maven-source-pluging in the "target" project: <a href="https://maven.apache.org/plugins/maven-source-plugin/index.html" rel="nofollow noreferrer">https://maven.apache.org/plugins/maven-source-plugin/index.html</a>

Just use the following snippet in the pom.xml file of the target project, make a release, and use the release version into the pom.xml file of the client project. Then eclipse can automatically let you "jump" to the target project seamlesly:

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-source-plugin&lt;/artifactId&gt;
 &lt;version&gt;${version.maven-source-plugin}&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;attach-sources&lt;/id&gt;
 &lt;goals&gt;
 &lt;goal&gt;jar-no-fork&lt;/goal&gt;
 &lt;goal&gt;test-jar-no-fork&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

I've downloaded the source for all the Maven JARs in my buildpath using Maven->Download Sources and <code>mvn eclipse:eclipse -DdownloadSources=true</code>, which worked! When I open up the build path I can see that the sources JARs are attached for every JAR file. 

But when I run the damn thing on Tomcat 6 I keep getting "Source not found" page with "Edit Source lookup path" button. But the source is already attached in the build path. What isn't this working? 

When I manually point it to the JAR file by clicking on the "Edit Source lookup path" button it works. And when I manually point it to the folder it does not work. Why isn't Eclipse or Tomcat picking up the attached source in the build path? 

Note: I'm using apache-maven-3.0.4, apache-tomcat-6.0.16 and Eclipse Indigo Service Release 2.

Eclipse not picking up Maven attached source on debug

Windows

Eclipse

Java

我已经使用Maven->Download Sources and mvn eclipse:eclipse -DdownloadSources=true下载了构建路径中所有Maven JAR的源代码，它起作用了！当我打开构建路径时，我可以看到每个JAR文件都附加了源代码JAR。但是当我在Tomcat6上运行这个该死的东西时，我总是得到"Source not found“页面和"Edit Source

问Eclipse在调试时不拾取附加Maven的源代码
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse在调试时不拾取附加Maven的源代码EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Eclipse在调试时不拾取附加Maven的源代码
EN