Thank you to everyone who replied. My project now compiles in Eclipse.
In case it helps anyone else, here's what did and did not worked for
me.
A. I set my preferences to use the same version of Maven that I use on
the command line. This didn't solve the problem for me (when I
rebuilt, I still ha
Yes. You're using the m2e plugin for eclipse. Have you set up your
preferences such that you're building with the same version of maven you
have on the command-line, or is it using the embedded version of maven?
I've seen this sometimes cause strange behavior in eclipse vs. commandline.
One thing
> How are you doing eclipse dependency management? Q4e, m2e or maven-
> eclipse-plugin?
I'm not sure if this answers your question, but when I look at the
list of installed software in Eclipse, I don't see anything that
matches those names exactly.
I see "Maven Integration for Eclipse", version
On Mar 6, 1:07 am, David Bernard wrote:
> try (not tested)
> * In your pom.xml, force the version of jetty to be an exact version
> like 6.1.14 instead of the current version of jetty something like
> [6.1,) (== latest version available upper 6.1)
Setting version to [6.1.6,7) works fine.
--~--~
All the eclipse maven plugins are actually using embedded maven 2.1
pre-releases. M2e is unique in that you can specify what maven
version to use.
How are you doing eclipse dependency management? Q4e, m2e or maven-
eclipse-plugin?
On Mar 5, 2009, at 4:57 PM, Amy de Buitléir wrote:
>
>
try (not tested)
* In your pom.xml, force the version of jetty to be an exact version
like 6.1.14 instead of the current version of jetty something like
[6.1,) (== latest version available upper 6.1)
* or remove the class RunWebApp if you don't need it, (it's need only
to launch jetty from an IDE
