[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556552#action_12556552
]
Nicolas Lalevée commented on IVYDE-68:
--------------------------------------
OK I see the issue, the UI is effectively not very clear. It seems that the
eclipse developer didn't see the real issue here, maybe he didn't read your
last comment ?
About letting the fix into IvyDE, I see no reason to not have this kind of
eclipse internal fix within the plugin. But it seems wrong to have the plugin
only target 3.2. Maybe you could create another plugin
org.apache.ivy.eclipse.javasearchfix that could be downloaded within the IvyDE
update site, with as many version as there are tagetted eclipse version.
> 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: 1.3.0
> Reporter: Nicolas Lalevée
> Attachments: IVYDE-68-r607532.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.
