Including Dependencies in Your Gradle Build Script's Classpath
In a recent project, I wanted to use SnakeYAML in my Gradle build script. This is pretty easy to do; all you have to do is add the following to your script:
In a recent project, I wanted to use SnakeYAML in my Gradle build script. This is pretty easy to do; all you have to do is add the following to your script:
Adding a JAR as a dependency is simple in Gradle. In your dependencies {}, add the following line:
I created a tool today called up. Although it’s really simple, it gets the job done and it’s really useful.
I recently purchased a VPS to run my IRC client in. I wanted to start my IRC client in tmux on startup. The answer is simple: crontabs.
I don’t like the traditional JAR name assigned in Gradle. In Bukkit development, you usually make the JAR name the same as the plugin name. Here’s how you set the name of the JAR:
My friend wanted me to test out his program, but it didn’t have a main class specified in the manifest. Here’s the solution:
I often SSH to remote servers, and those servers usually have tmux installed. (tmux is better than Screen in every way) However, conflicts arise when you want to manipulate a remote tmux session within a local one. Ctrl-B refers to the local tmux session, not the remote one, and you have to press Ctrl-B twice to manipulate the remote one. This is pretty annoying. Fortunately, there is a solution to this.
I use XFCE as my primary desktop environment. It’s a fast, lightweight operating system that when combined with Synapse provides a great, lag-free computing experience.
After hearing good things about Powerline for a while, today I finally decided to install Powerline on tmux. However, it didn’t work when I followed the directions. Apparently, this is a common error.
Recently, I tried to install the agnoster theme with zsh. However, a bunch of symbols appeared instead of the powerline font. I installed one of the provided patched powerline fonts to fix it, but it still didn’t work.