Good thinking, shouldn't bee to hard to be written either. I'd like it more
dynamic, though :) On the other hand, I just had a doh! moment. Seems like
new File(".").getAbsolutePath() gives the execution folder in Eclipse (and
not the classpath root where the class is, like getClass().getResource("/")
does), which solves part of the issue. If you make sure all your
configuration files are in root, you will be able to locate them relatively
from that. *sigh*. It seems this is more a "what is a file and what is a
resource" type of question for somebody more versed in spring. Should you
embed applicationContext.xml inside the jar? It would allow you to run
jar-only (no external dependencies), but won't enable dynamically changing
the file and future additions without the repacking... :| Just blabing...
Thanks again James!
--
View this message in context:
http://n2.nabble.com/Getting-Maven-project-resources-Eclipse-tp3568731p3569403.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
