| Package visibility issues [message #619586] |
Mon, 24 September 2007 19:26  |
Eclipse User |
|
|
|
Ran into a couple plug-in package visibility issues. I'm using ECF 1.0.2.
I imported the source for the sample applications in
org.eclipse.ecf.example.collab_1.0.2 into my workspace. I assume these
examples are designed to be a starting point for developers to learn the
API. All went well, except that ECFGenericHyperlink.java gives this error:
Access restriction: The type AbstractURLHyperlink is not accessible due
to restriction
on required library
C:\projects\regatta-workbench\eclipse-3.3\eclipse\plugins
\org.eclipse.ecf.ui_1.0.200.v20070805-1626.jar
and ECFGenericHyperlinkDetector.java gives a similar compile error.
Also, I imported the RCP XMPP chat application from CVS and found that
org.eclipse.ecf.ui.actions.AsynchContainerConnectAction had a similar
visibility issue.
None of these look like classes intended to be internal to ECF.
Will there be a 1.0.3?
$cott
|
|
|
| Re: Package visibility issues [message #619587 is a reply to message #619586] |
Mon, 24 September 2007 22:56  |
| Eclipse User |
|
|
|
Hi Scott,
Scott Dybiec wrote:
> Ran into a couple plug-in package visibility issues. I'm using ECF 1.0.2.
>
> I imported the source for the sample applications in
> org.eclipse.ecf.example.collab_1.0.2 into my workspace. I assume these
> examples are designed to be a starting point for developers to learn the
> API.
No, we're not really there yet, unfortunately. We've got a bug in place
to refactor/redo the org.eclipse.ecf.example.collab plugin
https://bugs.eclipse.org/bugs/show_bug.cgi?id=160633
I've reopened this bug so that it can be used to capture these issues.
All went well, except that ECFGenericHyperlink.java gives this error:
>
> Access restriction: The type AbstractURLHyperlink is not accessible due
> to restriction
> on required library
> C:\projects\regatta-workbench\eclipse-3.3\eclipse\plugins
> \org.eclipse.ecf.ui_1.0.200.v20070805-1626.jar
>
> and ECFGenericHyperlinkDetector.java gives a similar compile error.
Hmmm...I don't immediately understand why this is giving you an access
restriction warning (it doesn't in my workspace), as the
AbstractURLHyperlink class (and AbstractURLHyperlinkDetector) are in an
exported package in org.eclipse.ecf.ui.
>
> Also, I imported the RCP XMPP chat application from CVS and found that
> org.eclipse.ecf.ui.actions.AsynchContainerConnectAction had a similar
> visibility issue.
We/I haven't been maintaining the RCP XMPP chat application (I assume
you mean the one from ecf1.osuosl.org). But I don't seem to have
visibility issues for dependencies.
I'm not sure why this would be necessary, but perhaps if you imported
the ECF core projects directly into your workspace (instead of having
them in the target platform).
>
> None of these look like classes intended to be internal to ECF.
>
> Will there be a 1.0.3?
I think yes. But it probably won't contain any changes that occur over
the next few days (it will probably be constructed for the Europa
maintenance release to happen this Friday).
There will also be a 1.1 (or perhaps it will be called 1.2) after we
have a foundation release review.
Thanks,
Scott
|
|
|
Powered by
FUDForum. Page generated in 0.04562 seconds
Home