I haven’t used Eclipse in about 2 years so I went ahead and downloaded a fresh copy. I set my M2_REPO variable and then went to import the project as the guide suggests and after Eclipse was done scanning my src root directory it reported that it had no projects to import.
I then decided to try to import the m2eclipse plugin since Geoserver uses maven. After I downloaded the plugin and imported the project using Import → General → Existing Projects into workspace, Eclipse still found no projects under my root directory.
I then tried going to Import → Maven → Existing Maven Projects and this seemed to have gotten the ball rolling, it found all the projects and is currently seems to be looking through the entire structure, fetching dependencies…
I’ve already built the entire tag and thus have already downloaded all directories in my local M2 repo.
Is eclipse not using my system maven and this is why the original import wasn’t working? Are there possibly some steps missing from the quickstart guide that I need to complete in order to force Eclipse to use my already downloaded system maven instead of the plugin?
I haven't used Eclipse in about 2 years so I went ahead and downloaded a fresh copy. I set my M2_REPO variable and then went to import the project as the guide suggests and after Eclipse was done scanning my src root directory it reported that it had no projects to import.
Odd. Did you run mvn eclipse:eclipse before trying to import?
I then decided to try to import the m2eclipse plugin since Geoserver uses maven. After I downloaded the plugin and imported the project using Import -> General -> Existing Projects into workspace, Eclipse still found no projects under my root directory.
I then tried going to Import -> Maven -> Existing Maven Projects and this seemed to have gotten the ball rolling, it found all the projects and is currently seems to be looking through the entire structure, fetching dependencies..
I've already built the entire tag and thus have already downloaded all directories in my local M2 repo.
Is eclipse not using my system maven and this is why the original import wasn't working? Are there possibly some steps missing from the quickstart guide that I need to complete in order to force Eclipse to use my already downloaded system maven instead of the plugin?
The only time I tried to use that plugin the overhead was so high
that I just run away.
I don't know of anyone else in the dev team using it either.
So we might have a lack of suggestions on that one. Or maybe not,
let's see if someone responds that uses m2Eclipse in day to day
development.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I haven't used Eclipse in about 2 years so I went ahead and downloaded a
fresh copy. I set my M2_REPO variable and then went to import the
project as the guide suggests and after Eclipse was done scanning my src
root directory it reported that it had no projects to import.
Odd. Did you run mvn eclipse:eclipse before trying to import?
I then decided to try to import the m2eclipse plugin since Geoserver
uses maven. After I downloaded the plugin and imported the project
using Import -> General -> Existing Projects into workspace, Eclipse
still found no projects under my root directory.
I then tried going to Import -> Maven -> Existing Maven Projects and
this seemed to have gotten the ball rolling, it found all the projects
and is currently seems to be looking through the entire structure,
fetching dependencies..
I've already built the entire tag and thus have already downloaded all
directories in my local M2 repo.
Is eclipse not using my system maven and this is why the original import
wasn't working? Are there possibly some steps missing from the
quickstart guide that I need to complete in order to force Eclipse to
use my already downloaded system maven instead of the plugin?
The only time I tried to use that plugin the overhead was so high
that I just run away.
I don't know of anyone else in the dev team using it either.
So we might have a lack of suggestions on that one. Or maybe not,
let's see if someone responds that uses m2Eclipse in day to day
development.
m2eclipse uses maven 3.?-SNAPSHOT
It uses your maven2 config (Linux/BSD/etc: ~/.m2/settings.xml) but can't build geoserver on its own, because the poms contain errors and use Mojos not compatible to maven 3.
You can configure m2eclipse to use maven 2 though dependencies will still be resolved via maven 3. You just have to ignore all the errors (which are mostly caused by declaring version properties multiple times and/or importing the same dependency twice.
Cheers,
Lennart
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
------------------------------------------------------------------------------
This SF.net email is sponsored by
As Andrea indicated; you missed the step of running mvn eclipse:eclipse on the command line (so that your import actually has some .project and .classfile entries to recognise).
I have also tried using the m2eclipse plugin - with mixed results. I tried the geotools build on a release of Maven 3 a couple of months ago and there were issues. I was going to ignore both Maven 3 and m2eclipse until the devel lists were interested.
Jody
On 14/08/2010, at 10:34 AM, Alessandro Ferrucci wrote:
I haven’t used Eclipse in about 2 years so I went ahead and downloaded a fresh copy. I set my M2_REPO variable and then went to import the project as the guide suggests and after Eclipse was done scanning my src root directory it reported that it had no projects to import.
I then decided to try to import the m2eclipse plugin since Geoserver uses maven. After I downloaded the plugin and imported the project using Import → General → Existing Projects into workspace, Eclipse still found no projects under my root directory.
I then tried going to Import → Maven → Existing Maven Projects and this seemed to have gotten the ball rolling, it found all the projects and is currently seems to be looking through the entire structure, fetching dependencies…
I’ve already built the entire tag and thus have already downloaded all directories in my local M2 repo.
Is eclipse not using my system maven and this is why the original import wasn’t working? Are there possibly some steps missing from the quickstart guide that I need to complete in order to force Eclipse to use my already downloaded system maven instead of the plugin?
As Andrea indicated; you missed the step of running mvn eclipse:eclipse on the command line (so that your import actually has some .project and .classfile entries to recognise).
I have also tried using the m2eclipse plugin - with mixed results. I tried the geotools build on a release of Maven 3 a couple of months ago and there were issues. I was going to ignore both Maven 3 and m2eclipse until the devel lists were interested.
Jody
On 14/08/2010, at 10:34 AM, Alessandro Ferrucci wrote:
I haven’t used Eclipse in about 2 years so I went ahead and downloaded a fresh copy. I set my M2_REPO variable and then went to import the project as the guide suggests and after Eclipse was done scanning my src root directory it reported that it had no projects to import.
I then decided to try to import the m2eclipse plugin since Geoserver uses maven. After I downloaded the plugin and imported the project using Import → General → Existing Projects into workspace, Eclipse still found no projects under my root directory.
I then tried going to Import → Maven → Existing Maven Projects and this seemed to have gotten the ball rolling, it found all the projects and is currently seems to be looking through the entire structure, fetching dependencies…
I’ve already built the entire tag and thus have already downloaded all directories in my local M2 repo.
Is eclipse not using my system maven and this is why the original import wasn’t working? Are there possibly some steps missing from the quickstart guide that I need to complete in order to force Eclipse to use my already downloaded system maven instead of the plugin?