Community
Participate
Working Groups
M4 testing (I20041214-2000-gtk) 1. created a new 1.4 project, package src/com.example.m4testing 2. new interface wizard, create interface "ITester" 3. new class wizard, create class "Tester" - in the wizard, press A to add an interface Expected: ITester shows up in the Interface browser Actual: it does not 4. in "Tester", try to insert the implements clause to have Tester implement ITester. Expected: ITester shows up as content assist proposal Actual: it does not show up -> The new interface does not exist neither in the alltypes cache nor is it returned from content assist (this is why I figured this is a core problem). -> searching for ITester type declarations works
Note that compiling works fine, i.e. if I add ITester manually to the implemented interfaces of Tester, I get the error that I need to implement the declared methods.
Cannot reproduce using last 3.1 M4 candidate build (I200412142000). Which build are you using?
> M4 testing (I20041214-2000-gtk)
So we have the same build... (I also test using Linux-GTK). Did you create your interface/class in package com.example.m4testing or in default package...? When creating interface in default package and creating class in com.example.m4testing package, I get the interface in the list when I push on Add button of wizard but not in the code assist list. This behavior is normal as since 1.4, default package is not in the classpath... Conversly, when I create the interface in com.example.m4testing package and creates class in default package I have no error... But unfortunately, I never encounter your problem (ie. ITester neither in wizard list nor in code assist list...).
I created it directly in the said package.
I really do not understand... I've also tried in WinXP and everything works well as for Linux-GTK. So, perhaps asking stupid questions will help: 1) create a new 1.4 project means create project using default 1.4.2 VM or did you specify something special while creating it? 2) package src/com.example.m4testing means create source folder 'src', then package com.example.m4testing in it?
yes to both - everything straight forward, no special tricks. I can try on a fresh workspace, if you like (this was in my normal workspace).
yes it could be interesting...
cannot reproduce with fresh workspace, but it is consistently failing in my existing workspace (also after restarting the workbench).
Ok, I've found it. The project *name* must contain numbers. The test case fails with projects name ZZZ14 and ZZZ15, but not with ZZZPickup.
Not true, now after failing, it consistently fails, even with non-numbered project names.
The next time I will remember to check my type filters, which were set to ignore all com* types. sorry for the hassle!
no problem. happy that you found the reason... :-)
