You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Write code to list files in standard maven resources dir
2. Package app with one-jar
3. Try to run the app and list resource files
What is the expected output? What do you see instead?
A list of resource files on the classpath.
What version of onejar-maven-plugin are you using?
1.4.4
What is the output of "mvn -version" on your machine?
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
07:22:22-0800)
Maven home: /usr/local/maven
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.51.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-431.5.1.el6.x86_64", arch: "amd64", family:
"unix"
Please provide any additional information below.
Please see this stack overflow. This is not so much an issue or error with
onejar, but a question about how to perform a routine task in the context of
using the onejar maven plugin.
http://stackoverflow.com/questions/23094931/unable-to-get-file-list-from-standar
d-resource-dir-in-maven-project-with-spring/23132283?noredirect=1#23132283
Original issue reported on code.google.com by da...@tongal.com on 17 Apr 2014 at 4:53
The text was updated successfully, but these errors were encountered:
Also I have read this documentaton
http://one-jar.sourceforge.net/index.php?page=details&file=resources but it
does not contain sufficient information, for me at least, to understand how to
list the resources in the classpath of my nested jar. Also what would be
preferable is to have a mechanism to do so which does not explicitly depend on
OneJar in code. Is this possible?
Original comment by da...@tongal.com on 17 Apr 2014 at 5:19
Original issue reported on code.google.com by
da...@tongal.com
on 17 Apr 2014 at 4:53The text was updated successfully, but these errors were encountered: