Doc for Bug 496145 - Adding variable in interface gives error and
suggests major version change, but adding to class is OK?
diff --git a/bundles/org.eclipse.pde.doc.user/api_contexts.xml b/bundles/org.eclipse.pde.doc.user/api_contexts.xml
index d3542b0..6ea4aac 100644
--- a/bundles/org.eclipse.pde.doc.user/api_contexts.xml
+++ b/bundles/org.eclipse.pde.doc.user/api_contexts.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
- Copyright (c) 2005, 2012 IBM Corporation and others.
+ Copyright (c) 2005, 2017 IBM Corporation and others.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which accompanies this distribution, and is available at
@@ -32,6 +32,10 @@
<topic href="http://wiki.eclipse.org/Execution_Environments" label="Execution Environments"/>
<topic href="tasks/api_tooling_options.htm" label="Changing API Options"/>
</context>
+ <context id="apitools_error_warning_explain_incompatibility_field_addition_class" title="'Field Addition to Class' Incompatibility">
+ <description>Adding an API field to an API class is a breaking change due to two reasons 1) Name clash 2) Possible linkage error. See the 'Add API field incompatibility' link below for details. </description>
+ <topic href="https://wiki.eclipse.org/Evolving_Java-based_APIs_2#add-api-field" label="Add API field incompatibility"/>
+ </context>
<context id="apitools_error_warning_prop_page" title="API Errors/Warnings">
<description>This page allows you to configure project specific settings for problem severities related to API compatibility and use.</description>
<topic href="reference/api-tooling/preferences/ref-errorswarnings.htm" label="API Error and Warning Preferences"/>
