Please read this.
http://www.javaworld.com/javaworld/javaqa/2003-08/01-qa-0808-property-p2.html
> I have static method where i need to read a .properties file off of the
> classpath. The same code that works when running under a tapestry
> application in jetty does not work when run as a normal
You can also try checking off "Allow output folders for source folders" in
your build config... To remove all doubt just look at the contents of
whatever folder eclipse is compiling to.
On 6/8/06, Henri Dupre <[EMAIL PROTECTED]> wrote:
Check the "run" configuration of your app... Eventually try
Check the "run" configuration of your app... Eventually try to delete it and
create a new one. The "Run" configuration may not contain the same
classpath.
On 6/8/06, Dan Adams <[EMAIL PROTECTED]> wrote:
Well, that's the thing. The properties file *is* on the build path and
the same code works f
Well, that's the thing. The properties file *is* on the build path and
the same code works fine in the web app. But I never run normal java
apps within eclipse so i'm not sure if we're doin something wrong. I
made sure that the project is on the java app runner classpath as well
as the maven depend
Eclipse can be decieving. You have to be really sure the properties file you
are referencing really ~is~ on the classpath when you run it in eclipse. My
guess is that it is not. This usually isn't an issue if the resources you
are referencing are in the same tree as your java sources.
Not to worr
