JNDI?
On 18/04/2012 11:39 AM, S Ahmed wrote:
Yeah they are config files, I just wanted a simple way to reference them in
my code, i.e:
ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
InputStream is = classLoader.getResourceAsStream("config.properties");
I think what I should do is reference the file based on an environmental
variable, which I will set both locally and on the production server.
Plus having an EV let's other projects reference things in a more uniform
way.
you agree?
On Wed, Apr 18, 2012 at 1:26 AM, Barrie Treloar<[email protected]> wrote:
On Wed, Apr 18, 2012 at 2:20 PM, Wayne Fay<[email protected]> wrote:
I want to exclude the /resources folder from the release so it doesn't
get
compiled into my .jar
If you can't sort out how to do this, you can always make another
project, depend on the output of this one, then unpack the assembly,
set your excludes there, and repack the assembly minus the files you
don't want.
Also, why are you putting things in src/main/resources if you dont
want them in your jar?
Just put them somewhere else and they wont be included.
If they are needed for testing it should be src/test/resources.
If they are configuration files I put them in src/main/config and then
you can tell the assembly plugin to include them in the zip it builds.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
