Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Open Metadata Search"
(→'1.0 Introduction') |
|||
| Line 2: | Line 2: | ||
== ''''''1.0 Introduction'''''' == | == ''''''1.0 Introduction'''''' == | ||
| − | + | In working with huge projects there are many instances the developers fall into situations where they need to find Java EE artifacts and relevant documents to the project. It is indeed a tedious task to remember the exact locations of all project artifacts. Generally a particular artifact is remembered by a part of the content or some other special attribute such as the file name. At such instances developers usually tend to locate the file by performing a file search available in the operating system or going for a full text search. This indeed is a tedious task and wastes a lot of time of the developer. At the same time the results that he or she obtains might not be the most accurate and appropriate one available. | |
| + | It is indeed bliss if the Developing IDE itself can provide a Java EE metadata search. Obviously this can save a lot of time of the developer and it also can deliver the most optimal results that he is longing for. | ||
Revision as of 12:03, 1 April 2009
(Index search for Java EE metadata)
'1.0 Introduction'
In working with huge projects there are many instances the developers fall into situations where they need to find Java EE artifacts and relevant documents to the project. It is indeed a tedious task to remember the exact locations of all project artifacts. Generally a particular artifact is remembered by a part of the content or some other special attribute such as the file name. At such instances developers usually tend to locate the file by performing a file search available in the operating system or going for a full text search. This indeed is a tedious task and wastes a lot of time of the developer. At the same time the results that he or she obtains might not be the most accurate and appropriate one available. It is indeed bliss if the Developing IDE itself can provide a Java EE metadata search. Obviously this can save a lot of time of the developer and it also can deliver the most optimal results that he is longing for.