GitHub user matthiasblaesing added a comment to the discussion: annotationProcessorPaths editor dosen't recognized imported class
> Strange, why then it works in IntelliJ, Eclipse, VSCode Because they have a different approach. If all IDEs would be the same, they would not exist. All approaches have drawbacks and advantages. It might be possible to enhance the compilation process to consider generated code from a previous maven run (from a quick glance the compilation results in three files in `target/classes/templates` two look like the missing code. There interesting question is: How will that interact with code generated by javac at compilation time. For the "it just works everywhere else": Just downloaded Eclipse 2025-03 (Enterprise Java and Web Developers Variant), unzipped the sample again. Imported the maven project and I'm greeted with red error indicators under the import declaration and the `HelloWorld.render` call in `ManifoldTemplate.java`. Running a maven build (goal: `package`) does not change that, neither does calling "Refresh" on the project tree or running "Project -> Update Maven Project" from the menu. There might be a bit more to this.  GitHub link: https://github.com/apache/netbeans/discussions/8549#discussioncomment-13328315 ---- This is an automatically sent email for notifications@netbeans.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@netbeans.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
