I may have found out something.  I turned off "Build Automatically"
and everything seemed to import much more smoothly.

On Tue, Oct 28, 2008 at 2:03 PM, James Carman
<[EMAIL PROTECTED]> wrote:
> On Tue, Oct 28, 2008 at 1:54 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
>> James Carman wrote:
>>>
>>> I just downloaded everything today, so I should be running the latest
>>> and greatest of everything.  Here's what I did:
>>>
>>> 1.  Download latest Eclipse for Java developers bundle.
>>> 2.  Install latest Subclipse
>>> 3.  Install latest WTP
>>> 4.  Install latest AJDT
>>> 5.  Install latest m2eclipse including Subclipse, WTP and AJDT
>>> integration.
>>>
>>> Try to import my projects.
>>
>>  Can you please clarify if you are importing your Maven projects as multiple
>> Eclipse projects?
>
> I am importing maven projects and then choosing all projects that show
> up under my main directory.
>
>>  Also, what versions of Subclipse and AJDT exactly you have installed?
>
> Eclipse AspectJ Development Tools
>
> Version: 1.6.0.200809031144
> AspectJ version: 1.6.2.20080828190000
>
> (c) Copyright IBM Corp. and others 2000, 2006.  All rights reserved.
> Visit http://www.eclipse.org/ajdt
>
>>>
>>> It takes up a huge amount of memory and bogs down my machine
>>
>>  Can you please be more specific about "huge amount of memory" and what
>> "bogs down my machine" means?
>
> 2.6 GB is a huge amount of memory.  By bogging down my machines, I
> mean that it eats up the CPU and everything else slows down.
>
>>
>>  What is happening at that time? Please check what is shown in the Progress
>> view and in Maven console.
>
> 1.  Importing Maven projects
> 2.  Updating Maven Dependencies
>>
>>  The m2eclipse runs several jobs in the background, but if you experiencing
>> noticeable slowness of the Eclipse workbench, please take few thread dumps
>> from the Eclipse JVM. See
>>
>>
>>> [INFO] Final Memory: 62M/439M
>>>
>>
>>  m2eclipse is also running Maven while importing those projects, so you may
>> expect it to consume some amount of memory close to amount used by Maven in
>> command line, though m2eclipse runs Maven on those projects one by one.
>>>
>>> The workspace state file is only 742.3 KB in size.  Is that too big?
>>>
>>
>>  Not at all. It is about the right size for workspace of your size and it
>> also seem like you have some decent number of dependencies in your projects.
>>
>>  regards,
>>  Eugene
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>   http://xircles.codehaus.org/manage_email
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to