Community
Participate
Working Groups
I've written a plugin which * has a dependency to org.eclipse.jface.text 3.11.0 * in the Java code, references a constructor defined in this dependency (ContentAssistant(true) in this case) which is annotated with @since 3.12 in Javadoc and I see no warning reported by API Tools. In such case, I would expect the API Tools to show a warning on the constructor reference to highlight that my dependency minimal version doesn't match the version required in the code.
Does your target have org.eclipse.jface.text 3.11.0 or 3.12? If the target doesnt have 3.11 it should give something like "Unsatisfied version constraint" in a manifest file. I think I can recreate this but can you attach a sample project file so that we are sure that we are discussing the same problem.
(In reply to Vikas Chandra from comment #1) > Does your target have org.eclipse.jface.text 3.11.0 or 3.12? > > If the target doesnt have 3.11 it should give something like "Unsatisfied > version constraint" in a manifest file. Target has 3.11, but 3.12 is opened in the workspace.
To reproduce it: * Set baseline to Eclipse 4.6.2 * Import and open org.eclipse.jface.text and org.eclipse.ui.genericeditor in workspace from eclipse.platform.text repo, using commit c88654a1094f40f402575bfd0e258aade7dac74b You'll notice that: * org.eclipse.ui.genericeditor/META-INF/MANIFEST.MF mentions org.eclipse.jface.text;bundle-version="3.11.0" * org.eclipse.ui.genericeditor/src/org/eclipse/ui/internal/genericeditor/ExtensionBasedTextViewerConfiguration.java line 105 references a constructor for ContentAssistant which was introduced in 3.12 and has the annotation setup And no warning is shown on the code, nor on the MANIFEST.MF
Ok. I will investigate this further.
