You have 3 possibilities. In all three cases you can keep the hello-job.xml file in src/main/resources folder. I'll start with the easier variant:
1. With the condition that you're using Maven for dependency management, just add a configuration for the maven-assembly-plugin in which you specify the main class + to include you dependencies in the final executable jar. When you run mvn clean package it will build an executable jar on which you can run java -jar myjar-jar-with-dependencies.jar, no matter where you put that jar.
The following is the configuration for the plugin which you need to add to you pom.xml file:
<build>
<plugins>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
<archive>
<manifest>
<mainClass>com.mypackage.RunApp</mainClass>
</manifest>
</archive>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
2 You have to create a MANIFEST.MF file in your src/main/resources/META-INF directory, in which you specify the main class by adding the line Main-Class: com.mypackage.RunApp (note that you have to insert a newline after each line you write).
After you build your package, you have to put that executable jar in a directory where ALL your dependencies are as well.
3 This is similar to the second variant (you also have to put your packaged jar in the same directory as your dependencies), the difference being that you tell Maven to build your MANIFEST.MF file. This is also done by configuring a plugin:
<build>
<plugins>
<plugin>
<!-- Build an executable JAR -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifest>
<addClasspath>true</addClasspath>
<classpathPrefix>lib/</classpathPrefix>
<mainClass>com.mypackage.RunApp</mainClass>
</manifest>
</archive>
</configuration>
</plugin>
</plugins>
</build>