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.

Bug 211707 - IDE Deployment: Hints processor not available on update center
Summary: IDE Deployment: Hints processor not available on update center
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: Hints (show other bugs)
Version: 7.2
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-25 11:56 UTC by Peter Nabbefeld
Modified: 2012-04-25 12:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2012-04-25 11:56:49 UTC
I admit I've done something suspicious:
I've removed org-netbeans-modules-java-hints-processor.jar from an outdated testing directory to get it updated using "Missing Modules Resolver".

Unlike other modules, it is not built with the job "nbms-and-javadoc", so it's obviously a deployment problem.
Comment 1 Jan Lahoda 2012-04-25 12:27:00 UTC
What exactly are you trying to do? the -java-hints-processor module is no longer part of the trunk build, as the Java Hints SPI has been introduced and the processor has been moved to org-netbeans-spi-java-hints.jar.
Comment 2 Peter Nabbefeld 2012-04-25 12:44:13 UTC
Sorry for the inconvinience - seems the move was done recently, as my local repo copy still contains the module (updated two or three days ago, so should contain the changes until then, I'd expect).
Comment 3 Jan Lahoda 2012-04-25 12:51:18 UTC
Not that recently - was done about two months ago. Where exactly do you see the module? The directory in the checkout (java.hints.processor) may still exits if you have e.g. the build subdirectory (I do in some of my clones). But it should not contain any sources.
Comment 4 Peter Nabbefeld 2012-04-25 12:58:13 UTC
Ah, yes, You're right - didn't notice that. Usually I'm not so crazy as to try to force updates of outdated modules (which are not always recognized for updates, probably because of their outdated deps) manually ... ;-)