![]() ![]() A subsequent modification in Eclipse is detected by the incremental compiler and processed, all is fine. If I do a Maven build the Maven compiler will build any changed classes (that would be all of them if a clean is included). I tend to have my Eclipse output directories the same as for Maven and have no issues inside Eclipse (I modify the Maven builder to only run process-resources so it doesn't attempt to compile). ![]() This part doesn't directly answer your question, but you may find useful anyway. You can see what goals are run by Maven by opening the project properties ( alt-enter) and selecting the Maven item. This is a long shot, but it may also be that a Maven clean is configured on your project, if that is the case the contents of target/eclipse-classes would be dropped whenever the clean goal is run, so your tests would be deleted from the file system before the tests are run. Does your classpath look markedly different, if so that may be the issue classpath file is hidden from view, it is located in the root of the project).īased on your description I would expect to see entries something like below (note the default output folder and the override for src/main/java and src/main/resources). classpath file, so that JUnit is confused (by default the. It may be that there is something dodgy in your. ![]() The Eclipse JUnit integration has no special classpath configuration, it will work off the output folders defined in your classpath and should find all classes compiled to those folders. ![]()
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |