Re: [m2e-users] m2e-users Digest, Vol 44, Issue 2

[Anders Hammar <anders@xxxxxxxxxx>]

This one should work:
http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-egit/0.14.0/N/0.14.0.201207041402/

/Anders

On Sun, Sep 2, 2012 at 4:05 AM, Sean Fitts <sean@xxxxxxxxxx> wrote:
>
> Mike, hi.  That does look like the same bug and the fix looks like what I
> was asking for (make it work like the vanilla Import).  Unfortunately I
> tried loading both the current 1.2 milestone and the most recent build and
> in both cases I could not load the current version of m2e-egit.  Got a
> series of dependency errors.  Are there updated connectors that go with this
> build of m2e?  Oh -- and should the fix be in the current milestone build?
>
> Thanks,
> Sean
>
>>
>>
>> Message: 3
>> Date: Sat, 1 Sep 2012 18:49:55 -0600
>> From: Mike Youngstrom <youngm@xxxxxxxxx>
>> To: Maven Integration for Eclipse users mailing list
>>         <m2e-users@xxxxxxxxxxx>
>> Subject: Re: [m2e-users] Inconsistent Import behavior M2E vs. M2E-Git
>>         connector
>> Message-ID:
>>
>> <CAEoPEDo+X4qB_o9DTMo5C=c7JKAXW_7-KvnBuWPB9WZT=Jz3sg@xxxxxxxxxxxxxx>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> 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<https://mail.google.com/mail/u/1/?ui=2&view=bsp&ver=ohhl4rw8mbn4>,
>> >> 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
>> >
>> >
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <https://dev.eclipse.org/mailman/private/m2e-users/attachments/20120901/60781cde/attachment.html>
>>
>> ------------------------------
>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>
>>
>> End of m2e-users Digest, Vol 44, Issue 2
>> ****************************************
>
>
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>