Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] m2e 1.1 and compatible egit connector availability

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.

Maybe m2e should also bug users that have submodule directory names and their artifactId not aligned with warnings, and recommend and offer quick-fixes to align the names - maven plugins (like site and related ones) expect (or at least used to expect) this consistency, it's more intuitive, and helps avoid collisions when working on more (related) projects in single workspace. Nevertheless, it should work ok with configuration which is not aligned with convention.

Btw, maybe Sonatype developers would be interested in somewhat related topic (m2e scm connector for Subversive) at

Kind regards,

On Sun, Jul 1, 2012 at 3:05 PM, Jason van Zyl <jason@xxxxxxxx> wrote:
To help you can test this build here:

On Jul 1, 2012, at 9:03 AM, Stevo Slavić wrote:

Hello m2e community,

m2e egit connector in the current m2e 1.1 catalogue is not compatible with recently released egit 2.0 (see [1])

What needs to be done to have a compatible version released? Is there any help needed?

Kind regards,

[1] m2e egit dependency conflict

Operation details
Cannot complete the install because of a conflicting dependency.
Software being installed: Maven SCM Handler for EGit (
Software currently installed: Eclipse EGit (
Only one of the following can be installed at once:
Git Team Provider UI (org.eclipse.egit.ui
Git Team Provider UI (Incubation) 0.8.4 (org.eclipse.egit.ui 0.8.4)
Git Team Provider UI (org.eclipse.egit.ui
Git Team Provider UI (org.eclipse.egit.ui
Git Team Provider UI (Incubation) 0.11.1 (org.eclipse.egit.ui 0.11.1)
Git Team Provider UI (Incubation) 0.9.1 (org.eclipse.egit.ui 0.9.1)
Git Team Provider UI (org.eclipse.egit.ui
Cannot satisfy dependency:
From: Eclipse EGit (
To: org.eclipse.egit.ui []
Cannot satisfy dependency:
From: Maven SCM Handler for EGit (org.sonatype.m2e.egit
To: bundle org.eclipse.egit.ui [1.0.0,2.0.0)
Cannot satisfy dependency:
From: Maven SCM Handler for EGit (
To: org.sonatype.m2e.egit []
m2e-users mailing list



Jason van Zyl
Founder & CTO, Sonatype
Founder,  Apache Maven

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

-- Thoreau 

m2e-users mailing list

Back to the top