So does that mean I shouldn't configure the build path within Eclipse? Will the dependency entries still populate the .classpath file?
And is it only the compile scope of dependency that does this, or any of the others too? Thanks. Eugene Kuleshov wrote: > > > There is not just one way to use Maven in Eclipse. m2eclipse plug-in > is trying to provide convenient option to use dependency configuration > from the pom.xml. So, build path is always in sync between command line > and the IDE. > > Hopefully this answers your questions. > > regards, > Eugene > > > lightbulb432 wrote: >> Does using Maven in Eclipse mean that it's unnecessary to ever put >> entries >> into the build path manually again? How could you specify dependencies so >> that it is not necessary to put things in the Eclipse build path? >> >> How, if at all, does this Eclipse plugin do it for you? What are the >> options >> for specifying dependency scopes as to make this happen? >> > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > > -- View this message in context: http://www.nabble.com/Eclipse-build-path-tf3050954.html#a8482063 Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
