[
https://issues.apache.org/jira/browse/IVYDE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556203#action_12556203
]
Nicolas Lalevée commented on IVYDE-68:
--------------------------------------
bq. BTW, I'm impressed how fast you catch up with the cache management changes
in Ivy!
I was not sure about what I did in fact, but it was happily working. And
further more I knew that you will review it ! At least it sounds that the Ivy
API is quite self explaining ;)
bq. The FixedJavaSearchPage is a problem to maintain, and since it has never
been documented and is probably not that much useful, I think we could remove
it. WDYT?
I fact I don't know the purpose of this feature. You wrote once you had some
debate with some eclipse developers about it. Do you have some pointers ?
> 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.
