[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée resolved IVYDE-68.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Nicolas Lalevée
Let's say it if fixed.
The only two parts of code which is using internal code of Eclipse is:
* to work around a bug in Eclipse 3.3
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=154071)
* to allow a context menu directly on the Ivy container.
> IvyDE is using some internal classes of Eclipse
> -----------------------------------------------
>
> Key: IVYDE-68
> URL: https://issues.apache.org/jira/browse/IVYDE-68
> Project: IvyDE
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Nicolas Lalevée
> Assignee: Nicolas Lalevée
> Fix For: 2.0.0
>
> Attachments: IVYDE-68-r607532.patch, IVYDE-68-r617088.patch,
> ivyde.diff
>
>
> Some classes in IvyDE use come classes which are in some
> {{org.eclipse....internal... }} packages, which should not be used. Compiling
> IvyDE with Eclipse 3.3 raise warning like :
> {quote}
> Discouraged access: The method containerPut(IJavaProject, IPath,
> IClasspathContainer) from the type JavaModelManager is not accessible due to
> restriction on required library
> /Users/nicolas/tools/eclipse-3.3/plugins/org.eclipse.jdt.core_3.3.1.v_780_R33x.jar
> ivyde/src/java/org/apache/ivyde/eclipse/cpcontainer
> IvyClasspathContainer.java {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
