Re: [Dltk-dev] Avoid emptying / recreating the H2 index upon every proje

[Kaloyan Raev <kaloyan.r@xxxxxxxx>]

Hi, 

I agree with your use case. Closing a project should clean memory, but should not delete any data on persistent storage like the H2 index. Close / open of a project should be cheaper than delete / create.

It's great you want to take the challenge in proposing a patch! I can help you going to the complete process of proposing a patch.

First, you need to open a bug in Bugzilla to the DLTK project: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=DLTK

Then you need to setup you development environment for the patch:

  1. Download and install the Eclipse Standard distro: https://www.eclipse.org/downloads/

  2. Set your Eclipse PDT installation as target platform - you do this from Window > Preferences > Plug-in Development > Target Platform

  3. Then using EGit clone the DLTK git repo project: git://git.eclipse.org/gitroot/dltk/org.eclipse.dltk.core.git

  4. Import the necessary plugin projects - I believe org.eclipse.dltk.core plugin should be enough for this change.

I think it is enough for first step. Let me know when you successfully complete them or if you have any troubles.

Greetings,

Kaloyan

On Tue, Jul 22, 2014 at 3:46 PM, Dori <avatar2004-franprix@xxxxxxxx> wrote:

Hello

If possible, how difficult would it be to avoid emptying / recreating the H2 index upon every project close / open ? Maybe by splitting the H2 database per-project and querying only projects that are open in the workspace (?)

Using PDT. Initial code review led me to the DLTK module but if this is better handled in PDT please let me know.

Quick use case :

Using Eclipse on a laptop for many projects. One (huge) project is only available on a network drive from a specific location. When moving around without access to the drive, I have to close / reopen the project every time. Can't just close Eclipse leaving the project open since I have to keep working on other projects in the same workspace while on the go.

Rebuilding the full index every time takes ages which is to be expected from such a large code base and that's not the issue. The problem is the index being emptied on closing the project.

Would be great if we could find a way to keep the index for a project while it is closed and reuse it incrementally the way it works if Eclipse is closed and reopened with the project kept open.

I'd be willing to contribute with some help / mentoring on the code base. I've never touched the Eclipse sources.

Thanks

--

_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/dltk-dev