Re: [m2e-users] Having a Bad Week - eclipse sick

[Alejandro Calbazana <acalbazana@xxxxxxxxx>]

Oh!  That reminds me!

We keep workspace and project metadata in separate directories.   This
might be standard practice for some, but eclipse does not prevent you
from storing projects "inside" of a workspace directory.  Doing so
brings pain...

Thanks,

Alejandro

On Mon, Mar 28, 2011 at 2:48 PM,  <Jordan.Hein@xxxxxxxxxxx> wrote:
>
> Back in the day, well, only a few years ago, I would get an eclipse crash
> and then have all sorts of issues after that. The solution then was to use
> an entirely new eclipse workspace. I know the prospect of using a new
> workspace sucks but if you are at the end of your rope it is something to
> try. I have also been known to blow away my eclipse installation, decompress
> it from zip again and reinstall all my plugins and create a new workspace.
>
> Performance, yes, Eclipse and M2E combination is a memory, disk, and CPU
> hog. I give Eclipse a bunch of RAM and I try not do anything until the
> progress bar in the lower right disappears. It seems like most instability
> occur when users try to tell the IDE to do to much. Keep your eye on that
> progress bar on the lower right and don't do anything until that thing
> disappears.
>
> You have my sympathies. Keep supporting the Eclipse and M2E dev team because
> integrating Maven with Eclipse this is a tough domain space.
>
> -Jordan
>
>
>
> m2e-users-bounces@xxxxxxxxxxx wrote on 03/27/2011 11:20:37 AM:
>
>> [image removed]
>>
>> Re: [m2e-users] Having a Bad Week - eclipse sick
>>
>> Alejandro Calbazana
>>
>> to:
>>
>> Maven Integration for Eclipse users mailing list
>>
>> 03/27/2011 11:20 AM
>>
>> Sent by:
>>
>> m2e-users-bounces@xxxxxxxxxxx
>>
>> Please respond to Maven Integration for Eclipse users mailing list
>>
>> FWIW -  My team suffered with m2eclipse + maven projects.  After I had
>> them make a few changes, things seem workable and stable.  I've
>> invested some time getting them setup properly.  The following might
>> help:
>>
>> - Use the latest HotSpot JVM while running eclipse.  I've tried
>> JRockit and, for whatever reason, this makes M2Eclipse unusable under
>> Windows (Linux runs fine).  It predictably hangs while updating
>> indexes.  I can reproduce this at will.
>> - Install and external maven runtime and point to it.  The embedded
>> one seemed to work okay, but freaks out in some instances.  I haven't
>> figured out the pattern here.
>> - Ensure that you give the jvm enough memory.
>> - If you are going things like process resources, make sure that you
>> set this goal to run during the import process.  You can always go
>> back and update project configuration, but its easy enough to get this
>> done while the project imports.
>>
>> It is a shame that eclipse doesn't have native maven support...  Then
>> again there is always mvn eclipse:eclipse :)
>>
>> Thanks,
>>
>> Alejandro
>>
>> On Sun, Mar 27, 2011 at 9:18 AM, Steve Cohen <scohen@xxxxxxxxxxxxxxx>
>> wrote:
>> > On 03/27/2011 08:04 AM, Benson Margulies wrote:
>> >>
>> >> I don't believe that 'unused perspectives' eat anything interesting. I
>> >> do believe that those strange labels indicate that something, well,
>> >> strange, happened to your Eclipse, and I'm at a loss to characterize
>> >> what it might have been. But arbitrary giant squid may be swimming
>> >> below if that's the surface, at least as far as I know.
>> >>
>> >> While I raised the possibility that you are suffering something
>> >> tangled up with your use of a copy of Windows with antique license
>> >> places, I certainly can't prove it from here. In general, M2E takes
>> >> one very complicated system (Eclipse) and plugs another very
>> >> complicated system (Maven) into the very same JVM. The two systems
>> >> have, in some areas, independent, big, complex, mechanisms for solving
>> >> related problems (class loading and artifact management, e.g.). I
>> >> applaud the efforts of the M2E team. I believe that some problems are
>> >> inevitable as they climb the hill. I decided to invest effort in using
>> >> M2E (and building some plugins) rather than adopting the orphan
>> >> maven-eclipse-plugin and making improvements to it. This choice hasn't
>> >> entirely worked out yet, but I retain hope.
>> >>
>> >>
>> > me too.
>> >
>> > Have now adopted your permgen suggestions.  Keeping fingers crossed.
>> > _______________________________________________
>> > 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
>
>