Thanks for your opinion, it seems to me that I am gonna to abondon the use of system scope then.
However, I still think there should be a way how to define dependencies that are specific to a certain project only and you do not want to store them in a repository. This is maybe because of my bad underastanding of what a repository is intended to be for: I understand it as a store where I can place my SHARED /=common/ libraries so that I have a central management point over them. For project specific libs, I do not want to have them in a repo as they are pretty unlikely to be used in any other project and I don't see a point to have a lib in repo just because of one specific project. Another reason for this might be some kind of encapsulation when I want to have all my project-related stuff on one place only (so that I can back it up easily, for instance. If local repository was involved, I would have at least 2 things to backup: repo and project itself.) But as I said, this is probably just my bad understanding of things and ALL depenendies in Maven /both common and special/ shall be stored in repo. Any discussion on this is welcome :) -- View this message in context: http://www.nabble.com/System-scope-and-transitive-dependencies-t1326219.html#a3550912 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
