NetBeans 7.4 mx ideinit problem

[Doug Simon]

Does this help:

1. In NetBeans: File -> Project Group -> Remove “graal”
2. mx ideclean
3. mx fsck (answer yes to all)
4. mx netbeansinit
5. In NetBeans: File -> Project Group -> New Group... -> Folder Of Projects

It seems that NetBeans does not react to well to having projects disappear from behind its back (which can happen when you pull changes that delete/rename/create projects).

-Doug

On Nov 1, 2013, at 7:50 PM, Eric Caspole <eric.caspole at amd.com> wrote:

> I found that I can go into NetBeans and right click on each project and manually set the JDK correctly, and then it seems to work OK, although that is very time consuming with so many projects.
> 
> I never see this problem on Linux, BTW. Is the "mx ideinit" different between Windows/Linux?
> Eric
> 
> On 11/01/2013 02:11 PM, Mick Jordan wrote:
>> On 11/1/13 11:02 AM, Caspole, Eric wrote:
>>> 
>>> I don't know if this is a NetBeans bug or a problem with the "mx
>>> ideinit" output.
>>> Anyone have any suggestions?
>>> 
>> There have been changes in the ideinit area recently, so it could well
>> be a bug in mx. I don't use Netbeans myself but what we want to see
>> probably is the config files that get generated by mx.
>> 
>> One thing you might be able to do is clone an older version of the repo,
>> say a month ago, and run mx ideinit in there and compare the config
>> files. Try the revision before the none that has the comment:
>> 
>> "Allow mxtool suites to be in separate repositories (CR-1367)", which
>> was Sep 11.
>> 
>> 
>> 
>> 
>