[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5524) Debugger does not "see" source by default
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Fri Dec 18 17:35:30 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Snjezana Peco resolved JBIDE-5524.
----------------------------------
Resolution: Done
The fix for JBIDE-2215 was to use the "org.eclipse.jst.server.tomcat.core.sourcePathComputer" source path computer. It adds only WAR and EAR projects to the source lookup path.
Since https://bugs.eclipse.org/bugs/show_bug.cgi?id=233110 has been fixed in the meantime, I have replaced the "org.eclipse.jst.server.tomcat.core.sourcePathComputer" spc with the "org.eclipse.jst.server.generic.core.sourcePathComputer" spc.
> Debugger does not "see" source by default
> -----------------------------------------
>
> Key: JBIDE-5524
> URL: https://jira.jboss.org/jira/browse/JBIDE-5524
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 3.1.0.CR1
> Environment: Windows Vista 64-bit, Java 1.6, SOA Platform 5 Beta 1
> Reporter: Burr Sutter
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 3.1.0.GA
>
> Attachments: Debugger_Source_not_found.jpg, Edit_Source_Lookup_Path.jpg, MyEsbAction_source.jpg
>
>
> Add a break point to an ESB action does bring up the debugger perspective but the source is not found. Since I am editing the source in JBDS, I would think it can actually find the source.
> File - New - Project - ESB Project was how the project was constructed.
> The "test case" is defined here:
> http://community.jboss.org/wiki/SOA-P43WorkshopLabExamples
> Screenshots will be uploaded
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list