Why does it have to be a separate JAR if only project1 depends on it? Quintin Beukes
On Sun, Oct 18, 2009 at 2:37 PM, _MS_ <matija.slivo...@gisdata.com> wrote: > > My project structure is: > > project1 with dependencies :lib-project.jar, config.jar > lib-project - this is separate project > > All dependencies are resolved through local repository. > > Project1 has subdirectory mibs that I would like to package into jar in > order to load more easily all the MIB files by using getResource java native > call. > > I recently tried following: > - created config.jar by using separate assembly descriptor( config has same > groupId, artifactId and version as project1 as it's part of project1, only > different classifier, config) > - Config jar is set as RUNTIME dependency for project1 > - installed it into local repository with install:install-file > > But after all that I get cyclic reference between project1 and config. I > was convinced that this would NOT happen because I used runtime scope and > config as classifier:confused: > > > What am I doing wrong > :-((:-(( > > PS using new project just for configuration doesn't work for me. > > Any suggestions are more then welcome. Thnx. > > -- > View this message in context: > http://www.nabble.com/Config.jar-project-dependency-tp25939781p25946335.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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
