I pretty much boils down to your requirements. Loading from the classpath is IMO the right way to do things. However, if you need to keep the config files in a separate project, or just have them in the same project where you read them, depends on your needs. I would not have a separate config project unless there are any specific requirement forcing meto do so. I'd just put the resource files in lib-project2.
Your module tree looks strange. Where would lib-project2 be in it? /Anders On Sat, Oct 17, 2009 at 18:27, _MS_ <matija.slivo...@gisdata.com> wrote: > > I have project consisting of several modules. > > One of the modules requires configuration and loads it through > Class.getResource native call. > Configuration is packaged in jar archive on classpath. > > What is best practice of doing this in maven2. > > For example. > > project1 > |- > |-config.jar > > lib-project2 > > project1 depends on lib-project2. Lib project loads configuration from > classpath. > > > -- > View this message in context: > http://www.nabble.com/Config.jar-project-dependency-tp25939781p25939781.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 > >
