Hi Samuel, On 11 Apr 2024, at 03:45, Samuel Pelletier via Webobjects-dev <webobjects-dev@lists.apple.com> 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) but all debug > functions are not working for frameworks. I set breakpoint in code but > Eclipse open class from a jar instead of my source. I hadn't noticed this before, but you're right. You need to tell Eclipse where to find the source. See: https://stackoverflow.com/a/22934568/18493 Eclipse java debugging: source not found stackoverflow.com > Also, I have to restart the app to test for my code change in frameworks even > with an hot swap enable JRE. Seems Eclipse does not figure out the maven > dependencies code is in the current workspace. This I cannot reproduce. Possible explanations: 1. Maven versions have to match precisely, obviously. That is, the version your application POM is asking for must match the version the project open in the workspace is providing. 2. You have to launch the app using "Debug As...". 3. There are certain changes that hot code replacement won't allow, though these are usually flagged by Eclipse when you try. What type of change were you making? -- Paul Hoadley https://logicsquad.net/ https://www.linkedin.com/company/logic-squad/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
