Scan on demand

[P.N.]

Hello!

Is it possible, to select files to be ignored per project? E.g. I've got
some big jars, which I do need only for resolving references, but
the classes contained will never change. Thus, they should be scanned
exactly once - on project creation. Sometimes it seems, they're
additionally scanned (but cannot check it, however).

Also, NB seems to not always detect, that the jars are the same, when
referenced from two different projects. Probably I can add those jars
as libraries programmatically (using my own project type - that's easier
than to add the jars to the global libraries, it seems).

Another related problem is, there are some (many) source for
customization. The IDE will never know, when these file change - so I
can only decide to allow NB to always scan automatically or to refresh
them always manually when needed. If I could NB programmatically tell to
refresh the sources (probably using an Ant task), it would be the
perfect solution.

One approach could be, to be able to customize a ClassPath instance,
i.e. path.enableScanning(true/false) and path.refresh().

Kind regards

Peter

[Jaroslav Tulach]

On Tuesday 13 October 2009 14:18:02 epdv wrote:
Hello Peter.
Thanks for you interest in SoD module. It's functionality description is
available at http://wiki.netbeans.org/ScanOnDemand

> Is it possible, to select files to be ignored per project?

You can ignore some files based on regexp.

> E.g. I've got
> some big jars, which I do need only for resolving references, but
> the classes contained will never change. Thus, they should be scanned
> exactly once - on project creation. Sometimes it seems, they're
> additionally scanned (but cannot check it, however).

There is also a way to turn on SoD logging (on the page again). You may want
to generate some logs and see why these JARs are thought to need rescanning.
If there is some pattern behind this malfunction, we would be glad to have
more information to fix it on parsing API side (so no SoD is needed at all).

> Also, NB seems to not always detect, that the jars are the same, when
> referenced from two different projects. Probably I can add those jars
> as libraries programmatically (using my own project type - that's easier
> than to add the jars to the global libraries, it seems).

If you know how to reproduce this, bug report would be perfect.

> Another related problem is, there are some (many) source for
> customization. The IDE will never know, when these file change - so I
> can only decide to allow NB to always scan automatically or to refresh
> them always manually when needed. If I could NB programmatically tell to
> refresh the sources (probably using an Ant task), it would be the
> perfect solution.

Ant during running from inside NetBeans IDE? That shall be possible (but you
need to write the Ant task yourself). Just call
http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-parsing-api/org/netbeans/modules/parsing/api/ParserManager.html

-jst

> One approach could be, to be able to customize a ClassPath instance,
> i.e. path.enableScanning(true/false) and path.refresh().
>
> Kind regards
>
> Peter

[P.N.]

Jaroslav Tulach wrote:
> On Tuesday 13 October 2009 14:18:02 epdv wrote:
> Hello Peter.
> Thanks for you interest in SoD module. It's functionality description is
> available at http://wiki.netbeans.org/ScanOnDemand
>
>> Is it possible, to select files to be ignored per project?
>
> You can ignore some files based on regexp.
>

That's not the same, and it is not what I wanted to do. Why should I
modify a global file, when I want to ignore one of several path's in the
project to be ignored?

>> E.g. I've got
>> some big jars, which I do need only for resolving references, but
>> the classes contained will never change. Thus, they should be scanned
>> exactly once - on project creation. Sometimes it seems, they're
>> additionally scanned (but cannot check it, however).
>
> There is also a way to turn on SoD logging (on the page again). You may want
> to generate some logs and see why these JARs are thought to need rescanning.
> If there is some pattern behind this malfunction, we would be glad to have
> more information to fix it on parsing API side (so no SoD is needed at all).
>

If I can catch it, I'll do so. However, there's sometimes scanning
starting without anything which should cause rescanning. Sometimes it's
probably just the wrong "task label", i.e. some other task probably uses
the same verb for sth. different (probably looking for plugins, updating
hudson info or anything else).

>> Also, NB seems to not always detect, that the jars are the same, when
>> referenced from two different projects. Probably I can add those jars
>> as libraries programmatically (using my own project type - that's easier
>> than to add the jars to the global libraries, it seems).
>
> If you know how to reproduce this, bug report would be perfect.
>
When scanning starts, I cannot always see what is scanned. However, this
is sth. I noticed some months ago, so it may be fixed. Didin't use these
libs for some time. If I can tell something definite, I'll write a bug
report.

>> Another related problem is, there are some (many) source for
>> customization. The IDE will never know, when these file change - so I
>> can only decide to allow NB to always scan automatically or to refresh
>> them always manually when needed. If I could NB programmatically tell to
>> refresh the sources (probably using an Ant task), it would be the
>> perfect solution.
>
> Ant during running from inside NetBeans IDE? That shall be possible (but you
> need to write the Ant task yourself). Just call
> http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-parsing-api/org/netbeans/modules/parsing/api/ParserManager.html
>

Hm, seems not to be a good approach - seems I'll have to get a parser
implementation or write myself. Probably I've just misunderstood the
concept, but it seems easier to adopt the SoD action classes. The bad
thing is, it seems I have to depend on implementation version of parsing
api.

Kind regards

Peter

> -jst
>
>> One approach could be, to be able to customize a ClassPath instance,
>> i.e. path.enableScanning(true/false) and path.refresh().
>>
>> Kind regards
>>
>> Peter
>
>
>