classpath

How do you add a folder (e.g. a resource folder containing arts) to the classpath of a netbeans project? I managed to do that manually via editing the NB generated jar file of the project (that is its MANIFEST.MF file + copying the resources manually), but there should be a way to tell netbeans as well to mind the resources, no? The folder structure looks like this: /project/art/ /project/dist/lib/ /project/dist/art/ /project/dist/project.jar /project/lib/ /project/src/ I don't want to package the art into the jar because I'd like the art to be easily exchangeable. If I add the art folder to

How can I run an sbt app from the shell, so that I can run my app as a normal command-line program (as if run directly via scala but without having to set up an enormous classpath)? I know I can do: echo hello | sbt 'run-main com.foo.MyMain3 arg1 arg2' > out.txt But this (1) takes forever to start because it starts sbt, (2) causes all stdout and stderr to go to stdout, and (3) causes all output to be decorated with a logger [info] or [error]. I looked at https://github.com/harrah/xsbt/wiki/Launcher but it seems too heavyweight, since it downloads dependencies and sets up a new environment and

I am refering to the question on changing the classpath programmatically. I read and found out that there is some function under System class as getproperties where we can retrieve the properties and then also can set it using setProperties(). The answers however I got was that It Wont work. I have not tried this myself, however, i am taking the call. Just to clarify, then why these setProperty() and getProperty() methods are there if they cannot alter it at run time. Or is this specific to the classpath property only ? I will appreciate if someone can present a scenario where they are really

Can someone please give me a simple build.gradle example of how I can specify compile-time-only classes that are not included in the runtime deployment (war). Gradle seems to have gotten this the wrong way around since 'runtime' inherits from 'compile'. I can't imagine a situation where I would want classes at runtime that I wouldn't want at compile time. However, there are many circumstances where I need classes to generate code at compile time that I do not wish to deploy at runtime! I've ploughed through the bloated gradle documentation but cannot find any clear instructions or examples. I

I'm trying to create a plugin system for my application, and I want to start with something simple. Every plugin should be packed in a .jar file and implement the SimplePlugin interface: package plugintest; public interface SimplePlugin { public String getName(); } Now I've created an implementation of SimplePlugin , packed in a .jar and put it in the plugin/ subdirectory of the main application: package plugintest; public class PluginTest implements SimplePlugin { public String getName() { return "I'm the plugin!"; } } In the main application, I want to get an instance of PluginTest . I've

Can anyone tell me how to add to the classpath on OSX? If you want to make a certain set of JAR files (or .class files) available to every Java application on the machine, then your best bet is to add those files to /Library/Java/Extensions . Or, if you want to do it for every Java application, but only when your Mac OS X account runs them, then use ~/Library/Java/Extensions instead. EDIT: If you want to do this only for a particular application, as Thorbjørn asked, then you will need to tell us more about how the application is packaged. In OSX, you can set the classpath from scratch like