The system scope is recommended only for the tools.jar. Aside from that, people shouldn't use it in anyway.
Wayne Fay wrote:
I really don't suggest people use scope system. It just seems to cause more problems than its worth (based entirely on the questions posed on this list over the last few months). [I hope they (Maven dev) will deprecate it soon -- it just doesn't fit the desired Maven usage strategy, in my opinion.] Install the jar into your local user repo, or corporate Maven repo, etc and then use another scope that best fits your needs. Wayne On 3/22/06, Richard Sladek <[EMAIL PROTECTED]> wrote:One more question for today: Are system-scope dependencies supposed to be transitively resolved or not? My experience shows they are not. Any help on this? The reason for this is that I have a couple of jars related to a project which I don't want to store into the local rep. I have them just in /lib folder and reference them like: <dependency> <groupId>scheduler</groupId> <artifactId>scheduler</artifactId> <version>1.0</version> <scope>system</scope> <systemPath>${basedir}/lib/scheduler.jar</systemPath> </dependency> However, once I run packaging /WAR/, such a jar is not resolved into the WEB-INF/lib folder.... :( -- View this message in context: http://www.nabble.com/System-scope-and-transitive-dependencies-t1326219.html#a3539651 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
