The Equinox Framework and a some of the other core services provided by the
Equinox project have long supported the J2ME Foundation profile. As the
rest of the Java community moved on we spent a fair amount of time figuring
out how to continue our support of the J2ME profiles. Even when OSGi
is mandated by
the servlet 3.0 api...
or is that just for components using the http bits
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Mon, Jan 23, 2012 at 08:35, Thomas Watson tjwat...@us.ibm.com wrote:
The Equinox Framework and a some of the other core services provided by
the
Equinox
Sorry for the late warning on this. Any one that owns a framework
extension (a fragment of the org.eclipse.osgi bundle) pay close attention.
I hope this very small set of folks.
We had a bug opened late last night
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=369880) that prevents
framework
This should have little or no impact on projects outside of Equinox, but
thought I should mention this just in case. If your project uses any of
the types introduced in the new package org.osgi.framework.resource then
please pay attention.
The org.osgi.framework.resource package was introduced
Same for me. Although DJ in Ottawa says he can access bugzilla, but e-mail
appears to be busted. He has sent a mail to the webmaster.
Tom
From: Glyn Normington gnorming...@vmware.com
I don't know anything about why gemini.jpa or gef3d are getting added to
the repo, but this made me think about your question:
If these bundles are in the repository, shouldn't the owning projects be
Juno particpants?
I don't know the correct answer, but it strikes me as odd that we allow
I know that jetty is NOT an oversight in case that is one your were
wondering about.
Tom
From: Wayne Beaton wa...@eclipse.org
To: Cross project issues cross-project-issues-dev@eclipse.org,
Date: 01/08/2013 03:17 PM
Subject:[cross-project-issues-dev] Some Juno participants
Also using Import-Package allows for provider substitution. You don't
really know who the provider of the package dependency is by looking at a
bundle manifest in isolation.
Tom
From: Wayne Beaton wa...@eclipse.org
To: cross-project-issues-dev@eclipse.org,
Date: 05/17/2013 02:06 PM
We are well into M1 now for Luna. I thought I would take some time to
announce the efforts we have been making to improve the Equinox Core
Framework implementation for the Luna release. As you may know from
previous posts I have made to the equinox-dev mailing list, we have been
working in a
to try
building with Luna platform. I expect lots of surprised and angry reactions
in about a week.
Thanks,
- Konstantin
From: equinox-dev-boun...@eclipse.org [
mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson
Sent: Friday, August 09, 2013 8:53 AM
To: Equinox development mailing
Sorry for not communicating this aspect of the Equinox Framework changes in
Luna. Obviously we need to spell out the VM requirements clearly for the
Equinox framework being included in Luna. the NLS class is part of the
Equinox framework which has moved up to requiring Java 6.
Sorry for the
It has come to my attention that some bundles in eclipse appear to be using
interim headers and attributes that never made it into a final OSGi
specification. For Luna the Equinox framework no longer supports these
interim headers [1]. This seemed like a relatively safe change since we
assumed
This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=432485
But that should have been fixed in M7. I am curious if launching with
-clean fixes the issue. I would start with a bug against Equinox Framework
if it is what I suspect (somehow the framework is not forcing a refresh of
the
Sadly I did launch with –clean and it didn’t help.
Since it should be fixed in M7, we’ll try to reproduce on another machine
to make sure it is not my environment.
From: cross-project-issues-dev-boun...@eclipse.org [
mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Thomas
Watson
Sent
help.
Since it should be fixed in M7, we’ll try to reproduce on another machine
to make sure it is not my environment.
From: cross-project-issues-dev-boun...@eclipse.org [
mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Thomas
Watson
Sent: Thursday, June 05, 2014 3:07 PM
To: Cross
with java 6 cannot
recover
Sent by:cross-project-issues-dev-boun...@eclipse.org
Thomas,
I think I managed to find reproducable steps, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436758
Marc-Andre
On 14-06-05 04:54 PM, Thomas Watson wrote:
I just tried and could
That looks to be https://bugs.eclipse.org/bugs/show_bug.cgi?id=435888
Tom
From: Andreas Sewe andreas.s...@codetrails.com
To: cross-project-issues-dev@eclipse.org
Date: 06/06/2014 11:13 AM
Subject:[cross-project-issues-dev] Switch from Luna RC2 to RC3 fails
all
This sounds similar to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436073
There have been some changes to Equinox for SR1 dealing with system
properties. I am wondering somehow the system property
osgi.framework.useSystemProperties=true is being set before invoking the
framework from the
Konstantin
I put a fix into master for the 4.5 Eclipse I-Build that should happen
today (we need to respin for another issue). Would you be able to test
with this I-Build once it is done to see if it fixes the issue? Then we
can consider backporting to Luna.
Tom
From: Thomas Watson
on a stand-alone repro today.
- Konstantin
From: cross-project-issues-dev-boun...@eclipse.org [
mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Thomas
Watson
Sent: Tuesday, September 09, 2014 6:41 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Apparent Luna
I realized Equinox never announced. Lets make it official.
Equinox will be participating in the Mars simultaneous release with an
offset of +0
The 4.5 version will be contributed:
https://projects.eclipse.org/projects/rt.equinox/releases/4.5.0-mars
Tom
I have not heard of any other reporters of this. I got it hit with it
again recently and wanted to make others aware while testing M3. If your
installation contains multiple versions of the apache http client then you
could be hit by https://bugs.eclipse.org/bugs/show_bug.cgi?id=447993
My
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
Markus Keller wrote up an nice summary of what consumers should do to fix
any warnings that may be caused by this change at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
Here is a copy of the recommendations if you are going
If you really cannot move up to at least the Juno release then the 2
following options area available:
1) remove the signatures from the jars and place them on your own update
sight to install from ... or
2) patch equinox (org.eclipse.osgi) with
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
eeling that Wayne would wish I would
have reminded everyone to create a release record, to go along with your
announcements. :)
I am lucky and never have ... but appears the "how to" instructions have
moved to
https://www.eclipse.org/projects/handbook/#pmi-releases
Thanks,
Fro
Not sure you noticed but Equinox only declared for Neon just now. Would
have been interesting to see what happens if you disabled Equinox.
Tom
From: David M Williams/Raleigh/IBM@IBMUS
To: cross-project-issues-dev@eclipse.org
Date: 10/21/2015 09:15 AM
Subject:
>
> I think this is also something, which should be fixed directly in
> the code, which reads or parses the /configuration/org.eclipse.osgi/
> framework.info.{x} file.
>
> Regards,
>
> Simon
>
The OSGi framework is behaving exactly the way you told it to. There is
no bug in the framework
I think the fix in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478054 is
incorrect. I added a comment to the defect with the details.
Tom
From: Etienne Studer
To: Cross project issues
Date: 09/22/2015 12:08 PM
Subject:
One thing to note is that Java 8 is already supported for WebShere
Application Server Liberty. Also, the statement of general direction from
IBM is that IBM intends to support Java 8 for WebSphere Application Server
- Classic [1]
I would imagine by the time Neon is released in June and used
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=491565
The org.eclipse.equinox.log implementation and API has been included in
the Equinox framework since the Indigo release. As such the old
org.eclipse.equinox.log has been untouched and not maintained over the
years. For Neon we are
Same for me.
Tom
From: Pascal Rapicault
To: Webmaster , Cross project issues
Date: 08/16/2016 07:30 AM
Subject:[cross-project-issues-dev] git.eclipse.org not reachable
Sent by:
Equinox will be participating in the Neon Simultaneous release with an
offset 0.
The planned release is 4.7.0.
Tom
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your
.7 seems to be right though
Von: cross-project-issues-dev-boun...@eclipse.org
<cross-project-issues-dev-boun...@eclipse.org> im Auftrag von Thomas
Watson <tjwat...@us.ibm.com>
Gesendet: Dienstag, 4. Oktober 2016 23:19
An: Cross project issues
Betreff: [cross-project-issues-dev
> From: Ed Merks
> During testing I also see this stack trace in my Error log:
>
> java.lang.reflect.InaccessibleObjectException: Unable to make field
> private static volatile java.net.Authenticator
> java.net.Authenticator.theAuthenticator accessible: module java.base
>
Hi,
Equinox will participate in the Photon release with version 4.8.0 at offset 0.
The release record is here: https://projects.eclipse.org/projects/rt.equinox/releases/4.8.0-photon
Tom
___
cross-project-issues-dev mailing list
Equinox will contribute to Oxygen.1a for the following bugs:
Bug 520636 - Make sure Eclipse starts with Java 9
Bug 522313 - Remove loop used to acquire the bundle id lock on bundle installation
Tom
___
cross-project-issues-dev mailing list
I've been getting 502 errors access the eclipse servers, bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=559928 opened.
Tom
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve
FYI - I'm seeing odd behavior for recently opened bugzilla issues that do not allow them to be read without being logged into bugzilla. I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=566622
NOTE: You must be logged into bugzilla to read the details of the bug!!
Tom
+1
Tom
- Original message -From: Martin Lippert Sent by: cross-project-issues-dev-boun...@eclipse.orgTo: Cross project issues Cc:Subject: [EXTERNAL] Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09Date: Wed, Sep 2, 2020 4:13 AM +1
Cheers
Martin
Am 28.08.2020 um
2020-09-24 12:07 p.m., Thomas Watson wrote:
Yes, p2 verifies the signatures and content of the JARs to confirm it hasn't been tampered with before installing the JAR. At runtime the verification of JARs is not enabled by default. Otherwise what you did would have resulted in a runtime
Yes, p2 verifies the signatures and content of the JARs to confirm it hasn't been tampered with before installing the JAR. At runtime the verification of JARs is not enabled by default. Otherwise what you did would have resulted in a runtime exception for the class you changed.
Tom
-
I don't think ecj itself requires equinox.common.
Tom
- Original message -From: Christian Dietrich Sent by: "cross-project-issues-dev" To: cross-project-issues-dev@eclipse.orgCc:Subject: [EXTERNAL] Re: [cross-project-issues-dev] Move JDT to Java 11Date: Wed, Jun 16, 2021 8:35 AM
as
om/eclipse/jetty.project/issues
cheers,
Jesse
--jesse mcconnelljesse.mcconn...@gmail.com
On Thu, Jun 3, 2021 at 7:30 AM Thomas Watson <tjwat...@us.ibm.com> wrote:
The issue is now the Import-Package for the jetty bundles have a non-optional import on the slf4j package with a range forc
The issue is now the Import-Package for the jetty bundles have a non-optional import on the slf4j package with a range forcing it to be 2.0:
For example:https://search.maven.org/artifact/org.eclipse.jetty/jetty-io/10.0.2/jar
Has this import:
org.slf4j;version="[2.0.0,3)"
If this either
I'm sure Ed is just being cute with the remark about JDT being perfect. But in
case anyone missed it: the Eclipse project moved to Github. JDT issues should
be opened there against the proper repository: https://github.com/eclipse-jdt
We still have much to work out to get our issue reporting
It is unfortunate that we are forbidden from using the Eclipse OpenJ9 project
Java releases. I am sure they will have a ppc64le variant when they release
Java 21.
Tom
From: cross-project-issues-dev
on behalf of Ed Merks via cross-project-issues-dev
Sent:
47 matches
Mail list logo