I started to refactor SimpleArtifactRepositoryFactory to use
ECFTransport instead of using URL.openStream() to load the artifacts.xml.
In my first attempt I was using ECFTransport to download artifact.xml
into a temporary file and than reading its content with
It seems that there is a difference between loading a class (from another
bundle) from the ´main´ thread and from a spawned thread while activating a
There is no difference between loading a class from the main thread or from
another thread. All calls end up in the same place.
Thanks for your help Thomas, your clue about our config.ini not requiring all
of those bundle-startups led me on the path to the solution. It turns out that
we were using the OSGi launcher and not the Equinox/Eclipse launcher and that's
why we needed to explicitly start all of those bundles in
If I was looking at this from the perspective of only RPM for the SDK, you
would likely be close enough.
bundles.txt stored in user home.
YES. I would change that to stored in users workspace or preferable
user's configuration space.
Yes, configuration space is more accurate. I just
The map file has been updated for the following Bug changes:
+ Bug 211745. [sec] Graduate signedcontent API and related services
+ Bug 211904. [launcher] Running from outside current directory causes
contents of .ini file to be ignored (FIXED)
The following projects have changed:
ECF had a milestone build last Friday 12/14, and it would be great to
update the Equinox provisioning to use the latest from ECF
filetransfer. See below for project set changes (for
org.eclipse.equinox.p2.releng) and http get URLs (for map/build files).
My understanding is that DJ is making
Hey James, this is alot of good information. Would you have a chance to
update the shared install scenarios document to highlight some of the
points? My gut feeling from reading your comments is that most of what
you suggest is do-able wrt the underlying infrastructure but the current