adrianblakey commented on issue #5418: URL: https://github.com/apache/netbeans/issues/5418#issuecomment-1416726011
I have a similar issue. I am building and coding against this: https://gitlab.com/ubos a bit more about it here: https://ubos.net/docs/developers/faq/netbeans/ It builds in an nspawnd container on the host using a gradle build process wrapped by python scripts. My home directory maven repo is exported to the container to which artifacts built in the container, are written. The nspawnd container is on a bridged subnet on my arch-linux host. The container file system is shared r/w with my host. I open the sources and projects in NetBeans on the host. NetBeans does not resolve the imports and shows the cleanly-built code as not being compiled - it is, These issues are not as bad in NB 13. I run the compiled code in the container with the java debug options to expose its debugging port as 8888. To debug the code running in the container I attach to port 8888 from NetBeans. I have tried repeatedly to rm -rf ./.cache/netbeans and restart NB - no improvements. I can set breakpoints and halt the code. I can step into code - however NB does not open the corresponding source code into which the execution steps for code that it seems to know nothing about. Command-O works as you described. NetBeans 16 - installed using the Arch package installer https://wiki.archlinux.org/title/netbeans openjdk 11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
