Re: Subclipse, Maven and m2eclipse

Mark Phippard <[email protected]>
Newsgroups gmane.comp.version-control.subversion.subclipse.user
Message-ID <CAHFaGCpiwvGL2mVs_7-6TVrvPU9GU9xXe92zYGc2-AuhNWeQrA@mail.gmail.com>
Not sure if you saw my comments in the issue, but the best course of
action at the moment would be to uninstall the feature I have
published and install the one on the m2e discovery site.

The current version of m2e is providing a connector that works with
Subclipse 1.8.  The problem is that its version number if still 0.13
so it did not replace the 0.14 version that did not work with m2e 1.2.

So I would just use the connector provided with m2e for now.

Mark



On Thu, Oct 25, 2012 at 2:38 PM, Steve Gillam <[email protected]> wrote:
> Wow - now that's service :)
>
> My post on the aforementioned thread was just to address some unwarranted silliness going on in there.
>
> You anticipated my desire in that I was not aware that m2e started in Juno as 1.1 but it is now 1.2 and there was an incompatible dependency in tigris.org's Subclipse 0.14 (required for Subversion 1.8+)
>
> I can confirm also that Subclipse 0.15 now installs (pom's seem to still have 0.14 if that's of significance to you? but shows in Eclipse Installer as 0.15.xxxxxx) so I'll now go and play with my fully up to date env subversion(1.8)/mvn(3.0)/eclipse(Juno(m2e(1.2)+subclipse (0.15))/testNG(6.7)
>
> Grateful thanks - where's the 'buy me a beer' button?
>
> ------------------------------------------------------
> http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3023522
>
> To unsubscribe from this discussion, e-mail: [[email protected]].



-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3023536

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.