Re: [m2e-users] Import Existing Support with Parent pom.xml in Project R

[Asaf Mesika <asaf.mesika@xxxxxxxxx>]

Well, from my many years working from Eclipse, I can tell you that workspace directory is always separate from your project dirs.
Workspace dir saves your preferences for Eclipse. Sometime Eclipse freaks out and the only solution is to start from a fresh workspace, thus you need to delete it. If you needed to move your projects each time, it will annoy you.

In our company, we work as follows:

~/eclipse
~/work/acme/foo-1.2-build/foo-parent
                                                         pom.xml 
                                                         foo-core/
~/work/acme/workspace


We keep one workspace and work with different work set, one for each version of foo (or any different project-version combination)



On 29/12/2010, at 23:53, Alejandro Calbazana wrote:

> My project structure is as follows:
> 
> pom.xml (parent)
> core\
>  pom.xml
> wscli\
>  pom.xml
> webapp\
>  pom.xml
> 
> Now...  I do not have a top level project that contains the parent
> pom.xml.  I am not sure that this makes a difference.  The error
> message that I get is - "Can not import project {0} from existing
> workspace."  I was able to get this working by putting my workspace in
> a different directory than my project (typically, I have one workspace
> per group of projects and they all live along side each other).  I
> saw, from checking some of the eclipse plugin development docs, that
> this isnt recommended with maven projects within eclipse.  I didn't
> see any such restriction on the m2eclipse  site though.
> 
> Thanks,
> 
> Alejandro
> 
> On Wed, Dec 29, 2010 at 4:27 PM, Asaf Mesika <asaf.mesika@xxxxxxxxx> wrote:
>> Well, I'm using a parent project with multi-modules without any issue (Eclipse 3.5, 3.6), and M2Eclipse 0.12.
>> Also, Using git.
>> 
>> The project is as follows:
>> 
>> foo-parent\
>>      pom.xml
>>      foo-core\
>>            pom.xml
>>      foo-commons\
>>            pom.xml
>>      foo-webapp\
>>            pom.xml
>> 
>> Each foo-X directory is a git repository. We're currently composing this by hand (manually checking it out), but we plan to do this a custom made Maven plugin like the guys in Atlassian wrote.
>> 
>> When I import, I choose "foo-parent" directory and it automatically shows all 4 projects.
>> 
>> Can you describe you problem in more detail?
>> 
>> 
>> On 29/12/2010, at 21:03, Alejandro Calbazana wrote:
>> 
>>> Hi,
>>> 
>>> I'd like to get some clarity around importing existing maven projects
>>> into eclipse.  I am not able to successfully import projects that have
>>> a parent pom.xml at the project root dir.  I am able to import the
>>> modules successfully, but the parent pom.xml gets left behind.  This
>>> is unfortunate as I am not sure if the projects are referencing the
>>> parent pom.  While importing from a SCM, I notice that a parent
>>> project is created behind the scenes for projects that have a pom.xml
>>> at the root.  What are my options for getting my parent pom.xml to
>>> import using the import existing functionality?
>>> 
>>> The motivtion for this is to use git.  I do not see any git support
>>> for m2eclipse, so I am not sure where to go from here.  Additionally,
>>> I would like to not have to modify my project structure.
>>> 
>>> Thanks,
>>> 
>>> Alejandro
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>> 
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>> 
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users