[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Updates to the org.eclipse.osgi.framework.adaptor API and default implementation

Hi Thomas,

I think the I20040226 still works with the latest code in HEAD (I may be wrong). I've already moved up to I20040304. To run with the code out of head I checkout the following projects from CVS:

org.eclipse.core.runtime
org.eclipse.core.runtime.compatibility
org.eclipse.osgi
org.eclipse.osgi.services
org.eclipse.osgi.util
org.eclipse.update.configurator

The project org.eclipse.core.runtime.compatibility is optional but the other projects must be located in the same directory. That means when you self-host, these projects must either all come from your eclipse install or from your workspace. From your PDE launch configuration you should just select "Launch with all workspace and enabled external plug-ins" from the plug-ins tab. This should launch eclipse with the code from your workspace.

I20040226 throws an exception when starting a runtime workbench with the lasted versions of the bundles you mentioned (NPE in LocationManager.computeDefaultConfigurationLocation(LocationManager.java:152))


I tried it with the integration build you are using and that is working fine. And I got my specialized adaptor to run with your changed adaptor implementation!!! :-)

The only tricky thing was that the signature of AdaptorElementFactory.createClassLoader(..) changed slightly (the type of the last parameter). I wrote a subclass of EclipseElementFactory which overrides this method and therefore has to match the signature. ;-)

Let me know if more changes to the adaptor implementation happens and I will try again. Thanks for the help.

Best regards,
Martin





Thomas Watson





Martin Lippert <lippert@xxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx
03/06/2004 11:15 AM
Please respond to equinox-dev
To: equinox-dev@xxxxxxxxxxx
cc: Subject: Re: [equinox-dev] Updates to the org.eclipse.osgi.framework.adaptor API and default implementation



Hi,


Some code restructuring has gone on in eclipse that requires you to use
one of the latest I-Builds as your development environment when using

code

from HEAD. Unfortunately M7 is not able to selfhost the latest code

from

HEAD.  I believe most developers are using I-Build I20040226 or later.

We will continue to make some changes to the adaptor API's so I hope we
are not too much of a moving target for you.  I would really appreciate
any feedback you have though.


I have problems getting the head version of the osgi bundle to run with
I20040226. The splash screen appears and disappears after a moment. No
workbench is coming up (no log or error) messages. Some (maybe stupid)
questions:

- which bundles should I check out of the cvs head and which bundles
could I use from the I20040226 installation?

- do I need to do something special for my PDE launch configuration
instead of selecting my workspace version of the osgi bundle?

Thanks a lot for the help!

Best regards,
Martin



Thanks.

Thomas Watson





Martin Lippert <lippert@xxxxxxx>
Sent by: equinox-dev-admin@xxxxxxxxxxx
03/05/2004 10:01 AM
Please respond to equinox-dev

       To:     equinox-dev@xxxxxxxxxxx
       cc:
       Subject:        Re: [equinox-dev] Updates to the
org.eclipse.osgi.framework.adaptor API and default implementation


Hi,

I would be happy to test my load-time weaving stuff (that introduces a
spezialized adaptor) with your new implementation. (And I would, of
course, give feedback on the results.)

What is the best way to set up the environment properly? I tried to
check out the head version of several plugins (including osgi...) into
my M7 workspace, but failed to get that run. Which target (and
development) environment should I use to get your new adaptor
implementation to run?

Best regards,
Martin





Today I dropped some changes to the org.eclipse.osgi.framework.adaptor

API


and have reworked much of the DefaultAdaptor and EclipseAdaptor
implementation.  This should not effect most of the equinox development
community that are doing bundle development.  But it will effect those
that have written custom FrameworkAdaptors from scratch or
FrameworkAdaptors that extend either the DefaultAdaptor or

EclipseAdaptor.


Please get the latest code for the project org.eclipse.osgi from HEAD

if


you are developing a FrameworkAdaptor to get the latest code.

Let me know if you have any questions or problems

Thanks.

Thomas Watson






#### smime.p7s has been removed from this note on March 05, 2004 by

Thomas

Watson







#### smime.p7s has been removed from this note on March 07, 2004 by Thomas Watson
[attachment "smime.p7s" deleted by Thomas Watson/Austin/IBM]



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature