So "runtime" seems very similar to the "compile" scope type. Could somebody please explain the difference?
The Maven documentation seems to imply something about transitive dependencies, but I don't understand what it's trying to say. Thanks. Larry Meadors-2 wrote: > > I'd assume that it's there so that you can run your app from the IDE - > that's the behavior I'd expect. > > Larry > > > On 5/16/07, lightbulb432 <[EMAIL PROTECTED]> wrote: >> >> Why are dependencies with a scope of "runtime" added to Eclipse's >> .classpath >> file? I thought the point of runtime is that it's not a compile-time >> dependency; therefore, why the addition to the .classpath? >> >> Perhaps someone can correct me, but my understanding of runtime scope is >> that it is not included in the compile-time classpath, but is added to >> the >> JAR or WAR upon packaging - is this an accurate statement? >> >> Thanks. >> -- >> View this message in context: >> http://www.nabble.com/Runtime-dependencies-in-Eclipse-classpath-tf3769914s177.html#a10658508 >> Sent from the Maven - Users mailing list archive 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] > > > -- View this message in context: http://www.nabble.com/Runtime-dependencies-in-Eclipse-classpath-tf3769914s177.html#a10658694 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
