jar files in the directory dont actually end up on the classpath. The classpath tells Java where to look in the filesystem for files defining these classes. In 'project properties -> Libraries -> Compile' if I add a folder to the classpath rather than adding every. For example, Samza 1.1 and later stuff the entire classpath into META-INF/MANIFEST.MF in pathing.jar, and therefore consists only of a conf dir and pathing.jar.
Select a source folder in the drop-down list and add or remove classpath elements for the source folder. (1) On systems where the classpath length may exceed command-line or other limits, the system property may include at least one level of indirection via the Class-Path keyword in a jar’s manifest. To set a separate classpath for each source folder, leave the Separate Classpath for Each Source Package Folder checkbox selected. Then add or remove classpath elements with the buttons on the right of the dialog box. Must select some files in the IDE or set javac. jira Created (NETBEANS-5442) Adding folder of Jar files to classpath has no effect. To set a common classpath for all source folders, unselect the Separate Classpath for Each Source Package Folder checkbox. Must select some files in the IDE or set javac.includes Rt Cdiff netbeans/buildSrc/nbproject/build-impl.xml netbeans/buildSrc/nbproject/build-impl.xml Print this page rev 10040 : 8165809: Rework build to enable future jigsaw aware JDK9 build