Re: [platform-releng-dev] [eclipse-build]Build N20051118-0010 (Timestamp

[Oleg Besedin <obesedin@xxxxxxxxxx>]

There was a change in the org.eclipse.core.runtime
that might affect people who specify classpaths explicitly (such as javadoc
scripts).

The org.eclipse.core.runtime plugin
is being split into several portions:

• org.eclipse.equinox.common - portions that are needed by more than one piece of the former runtime plugin (i.e. IPath, IStatus, IProgressMonitor)
• org.eclipse.equinox.supplement - some functionality presently located in OSGi plugin, but needed to be available in the environments with no OSGi (i.e. NLS)
• org.eclipse.equinox.registry - Extension registry separated from the runitme
• org.eclipse.equinox.preferences - Preferences mechanism separated from the runitme
• org.eclipse.core.jobs - Jobs mechanism separated from the runtime
• org.eclipse.core.contenttype - Content mechanism separated from the runtime

As a result, the org.eclipse.core.runtime
plugin becomes much smaller.

The change should have being transparent
to all clients. To test it, few recent nightly build were run with the
runtime source code being picked up from the equinox-incubator\runtime-split.

However, a few issues have been found
(surprise, surprise :-)).

One of the items I didn't consider was
that some build and javadoc scripts would explicitly specify classpaths.


As a result of this change, custom
scripts that had org.eclispe.core.runtime specified in the classpath need
to add one or more of the following:

• org.eclipse.equinox.common
• org.eclipse.equinox.registry
• org.eclipse.equinox.preferences
• org.eclipse.core.jobs
• org.eclipse.core.contenttype

to the classpaths.

Normal build is not affected as
the org.eclipse.core.runtime re-exports all those new plugins. If you don't
have custom scripts, then no change is necessary.

I will try to contact plugin owners
for the problems picked up by the nightly build (i.e. javadoc problems
below). 

If you know of a situation where
org.eclipse.core.runtime was specified on a class path explicitly (such
as custom build scripts?) please let me know.

Sincerely,
Oleg Besedin

Douglas Pollock <douglas.pollock@xxxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

11/19/2005 08:43 AM

Please respond to
dpollock and "Eclipse platform release engineering list."

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	Re: [platform-releng-dev] [eclipse-build]Build        N20051118-0010        (Timestamp:        200511180010):Automated JUnit testing        complete.        Test failures/errors occurred.

On Friday November 18 2005 02:16 pm, Kim Moir wrote:
> org.eclipse.team.ui
> org.eclipse.core.resources
> org.eclipse.ui.workbench
> org.eclipse.jface.text
> org.eclipse.ltk.core.refactoring
> org.eclipse.ui.forms
> org.eclipse.core.filebuffers
> org.eclipse.core.commands
> org.eclipse.core.runtime
> org.eclipse.ui.workbench.texteditor
> org.eclipse.ui.editors
> org.eclipse.ui.views
> org.eclipse.update.core
> http://download.eclipse.org/eclipse/downloads/drops/N20051118-0010/compilel
>ogs/platform.doc.isv.javadoc.txt

A lot of these look bogus.  For example:

/builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.ui.workbench/Eclipse
UI/org/eclipse/ui/IEditorInput.java:13: cannot resolve symbol
symbol  : class IAdaptable 
location: package runtime
import org.eclipse.core.runtime.IAdaptable;

In the N20051119-0010 build, there are still warnings, but now most of
them 
complain that they can't find IContentType.


Has something changed in the build itself?



d.
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev