On 01/11/2012 03:22 PM, Rainer Pruy wrote:
But beware that reading "pom.properties" might expose similar problem
as soon as there is a second jar (or some classes directory) with such
file (name).
This is intrinsic to anything that uses getResource*() family of methods
(at least under the hood)
A dirty hack for avoiding that trouble would be to use a file name that
likely is unique to your application.
Rainer
On 11.01.2012 22:13, Steve Cohen wrote:
Thanks for explaining this mysterious result.
I have found that using the pom.properties that Maven creates is a
more straightforward approach and also can be made to work when the
program is not run from the jar (i.e., from Eclipse).
Thanks.
Hmm. See my reply to your original post.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
