Bug 34794 - extendable JDT Indexer
Summary: extendable JDT Indexer
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-12 05:36 EST by Eli Lopian CLA
Modified: 2004-05-10 05:56 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eli Lopian CLA 2003-03-12 05:36:03 EST
There is a need to extend the JDT Indexer.

We are currently building huge Java projects via samba on remote unixs,
Our computers/network don't have the power to compile the full application
on the net. so we copy the jars to our PC's and compile only the remote
files that the user checked-out.

But, we can not use most of the refeactoring abilities. We do have our own
Cross-Reference (Indexer) database on our master code. So if the
refactoring can use this, we can checkout all the needed files (via
checkout on edit feature of the team plugin) and the refactoring will work.

To do this we need an extention point for the Indexer to add the reference usage of files that are
not in the workspace

(I know that there are plans to extract parts of the Indexer for the CDT planed for version 2.2)
Comment 1 Jerome Lanneluc CLA 2003-03-12 05:51:27 EST
Will consider for 2.2.
Comment 2 Eli Lopian CLA 2003-05-28 16:31:33 EDT
Any news about this, I can't see any work in this area in the 3.0 plans.
What are the CDT group doing about this?
Comment 3 Eli Lopian CLA 2003-05-28 16:33:14 EDT
I'm going to reopen this bug to see if some work can be done if 3.0
Comment 4 Philipe Mulet CLA 2003-06-02 07:21:17 EDT
We are planning to generalize our index infrastructure for the 3.0 release, so 
as to accomodate Java-like languages. Intriguing whether this could solve your 
problem as well...



Comment 5 Eli Lopian CLA 2003-06-22 03:16:48 EDT
Hi Philippe, I hope that it will solve the problem.
Basiclly what is needed is an extention point for the indexer.

So for example, if we are searching for references of method C.m(), the 
indexer/search should perform its normal search and and then call the extention 
for more references. (The extention should handle duplicates if required.)

Refactor Example:
a (User) Project contains one file C.java, the master contains 100 more that 
are jared up and added to the build path. If we want to refactor C.m() and 
change its name to m1() then the Indexer will return all references to m() 
including those that appear in the 100 master files (returned from the 
extention point), if the files are read only (in the Jar/Master) - refactoring 
should act as normal and show a message.

This should work for call heirarcy too.

If you need more examples or help with design or coding please contact me.

thanks

LE
Comment 6 Philipe Mulet CLA 2004-03-25 06:15:11 EST
The new search participant API should allow to do this.
Comment 7 Philipe Mulet CLA 2004-05-10 05:56:02 EDT
New APIs for search participant now allow you to contribute to indexes 
considered during search process.

See SearchParticipant API.