Thanks, I saw that go by.
Equinox was one of the early adopters of parallel class loaders during its
design and eventual inclusion in Java 7. Long ago we stopped needing any such
flags to prevent deadlock with our non-hierarchical class loaders. This should
have no impact for Eclipse
I assume the migration will include binaries also
(https://git.eclipse.org/c/equinox/rt.equinox.binaries.git/) or is that not
necessary?
Tom
From: equinox-dev on behalf of Aleksandar
Kurtakov
Sent: Wednesday, March 9, 2022 10:06 AM
To: Equinox development
The package org.osgi.service.component.annotations is not meant to be imported
by bundles. There is no need for a bundle to be wired to these packages at
runtime. The JARs the OSGi specification (working group) provides in maven
central are only meant to be used for compile time dependencies.
If all you need is a path to some resource in a bundle then there is no need for a custom header or a custom service interface. I recommend you define your own capability namespace and define a set of attributes that describe the capability for such a namespace.
For example, define a new
That is a bit of a dramatic statement that can open a can of worms. The extension registry and the Eclipse platform model with its many extension points does what it does very well. If you are developing bundles that plugin to the Eclipse platform do not "feel bad" about using the right
80420-1519.jarshould this work or do I need to explode the jar files into a folder?Am 12.04.21 um 16:17 schrieb Thomas Watson:> The dev class path entries are prepended to the value of the> Bundle-ClassPath header value. Normal delegation rules apply for the dev> class path as if they ar
The dev class path entries are prepended to the value of the Bundle-ClassPath header value. Normal delegation rules apply for the dev class path as if they are part of the bundle's Bundle-ClassPath. That roughly is the following:1) Import-Package wires, if package is imported the search
To be clear, the Eclipse IDE doesn't support x86 32-bit. Nothing in the Equinox Framework prevents you from running on x86 32-bit.
Can you run the gogo console in your environment and run the following command?inspect capability osgi.native 0
I expect output like this (note this is from my
I've certainly made fixes to this code long after Equinox has stopped using it and I don't mind maintaining fixes there when required. I do care enough to not break existing projects that are using this API. After all, I do use PDE nearly every day and we are very dependant on tycho to build.
like a rat hole to me. :-(
On 08.01.2021 16:02, Thomas Watson wrote:
You are correct, this is a rather a tricky situation. Especially because of things like org.eclipse.pde.core.plugin.IPluginModelBase.setBundleDescription(BundleDescription)
I'm not entirely sure why that is API there,
stion here to deprecate these things too?!
On 08.01.2021 15:40, Thomas Watson wrote:
I would be in favor of deprecating the API package org.eclipse.osgi.service.resolver which is contained in the Equinox Framework (org.eclipse.osgi). The framework fragment called org.eclipse.osgi.compatibility.s
I would be in favor of deprecating the API package org.eclipse.osgi.service.resolver which is contained in the Equinox Framework (org.eclipse.osgi). The framework fragment called org.eclipse.osgi.compatibility.state holds the actual implementation, which is internal. But anything needing to get
I think there is simply a miscommunication here and nothing to take offence at. Regardless we have given Ranjana more than enough information.
Tom
- Original message -From: "Sravan K Lakkimsetti" Sent by: equinox-dev-boun...@eclipse.orgTo: "Equinox development mailing list"
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=525368
Under the covers p2 uses SAT4J to implement a resolver for selecting what to install. I remember discussing with the original p2 developers the complications of the uses directive such that they could look into encoding the constraint
I would try the osgi-dev mailing list: https://mail.osgi.org/mailman/listinfo/osgi-dev
Tom
- Original message -From: Lars Vogel Sent by: equinox-dev-boun...@eclipse.orgTo: Equinox development mailing list Cc:Subject: [EXTERNAL] [equinox-dev] JAXB with Java 11 in OSGiDate: Tue, Jul 28,
Thanks again Johah,
The blame history has been properly restored to the master branch and to the osgiR8 branch using this approach. My mistake is now properly swept under the rug.
Tom
- Original message -From: "Thomas Watson" Sent by: equinox-dev-boun...@eclipse.orgTo: e
from:
$ git blame bundles/org.eclipse.osgi.tests/META-INF/MANIFEST.MF--snip--713ce018b1 (Thomas Watson 2020-03-10 16:03:39 -0500 5) Bundle-Version: 3.15.300.qualifier
to$ git blame bundles/org.eclipse.osgi.tests/META-INF/MANIFEST.MF--snip--27288b2b5b (Alexander Kurtakov 2020-03-08 14:28
to do the force push to master for me.
Sorry for the bone-headed move on my part.
Tom
- Original message -From: Thomas Watson/Austin/IBMTo: equinox-dev@eclipse.org, platform-releng-...@eclipse.orgCc:Subject: Incorrect merge of osgiR8 branch into master for rt.equinox.frameworkDate
I incorrectly merged into master a long running branch I have for OSGi R8 development in the rt.equinox.framework. I have a bug opened against the foundation asking to get a force push to master to correct things: https://bugs.eclipse.org/bugs/show_bug.cgi?id=560997
As much as I dislike a
All the source can be found in the eclipse git repositories info found at https://git.eclipse.org/c/equinox/rt.equinox.framework.git/ and https://git.eclipse.org/c/equinox/rt.equinox.bundles.git/
But for most we do publish the source JARs into maven central:
Thanks Mykola, I've done the same for the Equinkox framework and bundles jobs now.
Tom
- Original message -From: Mykola Nikishov Sent by: equinox-dev-boun...@eclipse.orgTo: equinox-dev@eclipse.orgCc:Subject: [EXTERNAL] [equinox-dev] Log Maven version in p2-master and p2-gerrit
That version is over 6 years old and was released before Java 8 was even available so it may have issues with running on the oldest supported Java available and I doubt it will work well on anything Java 9+. While I suspect it should just work for the most part on Java 8 there will be a few
The equinox jobs have been migrated over to the new infrastructure, but we are experiencing some issues with the migration. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=545352
Tom
- Original message -From: Mykola Nikishov Sent by: equinox-dev-boun...@eclipse.orgTo:
I've started the 4.11 Equinox planning page at https://wiki.eclipse.org/Equinox/Plan/4.11
Please add any major work items you plan to work on for 4.11.
Tom
- Original message -From: "Daniel Megert" Sent by: eclipse-dev-boun...@eclipse.orgTo: "General development mailing list of the
I added a comment to the bug report, we can continue the discussion there.
Tom
- Original message -From: Guillaume Dufour Sent by: equinox-dev-boun...@eclipse.orgTo: Equinox development mailing list Cc: tycho-...@eclipse.orgSubject: Re: [equinox-dev] Tycho Surefire Test fails to load
Neil and Gunner are correct. I also question the motivation to running activators in parallel. In implies some kind of design flaw because you must have some long running BundleActivators if you want to run them in parallel. You are better off investigating why you must have long running
Dictionary my be documented as obsolete, but it is not deprecated. I would not want to deprecate a spec'ed API method that takes non-deprecated types. Anyway, the discussion is happening now in the expert group.
Tom
- Original message -From: Lars Vogel Sent by:
:Subject: Re: [equinox-dev] logging jobsDate: Wed, Mar 28, 2018 9:51 AM
On Wed, Mar 28, 2018 at 10:37 AM, Thomas Watson <tjwat...@us.ibm.com> wrote:
What do you mean by runtime jobs? When I hear that in the Eclipse context I think something from org.eclipse.core.jobs.
Maybe?
But I suspec
What do you mean by runtime jobs? When I hear that in the Eclipse context I think something from org.eclipse.core.jobs. But I suspect that is not what you are asking for. Are you asking for some tracing for all background operations the framework performs? I assume you are trying to diagnose
Hi Scott,
You are correct. That package got added to Oxygen when we started using the Felix SCR implementation for our OSGI R6 Declarative Services.
Tom
- Original message -From: Scott Lewis Sent by: equinox-dev-boun...@eclipse.orgTo: Equinox development
hat matter).best,StephanOn 05.10.2017 15:12, Thomas Watson wrote:> Not sure if you are aware of the work I have done for JPMS inter-op [1]> During my prototyping of inter-op I also did try implementing what you suggest, by adapting Java 9 modules to OSGi bundles on the> fly (See [2]). I kn
ecomean OSGi bundle and at it to the target platform).But from your answer, I understand that OSGi / Equinox does currentlynot plan to simplify the consumption of the Java 9 modules. So we haveto stay with the old conversion process.Thanks again for the answer, LarsOn Wed, Oct 4, 2017 at 8:20 PM, Thomas W
Over the years Equinox has become a stable project. The last major code effort was in the Luna release when the Equinox framework was refactored to use the OSGi generic capability and requirements model along with the OSGi Resolver service. Over the past few years the list of active committers
Over the years Equinox has become a stable project. The last major code
effort was in the Luna release when the Equinox framework was refactored
to use the OSGi generic capability and requirements model along with the
OSGi Resolver service. Over the past few years the list of active
I have merged the branch we had for OSGi R7 into master for rt.equinox.framework.
I expect there may be a few compilation errors in the next build because of some places where we implement interfaces from the framework which are not intended to be implemented by client code (probably mostly
Singleton should have nothing to do with activation. Do you have a scenario to reproduce?
Tom
- Original message -From: Lars Vogel Sent by: equinox-dev-boun...@eclipse.orgTo: Equinox development mailing list Cc:Subject: [equinox-dev]
rt.equinox Committers,
This automatically generated message marks the completion of all the legal
paperwork and webmaster provisioning for Alexander Kurtakov. Alexander
Kurtakov is a new full Committer on the rt.equinox project.
Welcome!
___
equinox-dev
For awareness,
I am looking at it, but will be a bit slow while at EclipseConverge and Devoxx. Looking at the problem it seems that the resolver should find a solution pretty easily but the presence of one of the versions of org.apache.httpcomponents.httpcore_4.4.4.v20161115-1643 (there are
A 'reference' install will not copy the content of the bundle file into the framework's internal storage. Instead it will load the bundle directly out of the file URL the 'reference' URL is pointing to. Note that 'reference' URLs only support embedded 'file' URLs (not http etc.) This has
2017 6:38 AM, Thomas Watson wrote:
EventAdmin is also the RI for OSGi R6. There are no updates to EventAdmin for R7.Thanks. One follow up on EventAdmin. I've read that the Equinox EventAdmin uses a single thread for dispatch...i.e. for all topics...and it seems like that's correct given a
tatype
Sent by:equinox-dev-boun...@eclipse.org
On 1/19/2017 12:36 PM, Thomas Watson wrote:
Equinox metatype implementation continues to be the reference
implementation for OSGi and implements the very latest released
specification.
I did update the CM implementation to be CM spec versi
Equinox metatype implementation continues to be the reference
implementation for OSGi and implements the very latest released
specification.
I did update the CM implementation to be CM spec version 1.5 a long time
ago (3 years?). OSGi R6 did not update the CM spec, if I recall
correctly. The
I'm not sure I understand the scenario.
What I do know is that in the latest Equinox (since the Luna release) the
framework will eagerly flush updated or uninstalled class loaders if they
are not 'reachable' by any other in-use bundle in the framework. It
sounds to me like this may be what is
This is all getting a bit fuzzy for me because PDE is still using the old
Equinox resolver API which the framework no longer actually uses at
runtime. But if I recall correctly Require-Capability reqs are modelled
with the org.eclipse.osgi.service.resolver.GenericSpecification interface
which
I'll also state that in Equinox (and AFAIK in Felix) the PackageAdmin
implementation is not going anywhere for the foreseeable future.
Tom
From: Pascal Rapicault
To: Equinox development mailing list
Date: 12/13/2016 08:46 PM
Subject:
I think Pascal is asking how to find an installed bundle given a specific
BSN and version (range?). I suggest you take a look at the
PackageAdminImpl for the getBundles method:
And yes, it will support the latest Declarative Services version 1.3 from
the R6 specification
Tom
From: Thomas Watson/Austin/IBM@IBMUS
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 11/29/2016 07:55 AM
Subject:Re: [equinox-dev] Felix SC
Yes, that is the plan. I had hoped to get it in for M4. But have not had
time to get it in. I will look to put it in for M5. If it slips past
that though it will get more difficult to get it in.
Tom
From: Scott Lewis
To: Equinox development mailing list
I will be interested to see if you can successfully map the OSGi uses
concept into the SAT solver p2 uses. I briefly looked at that a long time
ago when we were refactoring the Equinox framework (Luna) and were
replacing the old Equinox resolver. It was far from obvious how you would
achieve
Disabling uses is usually not a good idea. I would be interested to know
why you want to do this.
To answer your question, I would not disable this in the felix
ResolverImpl directly. Instead I would disable it at a higher level in
the equinox container by hiding the uses directives on the
in properly diagnosing these issues?
Regards,
Michal
From: equinox-dev-boun...@eclipse.org <equinox-dev-boun...@eclipse.org> on
behalf of Thomas Watson <tjwat...@us.ibm.com>
Sent: Monday, October 3, 2016 2:58:25 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev]
It is hard to tell if the exceptions are issues to be concerned about
without having one as an example. It is possible that enabling debug is
just printing out some benign exception that is otherwise ignored by the
system and not logged.
Yes Equinox should easily handle 1000s of bundles being
Equinox is used in many environments where there is very long-term support
for older Java levels. So far I have needed to keep the Equinox Framework
at a Java 6 level to be able to use the latest versions in these
environments.
Unfortunately Java 6 is getting harder and harder to support
For Oxygen I plan to replace the Equinox DS implementation with the Felix
DS (SCR) implementation. See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=501950
Tom
From: Todor Boev
To: equinox-dev@eclipse.org
Date: 09/28/2016 07:31 AM
Subject:[equinox-dev]
There is a bad endless loop bug in the last I-Build that the Equinox team
is requesting a respin for. Markus has already provided a fix for bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=500225 and we are ready for
a respin.
To workaround the issue in the Install dialog ensure that the
I may be wrong, but I think the limitations are on the Eclipse console
view implementation. You may want to try posting a message to
https://dev.eclipse.org/mailman/listinfo/jdt-debug-dev to get details on
enabling that for the eclipse console.
Tom
From: Christian Schneider
You may be interested in reading an article that I wrote about
experimenting with JPMS layers and representing an OSGi framework as a
JMPS Layer [1].
Tom
[1] http://blog.osgi.org/2016/08/osgi-with-java-modules-all-way-down.html
___
equinox-dev
It depends on the launcher you are using. Here I am going to assume you
are using the Equinox launcher as-is. The thing about
FrameworkEvent.STARTED is that it is only fired when the framework has
reached its "beginning framework start-level" during the call to
Framework.start(). By default
: Thomas Watson/Austin/IBM@IBMUS
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 06/30/2016 07:51 AM
Subject:Re: [equinox-dev] Fwd: Starting a runtime Eclipse fails
with Exception in
org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of
Some bundle in your environment looks like it has no Bundle-SymbolicName.
Can you open a bug against p2. It needs a null check at
ConfigApplier.refreshPackages(ConfigApplier.java:401)
But I am curious how you got p2 to install a bundle with no
Bundle-SymbolicName. I thought that was
We just setup a nexus repo for the Equinox project but still need to setup
the process for populating it with the Equinox releases:
John Ross and I are planning to get a process going soon to get the new
repo populated.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=494491
As for the Felix
I am wondering why anything outside of core.runtime and equinox would be
using this. Shouldn't you be using one of the following to get an ILog
object?
org.eclipse.core.runtime.Plugin.getLog()
org.eclipse.core.runtime.Platform.getLog(Bundle)
In Equinox everything eventually ends up going
> From: Stephan Herrmann
> Hi Tom,
>
> Thanks for your comprehensive answer.
> Yes, we can easily agree that SynchronousLogListener is dangerous :)
>
> More questions inline ...
>
>
> Sounds promising, but ...
>
> > But be aware that nobody is going to see your logs until there is
> a
ext = null;
}
}
Tom
From: Thomas Watson/Austin/IBM@IBMUS
To: Equinox development mailing list <equinox-dev@eclipse.org>
Date: 05/16/2016 09:15 AM
Subject:Re: [equinox-dev] Safe logging from a WeavingHook?
Sent by:equinox-dev-boun...@eclipse.org
Hi
The
Hi
The Eclipse Log API (org.eclipse.core.runtime.ILog) has the unfortunate
contract that log listeners registered with it will be called
synchronously. This can cause the issues you are seeing with class
loading if we get into a circularity. In Equinox we actually have one and
only one log
You probably should open a bug and give the details on how to reproduce. A
stacktrace may also help and the error log if it exists, At this point I
don't understand what is going wrong and I am not sure what to suggest.
With the Luna release (framework org.eclipse.osgi version 3.10) there was
I am moving forward with merging the equinox committer groups.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=488579
Tom
- Forwarded by Thomas Watson/Austin/IBM on 04/06/2016 07:57 AM -
From: Thomas Watson/Austin/IBM
To: Equinox development mailing list <equinox-dev@eclipse.
Equinox will not export the annotation package (via Export-Package)
because it will lead to a bad practice of using Import-Package for these
non-runtime packages. Whatever the solution ends up being to get the
annotations on the classpath of the project, PDE must do so without
requiring the
-22 09:50 PM, Ian Bull wrote:
+1
Cheers,
Ian
On Tue, Mar 1, 2016 at 8:46 AM, Raymond Auge <raymond.a...@liferay.com>
wrote:
+1
- Ray
On Tue, Mar 1, 2016 at 10:31 AM, Thomas Watson <tjwat...@us.ibm.com>
wrote:
I have no objections to merging in p2. But I would like Pascal and other
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=481625
This was a classpath entry that optionally could be provided by a
compatibility fragment. The compatibility fragment has since been
deprecated and removed from the Eclipse project. In Neon the jar has been
removed from the
Tom Schindl is probably the best person to ask since he did the work to
get javafx working. I remember we went through a number of options before
he landed on an acceptable solution. I'm pretty sure the solution
involved some equinox specific hook to grant access to the stuff on the
org.eclipse.equinox.http has been removed and replaced by the jetty backed
implementation org.eclipse.equinox.http.jetty
Since the Juno release we no longer maintain our own web container
implementation for the OSGi Http Service implementation.
Tom
From:
To:
fix
really belongs, and makes it unnecessarily hard to do large changes such
as rolling with deprecations.
+1
On Tue, Mar 1, 2016, 5:51 AM Martin Lippert <mlipp...@gmail.com> wrote:
+1
Cheers,
-Martin
> Am 01.03.2016 um 14:49 schrieb Thomas Watson <tjwat...@us.ibm.com>:
>
>
Right now the equinox project has the following sub-projects, each with
their own committer groups
rt.equinox - parent project, no real code here, but it does contain the
website
rt.equinox.framework - where the OSGi framework and Equinox native
launcher lives
rt.equinox.bundles - where
Mickael is correct. There is no capability defined which indicates the
eclipse release name. The version dependencies are what should be used.
Tom
From: Mickael Istria
To: equinox-dev@eclipse.org
Date: 02/24/2016 03:26 AM
Subject:Re: [equinox-dev]
The website is in a git repo. See
http://git.eclipse.org/c/www.eclipse.org/equinox.git/
It needs a major scrub. It would be great if you (or anyone else) would
want to contribute to fixing up the website.
Thanks.
Tom
From: "Carlos S."
To:
Classes found in the required bundles always take precedence over classes
contained in the local bundle. This is also true if you require the
system.bundle.
Tom
From: Lars Vogel
To: Equinox development mailing list
Date:
I think this is probably a bug. Can you open one? I suspect most folks
that use shared configurations are using the equinox launcher which should
read the parent config.ini before even invoking the framework. But here
you are not using the equinox launcher, right?
Tom
From: Cristiano
Is there much interest in the osgi application service? It seemed
interesting at the time it was spec'ed and it fit OK into the Eclipse
application story (but not perfectly). Since then the specification has
had no updates and I am not really aware of it being used much outside of
the
You should be able to set the osgi.sharedConfiguration.area property.
java -Dosgi.sharedConfiguration.area=/etc/myapp -jar org.eclipse.osgi.jar
-configuration /var/lib/myapp/
If I recall correctly that should treat the shared configuration directory
as read-only and load the config.ini from
The branch used for Kepler is R3_9_maintenance (
http://git.eclipse.org/c/equinox/rt.equinox.framework.git/log/?h=R3_9_maintenance
). The tag used for Kepler SR1 release is R4_3_1
If you already cloned the git repo then you can switch branches with:
git fetch --prune origin
git checkout --track
No the intention is not to replace the existing Equinox framework
implementation for the IDE.
Tom
From: Lars Vogel
To: Equinox development mailing list
Date: 11/20/2015 10:23 AM
Subject:[equinox-dev] Concierge and the IDE?
This sounds pretty strange. You say RegionManager is not able to see the
initial bundles? What version of regions and equinox are you using? I
assume the latest from Mars? I ask because the Mars version of regions is
a system.bundle fragment and ends up using the system.bundle BundleContext
Unfortunately the eclipse extension registry assumes a flat space for
bundles and depends on the bundles providing extensions to be singletons.
With that in mind the only way I can see this working is if the equinox
extension registry is installed into each isolated region such that each
rt.equinox.bundles Committers,
This automatically generated message marks the completion of all the legal
paperwork and webmaster provisioning for Stefan Xenos. Stefan Xenos is a
new full Committer on the rt.equinox.bundles project.
Welcome!
___
ILog has been around for a very long time, before OSGi as a runtime in
Eclipse I think. So its access is a bit static. If you have motivation
to access it in an 'OSGi way' then I recommend you enhance the eclipse
platform to register a ServiceFactory that bundles can use. The
ServiceFactory
bjects, should be removed from the E4 application
model, if the contributing bundle is not available any more.
Thomas Watson suggested this solution
https://bugs.eclipse.org/bugs/show_bug.cgi?id=445663#c4, which
unfortunately causes the bundles to load.
This is undesired and therefore this patch ha
I have some issues with both examples you gave. For the code that uses
ServiceTracker it will end up creating a ServiceTracker and never closing
it which will leave a ServiceListener leaked (registered) with the
framework for the lifetime of the active bundle. Once the bundle is
stopped the
That is a great question. I don't see why the path is restricted like it is. Perhaps you can open a bug and provide a contribution as well as tests that use a wider range of characters.
Tom
- Original message -From: Nikolis Galerakis Sent by:
From: Scott Lewis sle...@composent.com
To: equinox-dev@eclipse.org
Date: 07/20/2015 12:56 PM
Subject:Re: [equinox-dev] Getting equinox artifacts using maven
Sent by:equinox-dev-boun...@eclipse.org
On 7/20/2015 5:39 AM, Thomas Watson wrote:
I think it would be great if we
If I recall correctly the orbit gogo org.apache.felix.gogo.shell bundle
has a custom gosh_profile file in it. But I'm not sure what it does
special other than make the prompt use osgi instead of g!
Tom
From: Benson Margulies ben...@basistech.com
To: Equinox development mailing list
Neil is correct and I see you understand that. But to answer your
original question Equinox (org.eclipse.osgi) framework at version 3.10
implements the OSGi R6 Core specification.
Tom
From: Benson Margulies ben...@basistech.com
To: Equinox development mailing list
What version of Equinox are you using? Can you give the example of the
error message equinox does give you?
Tom
From: Benson Margulies ben...@basistech.com
To: equinox-dev@eclipse.org
Date: 07/09/2015 12:31 PM
Subject:[equinox-dev] Can I get logging corresponding to 'diag'?
, Thomas Watson tjwat...@us.ibm.com wrote:
What version of Equinox are you using? Can you give the example of the
error message equinox does give you?
Tom
I'm embarrassed to report that I've misplaced the log. I can, however,
try to surround the question, as follows.
I am using, in Maven terms
pretty minimal.
On Thu, Jul 9, 2015 at 9:48 PM, Thomas Watson tjwat...@us.ibm.com wrote:
Perhaps the Felix implementation of Bundle.toString displays resolution
results?
Tom
From:Benson Margulies ben...@basistech.com
To:Equinox development mailing list equinox-dev
The authorization support in Equinox was provisional and got removed as
part of the Luna (Equinox 4.3) release. It seems the documentation did
not make it clear that this was provisional and also did not remove the
authorization option from the docs.
With that said, you should be able to
org.eclipse.equinox.coordinator_1.3.100.v20150410-1453 is the expected
version for Mars. When I look at all the features contained in the
Equinox Target Components feature they refer to this version of the
coordinator. What if you create a new target and install the Equinox
Components into
So I got some questions:
- When is the next planned release of the equinox framework that would
contain the new resolver sources?
Our Mars Equinox release (version 4.5) is eminent (June 25th). The last
felix resolver fix that will go into this release of Equinox is:
In Mars M6 a fix [1] went into Equinox that allows an Equinox extension
hook implementation to return resource URLs that use a different protocol
than the built-in bundleresource protocol. For example, Virgo has the
need to return the VM built-in jar or file URLs in some scenarios. While
You can find the region bundle in the equinox SDK for Luna at
http://download.eclipse.org/equinox/drops/R-LunaSR2-201502041700/download.php?dropFile=equinox-SDK-LunaSR2.zip
The latest available builds for the upcoming Mars release is
1 - 100 of 796 matches
Mail list logo