This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 248240 - Netbeans sometimes doesn't recognize generated classes
Summary: Netbeans sometimes doesn't recognize generated classes
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.0.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-29 10:41 UTC by Paddius
Modified: 2015-06-15 13:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paddius 2014-10-29 10:41:40 UTC
I am developing a Netbeans Platform application. This application is splitted into Maven modules. In one of the modules I am generating JAXB classes from a XSD schema (using jaxb2-maven-plugin from org.codehaus.mojo, version 1.6). The classes are always generated and shown fine inside the project view. But sometimes, Netbeans seems to not recognize them anymore. In classes using these generated classes I get errors saying that the imported and used classes are not there. I still can build the application without any errors and the classes are still shown in the project view and I can open them.

My setup:

- Netbeans IDE 8.0.1 with all updates
- Java 1.8.0_20
- Maven 3.0.4
- Git

If I can provide anymore information regarding this issue, please let me know. Unfortunately I am working on a closed source project, so I cannot provide a sample project.
Comment 1 Paddius 2014-11-12 11:33:29 UTC
Seems to always happen, whenever I use "Clean and Build" on my main module. This can be resolved by invoking "Source/Scan for external changes". Is it possible, that this step isn't invoked automatically after the "Clean and Build"?
Comment 2 Tomas Stupka 2015-06-15 13:00:15 UTC
works for me with a current dev build. 
feel free to reopen in case you are able to reproduce with an actual build. In such a case, please also:
- attach your messages.log file from a NB session in which the mentioned problem happened
- it would be great, if you could provide a simple project in which it would be possible to reproduce

thanks