This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | "Breakpoint's source file does not belong into the preferred source root" when I have the project open | ||
---|---|---|---|
Product: | debugger | Reporter: | quidryan <quidryan> |
Component: | Java | Assignee: | Martin Entlicher <mentlicher> |
Status: | NEW --- | ||
Severity: | normal | CC: | bht, lhanson |
Priority: | P3 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
quidryan
2011-03-07 19:12:51 UTC
This also happened to me. When it happened to me I was debugging and I had two classes in my workspace, same name, same package, but different projects. Workaround The breakpoint I was trying to add was in the file listed 2nd in debugging sources. I moved the project containing the file to which I wanted to add the breakpoint to the top of the list and it worked. Meet same problem today in Netbeans 7.1RC1, and followed savan's workaround, and it worked. But I think this should be resolved if possible in future release. Same problem when debugging: Breakpoints were not reachable. in my situation problem occured this way: 1.)i checked out a Project via subversion and created a Netbeans Project with Existing Sources 2.)created a totally new Project in NetBeans - wrong Classpath, when rightclicked on one of the classes where the breakpoints were not reachable, were shown - the Classpath of the last checked out project were shown (not the one of the actual project) 3.)rightclicked the Netbeans Project and in Properties/Libraries removed the wrong entry in the "Compile-time" Libraries 4.)debuger worked as usual Could this perhaps be fixed by adding project sources of a new project at the top of the list of breakpoints gaining top priority? Not knowing what the problem is, I would intuitively try to close and re-open the failing project. Moving multiple source packages all the way up from the bottom as suggested as workaround is hard to do at times. I have the same issue in NB 8.0 (Build 201403101706). I could not put a breakpoint in source of 2nd maven module. The 1st module was referring to an older version of the 2nd one. NB claimed to have that same old version source. I fixed this by updating pom of the 1st module to refer to current version of 2nd module |