| easily moving or copying projects [message #42193] |
Tue, 14 August 2007 01:55  |
Eclipse User |
|
|
|
Originally posted by: eclipsenews.20.epm.spamgourmet.com
Hi all,
I work with a codebase that contains several thousand files. Due to the
way the ticketing and branching works at my company, I often need to
checkout multiple copies of the codebase, switch them around, delete
them etc.
The problem I run up against with this is that each time I need to
checkout a new branch, I need to create a new eclipse project to work
with it. Not such a huge problem except that for each new project,
eclipse has to 'build' the workspace from scratch, and with 4000+ files
that takes quite a long time as you can imagine, and also pretty much
locks up the machine, since building seems to be a very memory and
processor intensive operation.
I've tried copying the .cache directories from old project to the new
ones, figuring that it could maybe somehow reuse the cache. However it
doesn't seem to work (I assume this is because it is determining whether
to refresh the cache based on file modified times or absolute paths or
something).
Does anyone have any tips for working like this with pdt that would make
my life a little less painful?
Cheers
Tom
|
|
|
| Re: easily moving or copying projects [message #42239 is a reply to message #42193] |
Tue, 14 August 2007 08:39  |
| Eclipse User |
|
|
|
Originally posted by: mep_eisen.web.de
There is a bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=155214
I played around with latest cvs snap and performance seems to be better. I
am using a project with about 6.5k files.
There might be a problem If you are using "publish the project to this
server" feature. This causes pdt to copy every source file to another
directory representing your webroot. Maybe you can tune performance at
this point. Simply set your project path to something Your webserver
sees...
|
|
|
| Re: easily moving or copying projects [message #42461 is a reply to message #42193] |
Tue, 14 August 2007 19:05 |
| Eclipse User |
|
|
|
Originally posted by: csurface.gmail.com
Do a "Close Project" on anything that doesn't pertain to the branch you're
working on. I doubt PDT would be able to build any projects in this state
(at least they shouldn't be building them, IMO).
"Tom Walter" <eclipsenews.20.epm@spamgourmet.com> wrote in message
news:f9r235$tsu$1@build.eclipse.org...
> Hi all,
>
> I work with a codebase that contains several thousand files. Due to the
> way the ticketing and branching works at my company, I often need to
> checkout multiple copies of the codebase, switch them around, delete them
> etc.
>
> The problem I run up against with this is that each time I need to
> checkout a new branch, I need to create a new eclipse project to work with
> it. Not such a huge problem except that for each new project, eclipse has
> to 'build' the workspace from scratch, and with 4000+ files that takes
> quite a long time as you can imagine, and also pretty much locks up the
> machine, since building seems to be a very memory and processor intensive
> operation.
>
> I've tried copying the .cache directories from old project to the new
> ones, figuring that it could maybe somehow reuse the cache. However it
> doesn't seem to work (I assume this is because it is determining whether
> to refresh the cache based on file modified times or absolute paths or
> something).
>
> Does anyone have any tips for working like this with pdt that would make
> my life a little less painful?
>
> Cheers
> Tom
|
|
|
| Re: easily moving or copying projects [message #42580 is a reply to message #42239] |
Wed, 15 August 2007 00:23 |
| Eclipse User |
|
|
|
Originally posted by: eclipsenews.20.epm.spamgourmet.com
Cool, well I look forward to the next release. Hopefully that will make
life less painful.
I am not using PDT to publish the project, I am working directly on the
files over a samba share.
Thanks.
Martin Eisengardt wrote:
> There is a bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=155214
>
> I played around with latest cvs snap and performance seems to be better.
> I am using a project with about 6.5k files.
>
> There might be a problem If you are using "publish the project to this
> server" feature. This causes pdt to copy every source file to another
> directory representing your webroot. Maybe you can tune performance at
> this point. Simply set your project path to something Your webserver
> sees...
>
|
|
|
| Re: easily moving or copying projects [message #42609 is a reply to message #42461] |
Wed, 15 August 2007 00:32 |
| Eclipse User |
|
|
|
Originally posted by: eclipsenews.20.epm.spamgourmet.com
Thanks, but I do that already, and yeah PDT doesn't build the closed
projects. And as long as I stay working on the same checkout,
performance is fine.
My problem is I often need to checkout entirely new branches of the same
project in order to work on multiple tickets simultaneously, or to work
on different servers (we have one that mimics production and another
with dev specific stuff like xdebug and forensic logging). And each time
I add a new checkout to eclipse as a new project, I have to sit through
the whole build project thing again.
Hopefully the next release will speed it up so it won't be such an issue.
Charlie Surface wrote:
> Do a "Close Project" on anything that doesn't pertain to the branch you're
> working on. I doubt PDT would be able to build any projects in this state
> (at least they shouldn't be building them, IMO).
>
> "Tom Walter" <eclipsenews.20.epm@spamgourmet.com> wrote in message
> news:f9r235$tsu$1@build.eclipse.org...
>> Hi all,
>>
>> I work with a codebase that contains several thousand files. Due to the
>> way the ticketing and branching works at my company, I often need to
>> checkout multiple copies of the codebase, switch them around, delete them
>> etc.
>>
>> The problem I run up against with this is that each time I need to
>> checkout a new branch, I need to create a new eclipse project to work with
>> it. Not such a huge problem except that for each new project, eclipse has
>> to 'build' the workspace from scratch, and with 4000+ files that takes
>> quite a long time as you can imagine, and also pretty much locks up the
>> machine, since building seems to be a very memory and processor intensive
>> operation.
>>
>> I've tried copying the .cache directories from old project to the new
>> ones, figuring that it could maybe somehow reuse the cache. However it
>> doesn't seem to work (I assume this is because it is determining whether
>> to refresh the cache based on file modified times or absolute paths or
>> something).
>>
>> Does anyone have any tips for working like this with pdt that would make
>> my life a little less painful?
>>
>> Cheers
>> Tom
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03577 seconds
] 
Search
Help
Register
Login
Home
