Re: [platform-text-dev] Re: missing IDocument in org.eclipse.jface.text

[Kai-Uwe Maetzel <maetzel@xxxxxxx>]

The API did not change. What changed are the dependencies
between plug-ins. If your plug-ins depend on org.eclipse.ui they
should be fine, as org.eclipse.ui exports the newly created plug-ins.
Updating of the class path should happen automatically on import
when working with binary plug-ins. You can also force it manually
by invoking "Update classpath" from a project's context menu.

Information about the split can now be found at:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-text-home/dev.html

The link got accidentally removed when setting up the
Platform Text web pages.

Kai


At 01:34 PM 10/27/2002 +0100, you wrote:
> sorry about the mail
>
> I finally found it in org.eclipse.text
>
> btw is anywhere recorded how the split is done or is there an up to date
> API reference available?
>
> thanx and sorry again
>   Jens Lukowski
>
>
>
> ----- Original Message -----
> From: "Jens Lukowski" <jens.lukowski@xxxxxx>
> To: <platform-text-dev@xxxxxxxxxxx>
> Sent: Sunday, October 27, 2002 1:26 PM
> Subject: [platform-text-dev] Re: missing IDocument in org.eclipse.jface.text
>
>
> > sorry to bother you with this, maybe I am just blind but it seems
> > that in org.eclipse.jface.text the interface IDocument is missing
> >
> > am I wrong ?
> >
> > Jens Lukowski
> >
> > _______________________________________________
> > platform-text-dev mailing list
> > platform-text-dev@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/platform-text-dev
> >
>
> _______________________________________________
> platform-text-dev mailing list
> platform-text-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-text-dev