This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | IndexabilityQuery is needed | ||
---|---|---|---|
Product: | editor | Reporter: | Jaroslav Tulach <jtulach> |
Component: | Parsing & Indexing | Assignee: | Vitezslav Stejskal <vstejskal> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | pjiricka, tmysik |
Priority: | P3 | Keywords: | API |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 169036 |
Description
Jaroslav Tulach
2009-07-23 12:54:47 UTC
This sounds reasonable to me. I assume that the implementors of IndexabilityQuery will also provide means for user to configure what is or is not indexable in particular projects. In other the infrastructure is not going to provide any support for implementing these queries nor it is going to provide default query (with eg. some sort of UI customizer in Tools-Options). In general, I still assume that the mainstream usecase is to index stuff under the source roots in the project and the cases when IQ is needed are rather rare. I'm CCing Tomas, because he as the potential primary user of this API might have some useful notes/ideas/requests. I'd be grateful for some real world user scenarios/usecases that would describe how this is going to be used. Thanks > In general, I still assume that the mainstream usecase is to index stuff under the source roots in the project and
> the cases when IQ is needed are rather rare.
Yes, I agree. I did it because - and this the example you asked for, Víťo - there are frameworks that define specific
directory structure, e.g. Smarty or Symfony (Symfony is supported in NB 6.8):
.
|-- apps
|-- cache <-- needs to be ignored otherwise some classes are doubled in Go To Type, code completion etc.
|-- config
|-- data
|-- doc
|-- lib
|-- log
|-- plugins
|-- symfony
|-- test
`-- web
Moreover, many users already asked for such possibility for their existing projects, because of folders with
documentations etc. underneath source-directory.
(I know it's a bad practice but there's no easy way to solve it now.)
One comment - I think we need to be able to listen on changes of the exclude pattern.
FYI, I have asked originally for the same functionality (in C++ projects source roots are full of object files after building project). For now we use Jan's patch where we customize class paths (although it's really funny to have C++ project depending on org.netbeans.spi.java.classpath.FilteringPathResourceImplementation) http://hg.netbeans.org/cnd-main?cmd=changeset;node=f49234c9860a Obsolete, see issue #170308 for more information. |