Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Inconsistent Import behavior M2E vs. M2E-Git connector

I believe this is fixed in the latest 1.2 nightlies.  Give it a try.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=387252 

Mike

On Sat, Sep 1, 2012 at 5:47 PM, Sean Fitts <sean@xxxxxxxxxx> wrote:
I've recently been trying to puzzle out an inconsistency in the behavior of Import when done from "File...Import...Maven...Existing Maven Projects" vs. the "Import Maven Projects..." option provided by the M2E-Egit connector.  The former performs the import as expected without making any modifications to the structure of the project directories.  The latter however was taking some projects and creating new directories and moving both the pom.xml and source code into them.  Turns out the projects in question all had a difference between their artifactId and the directory in which they lived.  Needless to say I'd rather that import didn't have the affect of moving files around and I was a bit confused about why one worked and the other didn't.  

Then I ran across the following in the list archive:

On Jul 1, 2012, at 5:33 PM, Stevo SlaviÄ wrote:
Thanks for sharing!
It installs ok, but...
When importing existing maven projects from local git repository using this m2e egit connector (and when importing maven projects from remote svn repository using Polarion's Subversive m2e 1.1 compatible connector) where projects are multimodule projects and submodule directory names do not match their respective artifactId, parent/aggregator module gets imported well while submodules get copied over to directories with names equal to their artifactId, and then imported; old submodule directories get marked as deleted in svn.

I then have to logically remove eclipse projects for submodules, from parent/aggregator perspective revert changes and import existing  maven projects - then it imports well.

Probably this is bug in m2e itself and not in scm connectors.

<remainder of note elided in the interests of brevity...>
Kind regards,
Stevo.
This confirms the behavior I'm seeing.  There is a reply from the EGit developer after this that indicates that he wasn't going to look into it. I understand that the project structure in question (mismatch between artifactId and directory name) may be non-standard, but given that the vanilla M2E import works just fine having the SCM connectors work differently is... not good.

Are there any plans to look into this further?  Is there a bug logged already (where would one look to see about that)?  I like the ability to import directly from the Git repository view, so I'd like to see this inconsistency addressed.

Thanks,
Sean

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users



Back to the top