Bug 89808 Wording on the acess rules pages
20050329 - we should use 'Forbidden' instead of 'Non-accessible' to be consistent with jdt.core and the compiler settings - the text on the 'new access rules' should give examples for patterns
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/TypeRestrictionEntryDialog.java
fPatternDialog.setDialogFieldListener(adapter);
		
		fRuleKindCombo= new ComboDialogField(SWT.READ_ONLY);
		fRuleKindCombo.setLabelText(NewWizardMessages.getString("TypeRestrictionEntryDialog.kind.label")); 
		fRuleKindCombo.setDialogFieldListener(adapter);
		String[] items= {
				NewWizardMessages.getString("TypeRestrictionEntryDialog.kind.non_accessible"), 
				NewWizardMessages.getString("TypeRestrictionEntryDialog.kind.discourraged"), 
				NewWizardMessages.getString("TypeRestrictionEntryDialog.kind.accessible") 
		};
		fRuleKinds= new int[] {
				IAccessRule.K_NON_ACCESSIBLE,
				IAccessRule.K_DISCOURAGED,
				IAccessRule.K_ACCESSIBLE
		};
		fRuleKindCombo.setItems(items);
		
		
		if (ruleToEdit == null) {
			fPatternDialog.setText(""); 
			fRuleKindCombo.selectItem(0);
		} else {
			fPatternDialog.setText(ruleToEdit.getPattern().toString());
			for (int i= 0; i < fRuleKinds.length; i++) {
				if (fRuleKinds[i] == ruleToEdit.getKind()) {
					fRuleKindCombo.selectItem(i);
					break;
				}
			}
		}