I was naive enough to think I can inline images... Anyway, In the problematic scenario described, I see the "classes" and "test-classes" output folders added to the source lookup of the Remote Debug conifguration. After unchecking the "Allow output folders for source folders" option, I see all source folders added to the source lookup path.
Might worth saying - I don't have any unconventional source/resources folders in my projects. On Mon, May 18, 2015 at 11:10 AM, Dagan Sandler <[email protected]> wrote: > Hi, > > When I'm remote debugging a project that has another workspace project as > a dependency, I found that the project isn't added correctly to the source > lookup path: > > Resulting in "Source not found" messages, and sometimes worse - sources > of an irrelevant older version jar come up. > > What I found is that if I uncheck "Allow output folders for source > folders" in the "Java Build Path"->"Source" tab under the referenced > project, I get the project added to the source lookup path correctly: > > > Only problem with this so far - is that the option gets reset every time I > do a "Maven Update". > Anyone knows how to make it persist between Maven updates and/or has other > insights or solutions to this issue? > > > > > >
_______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
