A classpath is a list of locations to load classes from. These ‘locations’ can either be directories, or jar files. For directories, the JVM will follow an expected pattern for loading a class. If I have the directory C:/myproject/classes in my classpath, and I attempt to load a class com.mycompany.Foo, it will look under the … Read more
I prefer the first version to start a java application just because it has less pitfalls (“welcome to classpath hell”). The second one requires an executable jar file and the classpath for that application has to be defined inside the jar’s manifest (all other classpath declaration will be silently ignored…). So with the second version … Read more
If your spring-context.xml and my.config files are in different jars then you will need to use classpath*:my.config? More info here Also, make sure you are using resource.getInputStream() not resource.getFile() when loading from inside a jar file.
SIMPLE DEFINITION The classpath*:conf/appContext.xml simply means that all appContext.xml files under conf folders in all your jars on the classpath will be picked up and joined into one big application context. In contrast, classpath:conf/appContext.xml will load only one such file… the first one found on your classpath.
You can try invalidating the cache and restarting IntelliJ, in many cases it will help. File -> Invalidate Caches/Restart
Here’s an example: package foo; public class Test { public static void main(String[] args) { ClassLoader loader = Test.class.getClassLoader(); System.out.println(loader.getResource(“foo/Test.class”)); } } This printed out: file:/C:/Users/Jon/Test/foo/Test.class
In Intellij 13, it looks it’s slightly different again. Here are the instructions for Intellij 13: click on the Project view or unhide it by clicking on the “1: Project” button on the left border of the window or by pressing Alt + 1 find your project or sub-module and click on it to highlight … Read more
The buildScript block determines which plugins, task classes, and other classes are available for use in the rest of the build script. Without a buildScript block, you can use everything that ships with Gradle out-of-the-box. If you additionally want to use third-party plugins, task classes, or other classes (in the build script!), you have to … Read more
Custom Scanner Implement your own scanner. For example: (limitations of this solution are mentioned in the comments) private List<String> getResourceFiles(String path) throws IOException { List<String> filenames = new ArrayList<>(); try ( InputStream in = getResourceAsStream(path); BufferedReader br = new BufferedReader(new InputStreamReader(in))) { String resource; while ((resource = br.readLine()) != null) { filenames.add(resource); } } return … Read more
The difference from the Java API Specifications is as follows. For ClassNotFoundException: Thrown when an application tries to load in a class through its string name using: The forName method in class Class. The findSystemClass method in class ClassLoader. The loadClass method in class ClassLoader. but no definition for the class with the specified name … Read more