So, a little late addendum to this discussion...
While posting a video on YouTube yesterday I noticed a video I created last
year (and had totally forgotten about) that illustrates this exact issue:
https://www.youtube.com/watch?v=c2-YxVDYu_8
In short, the reason I'm not having problems with li
I don't think I've ever had to attach sources of maven projects manually in
Eclipse (although I recall hitting something like this in a far past). And
given the second problem, it kind of sounds like the link between the app
project and the libraries/frameworks is completely broken.
Paul's sugg
Hi Samuel,
On 11 Apr 2024, at 03:45, Samuel Pelletier via Webobjects-dev
wrote:
> I created a new workspace with the latest Eclipse to migrate my project to
> maven. My projects run and I can debug the application code (set breakpoint,
> click on exception stack trace to open project source)
Hi Samuel,
On 11 Apr 2024, at 3:45 am, Samuel Pelletier via Webobjects-dev
wrote:
> I created a new workspace with the latest Eclipse to migrate my project to
> maven. My projects run and I can debug the application code (set breakpoint,
> click on exception stack trace to open project source
Hi,
I created a new workspace with the latest Eclipse to migrate my project to
maven. My projects run and I can debug the application code (set breakpoint,
click on exception stack trace to open project source) but all debug functions
are not working for frameworks. I set breakpoint in code but
