On 4 Oct 2012, at 19:22, Davis Ford wrote:
> This doesn't make a whole lot of sense to me. Any idea what the problem is
> here?
You've given the jersey-server dependency a scope of "runtime" which means it
is on the runtime and test classpaths, but _not_ the compile classpath,
therefore the cl
Just to give you a hint:
Find out the difference between provided and
runtime
And know that Eclipse can't distinguish scopes, test-scoped dependencies
like junit ends on the one and only classpath of eclipse.
Robert
Op Thu, 04 Oct 2012 20:24:36 +0200 schreef Davis Ford
:
Appending th
Your dependency is set to runtime scope, so it's not use at compile time.
Eclipse is way more limited than Maven: it only has a single build path for
the project. M2Eclipse should configure the build path equivalent to
Maven's test scope but I can't tell for eclipse:eclipse, seems clearly
broken to
Appending this as well:
$ mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
Maven home: /home/ubuntu/apache-maven-3.0.4
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: /usr/lib/jvm/jdk1.7.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", versi
