ed.
An integration by C of both A and B could get a MANIFEST.MF warning
diagnostic that no mutually compatible version of Guava is available.
A launch of C should get a run-time failure because Guava 17 is not
suitable, and a diagnostic recommending installation of Guava 15 to
solve the prob
a compile
time version failure because A and B have no overlap; an integrator's
bug. Rarely it may occur at run-time if no Guava version from the
overlap is available, a user's bug. Both are sensible, diagnosable and
fixable leaving Eclipse as a good flexible integration platform.
Re
e Recommenders/Mylyn interacted with 11,12,15
Luna RC4 fudge: only one version of Guava to make an unpredictable
choice from.
Mars nightmare: someone introduces a second Guava version.
Regards
Ed Willink
On 25/03/2015 09:30, Andreas Sewe wrote:
Hi Ed, hi Wayne,
See https://b
went to 3.9.1, but Mars gets fixed elsewhere so
there really is no change and 3.9.0 might seem ok. Clearly it isn't. It
should be 3.9.100 until a real change comes along to make it 3.10.0.
Regards
Ed Willink
___
cross-project-issue
think we should all aim to move in I-builds
immediately following M6.
There may be a maintenance issue. e.g. Xtext 2.8.0 is out,so moving to
Guava 18 might force a 2.9.0.
I feel that barely a day before M6 is too late to request this.
Regards
Ed Willink
On 20/03/2015 21:34
before M6 to avoid problems for headless users.
Regards
Ed Willink
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=450783
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=461634
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=462431
. (The
only 1.7 is the filesystem.java7 bundle.)
Therefore IMHO this change should have been announced:
a) because it was a change to the platform project plan
b) because it clearly has an impact on many other projects
Regards
Ed Willink
On 05/03/2015 01:02, Ian Bull wrote:
Is this
ore breaks
Java 6 support. i.e. it guarantees non-functionality on Java 6.
Regards
Ed Willink
On 04/03/2015 16:59, Doug Schaefer wrote:
Our consensus has always been to not have a consensus. Each project
moved to where they needed to be when they needed to be. Obviously the
decision
Hi
On 04/03/2015 16:31, Ed Willink wrote:
Thus OCL contributes 10 404s. EMF, Xtext, ... contribute too many to
count.
Each 404 seems to add one second to the getting contents time.
Many of the 404s are old repos with missing p2.index. The difference
between a miss and a hit makes little time
consensus is.
Regards
Ed Willink
On 04/03/2015 16:32, Konstantin Komissarchik wrote:
What is the rationale for wanting to keep BREE levels as low as
possible? Even Java 7 enters the “no further public updates” phase in
April of this year. JRE 7 users in the normal update pipeline were
nt.
The policy of making everything equally available seems also suspect. Is
it really helpful to go through the composite repos to discover 20
releases of some component? Shouldn't P2 or its index scanning look only
at the top level/most recent aggregates leaving plumbing the depths til
and announced.
Regards
Ed Willink
On 04/03/2015 14:42, Daniel Megert wrote:
Hi Ed
Yes, this was intended. We never announce BREE changes.
Dani
From: Ed Willink
To: Cross project issues
Date: 04.03.2015 15:27
Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi
Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to
Java 7 intended?
Was it announced?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery
Hi
No. Unfortunately only for PPEs.
If you roll your own Eclipse, you need to install it and I could not see
it in the SimRel repo when I last looked.
Regards
Ed Willink
On 08/02/2015 12:17, Lars Vogel wrote:
AFAIK the plug-in is active by default for everybody...
Best
orm approach of having the developer describe his
development is much more efficient.
I tend to agree with that.
Ideally! What a Utopia. Many projects struggle to raise development man
power let alone extra specialists, so a lightweight aide for the
developer(s) please.
Regards
Hi
A mishmash is certainly undesirable, but they are indirected and maybe a
style consensus might materialize. (Maybe the PMI might even help format
it).
If the PMI doesn't help, we have to introduce a new all-projects
database/HTML file.
Regards
Ed Willink
On 02/02/20
;three item' overview, perhaps the PMI could supervise a
list of overview N&N's.
Regards
Ed Willink
On 02/02/2015 10:14, Lars Vogel wrote:
Hi Marcel,
I think the correct solution would be to extend the purpose of the
Platform N&N to include newsitems from the EPP si
.
Caused by: [0.2]java.net.SocketTimeoutException: connect timed out
Any news?
Regards
Ed Willink
On 31/01/2015 18:33, Doug Schaefer wrote:
No, I think they're all broken. One I was using can't see the git repos.
Sent from my BlackBerry 10 smartphone on the Rogers netw
the rebuild test easy. We had to eliminate obsolete
practices such as mapping.ini in which the build time was incorporated
into source and so guaranteed a pseudo-change.
Regards
Ed Willink
On 08/01/2015 20:40, Chuck Bridgham wrote:
I'm posting this to cross-projects because w
evel where
there might even be integration with changing project dependencies
during a slow open.
Regards
Ed Willink
On 02/12/2014 21:07, Lars Vogel wrote:
Hi Ed,
If an editor accesses the Internet I think it should use a worker
thread to get the editor content. I have not se
bstraction further on.
Is anyone else seeing this as a problem?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this l
rhaps Eclipse GIT, and the category entries can be
unconstrained.
Worst of all are features that start "Source for ...".
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change y
specifically requests them.
Please comment on [1].
Regards
Ed Willink
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=449568
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options
uot;Basic".
Regards
Ed Willink
On 13/10/2014 05:17, Eike Stepper wrote:
Hi,
I have noticed that the former "Eclipse Standard" package has recently
been renamed to "Eclipse IDE for Eclipse Committers". Personally I
don't like the new name because it sug
sions.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
ld be nice to be able to filter further logs from that offender.
Regards
Ed Willink
On 02/09/2014 11:09, Lars Vogel wrote:
Hi,
Sometimes the Eclipse IDE freezes without providing feedback which
part of the code is responsible for the freeze. Such freezes should be
avoided, but
Hi,
QVTd will be participating in the Mars simultaneous release, with offset +3.
Current plan is to graduate to 1.0.0.
http://projects.eclipse.org/projects/modeling.mmt.qvtd/releases/1.0.0-mars
Regards
Ed Willink
___
cross
7.0.0. There are however many legacy consumers and so
the old plugins are likely to continue to be available via a separate optional
install so long as a Simultaneous Release Participant needs them.
Regards
Ed Willink
___
cross
Hi Sven
Will this make Xpand obsolete as a separate install/download? (I hope it
does.)
Regards
Ed Willink
On 19/08/2014 14:45, Sven Efftinge wrote:
Hi,
Xtext and MWE will be participating in the Mars simultaneous release, with
offset +2.
Current plan is to contribute the
raw types
other than a very few fixed by very local @suppressWarnings for
rawTypes/uncheckedCast.
Since the API is evolving, it would seem to be a good point to also
introduce @NonNull/@Nullable.
Regards
Ed Willink
___
cross-project
Hi
Sorry for the noise; looking for org.eclipse.git. org.eclipse.egit
is in Modeling EPP.
Regards
Ed Willink
On 26/06/2014 15:52, Ed Willink wrote:
Hi
Just not in the Modeling EPP where I looked
Hi
Just not in the Modeling EPP where I looked.
Regards
Ed Willink
On 26/06/2014 15:34, Mickael Istria
wrote:
On 06/26/2014 04:31 PM, Ed Willink
wrote:
Except that of course we
Hi
Except that of course we should replace CVS by GIT in at least the
EPPs and so add on a lot more MB.
Regards
Ed Willink
On 26/06/2014 10:18, Fred Bricon wrote:
+1. Alex Blewitt blogged about it 3 years ago http
Hi
It's odd. I seem to have had a fairly steady stream of Bugzilla reports.
Regards
Ed Willink
On 16/06/2014 16:16, Webmaster(Matt Ward) wrote:
I restarted the bugzilla job queue a while ago and notices seem to be
fine.
-Matt.
On 06/16/2014 08:33 AM, Jan Koehnlein wrote
Hi
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=437107 for suggestions for a future policy.
Regards
Ed Willink
On 04/06/2014 12:20, Ed Willink wrote:
Hi David
On 04/06/2014 11:48, David M
ackage directives, then
surely it could/should rewrite all the Export-Package directives to
use "uses" too?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
.
Regards
Ed Willink
On 04/06/2014 01:44, David M Williams
wrote:
Ed,
Guess you know now it's not
related
to bug 436418, given the discussion and diagnosis given there.
https://bugs.eclipse.org
ated to:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=436418
in which the Plugin registry no longer has dependents.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/m
be loaded
by the overall class loader, which may have a problem if a different
version of SomeGuavaClass is similarly loaded on behalf of some
other component.
Regards
Ed Willink
On 02/06/2014 12:51, Igor Fedorenko
wrote
ugins that
exclude the latest version in Orbit, one with and one without a
non-optional OSGI dependency.
Regards
Ed Willink
On 02/06/2014 06:07, David M Williams
wrote:
This has been
discussed before, but apparently
is still
Hi David, Martin
Thanks for adding your insights.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=435734
raised for further discussion.
Regards
Ed Willink
On 26/05/2014 01:48, Oberhuber, Martin
wrote
either my expectation or the page is at fault.
Regards
Ed Willink
On 25/05/2014 07:05, David M Williams
wrote:
Ed, I don't really
know the answer to some
of your questions (not sure I understand what que
isible by manually reading the
properties file (or perhaps using a properties file API).
Is the above analysis correct and if so how much of it is a bug in
the Features page?
Regards
Ed Willink
On 08/05/2014 15:25, David M Wil
isible' on many pages since its an attachment
to the lower edge of the browser frame.)
Regards
Ed Willink
On 23/05/2014 07:45, Stephan Herrmann wrote:
On 05/23/2014 08:15 AM, Ed Willink
wrote:
O
Hi
Wow! It was almost designed to be invisible. Very successful.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=435661 raised.
(It's equally 'invisible' on many pages since its an attachment to the
lower edge of the browser frame.)
Regards
Ed Willink
On 2
Hi
On 23/05/2014 01:43, Wayne Beaton
wrote:
At the bottom of your project's PMI page,
Which page is that? The main view, or one of the tabs such Edit? For
the Project or for the Release?
if
you are logged in as a projec
Hi
I must be dozy.
I thought the IP tool had moved from the portal to the PMI, but I
can't find it in either location.
Regards
Ed Willink
On 22/05/2014 20:36, Wayne Beaton
wrote:
Greetings
#x27;t your
report find it?
Any idea where the clever code is?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
://bugs.eclipse.org/bugs/show_bug.cgi?id=431255
to use the GIT rather than P2 repo.
Regards
Ed Willink
On 24/04/2014 18:24, David M Williams
wrote:
Just to confirm, what
Andreas said is accurate,
the "best place" to get
2092
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=432088
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/ma
problems to fix. Bug
430875 is the first from me.
Regards
Ed Willink
On 21/03/2014 14:59, Konstantin Komissarchik wrote:
Are you talking about separate update site with java 8 patches for kepler
or full-blown release?
My preference is for a full release. If that doesn't h
Hi
Problems and solutions regarding class loader conflicts between Guava
versions are being discussed on
https://bugs.eclipse.org/bugs/show_bug.cgi?id=427862#c18
Comment 18 contains the latest bad scenario.
If you use Guava you should follow this bug.
Regards
Ed Willink
ot; source="false" mutable="false">
...
...
Regards
Ed Willink
On 25/01/2014 20:13, Ed Willink wrote:
Hi Eike
As a result of UML moving to 5.0.0, OCL has to too.
However there is no 5.0.0 milestone build till Monday. If you want a
5.0.0 now use the interim repo. Same probab
anticipation. But
there are many rubbish repos around so at most I would expect a warning.
I could back out the 5.0.0 aggregation, but then you'll get 4.2.0 which
will probably give you a different load of conflicts.
Regards
Ed Willink
On 25/01/2014 19:38, Eike Stepper
Hi Mikael
Surely the lack of visibility of HIPPs contradicts our normal Eclipse
policies of openness, so all HIPPs should have anonymous read access
unless specifically requested (and justified) otherwise?
Regards
Ed Willink
On 09/01/2014 08:11, Mikaël Barbero wrote:
Hi all
HI
Thanks Michael
+1
I certainly want my OCL/QVTd HIPP to be accessible and have been
inconvenienced by not being able to access other HIPPs.
Regards
Ed Willink
On 09/01/2014 08:11, Mikaël Barbero wrote:
Hi all,
I often struggle to build (or setup a CI build for) eclipse
will appear here:
https://projects.eclipse.org/projects/modeling.mdt.ocl/releases/5.0.0
The changes will obviously not occur in M4 and not until UML2 has
reversioned, so probably in M5.
Regards
Ed Willink
On 19/12/2013 00:21, Kenn Hussey
.
Perhaps we should require that any API evolution since a milestone is
made available in an I-build by -4 and that there is a temporary API
freeze from -4 to +4. Projects could then happily build in any order up
to four days early.
Regards
Ed Willink
On 19/12/2013 16:51, Doug
Hi Laurent
A long time ago GNU Java was the almost unuseable
default for vanilla Unix systems.
Have you perhaps just switched to a
new unconfigured platform such as a HIPP where the defaults are
different?
Regards
Ed Willink
On 17.12.2013 10:33, Laurent
Goubet wrote:
>
Hi David
Yes. I wrote 'optional', so it is obviously not Core.
Regards
Ed Willink
On 16/12/2013 07:17, David M Williams wrote:
I'm not sure if I should laugh, or cry?
If they are true examples, those example components could just be
omitted without loss of cor
Hi
There is a workaround for 'incubation' within mature projects.
New optional experimental functionality may be shipped in examples plugins.
Regards
Ed Willink
On 16/12/2013 04:06, Igor Fedorenko wrote:
Hello,
I just pushed updated version of m2e 1.5 plan.xml
Hi
The Eclipse QVTd (Query/View/Transformation declarative) project will
particpate in the Eclipse Luna simultaneous release with an offset of +3.
Release record
https://projects.eclipse.org/projects/modeling.mmt.qvtd/releases/0.11.0.
Regards
Ed Willink
Hi
Still seems to be hung.
How long do we need to hang in there for builds to proceed that cannot
proceed because of Hudson problems?
Regards
Ed Willink
On 23/10/2013 21:24, Denis Roy wrote:
Yep, but it's running eight builds right now, so we don't want to
restart
ets are great.
Regards
Ed Willink
On 22/10/2013 15:35, Sebastian Zarnekow
wrote:
Hi Ed,
Just because I'm curious:
>> However you may choose to follow my example of
keeping all non-text functionality in
Regards
Ed Willink
On 22/10/2013 14:50, Doug Schaefer
wrote:
Xtend is a Java language extension, no? I'm talking about a
template engine that we use in the new project wizard to
instantiate code templates based on various
Hi
Hudson seems unable to accept web connections. Anyone else able to connect?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project
entirety to Bugzilla/GIT as if the action
had happened there in the first place.
Regards
Ed Willink
On 04.10.2013 15:38, Shawn Pearce wrote:
On Fri, Oct 4, 2013 at 12:00 PM, Ian Bull
wrote:
I really like the flow that Gerrit provides. Pushing commits is
easier than
creating patchs and
ll be available in staging soon?
Regards
Ed Willink
On
02.10.2013 16:45, Matthias Sohn wrote:
> I was struggling to download
our updated documentation from the wiki to
> include it into 3.1.0
hence the final JGit / EGit 3.1.0 takes more time than
> I expected. I
think it will take me 2
contribution
For Luna, we propose a full contribution at +1 relying on latest N/I
builds of +2 dependencies.
Occasionally a 'no-change' +3 re-contribution may be necessary to
accommodate incompatible late changes in +2 dependencies.
Regards
Hi
Nice idea, but isn't the extension point a perfect target for hostile
attacks?
I'm pretty sure that I will disable it as vigorously as possible on my
installations.
Regards
Ed Willink
On 05/09/2013 01:14, Igor Fedorenko wrote:
As you may or may not know,
Hi
I must be very dense. Where does it say "The platform requires Java 6".
Regards
Ed Willink
On 03/09/2013 17:19, John Arthorne
wrote:
I can't think of any
way to be clearer
is updated with each plan revision, but as
long as
they are within the scope of the current list of reference
platforms they
are not generally announced individually.
John
From:
Ed Willink
gards
Ed Willink
On 03/09/2013 13:51, David M Williams
wrote:
I probably should
have mentioned, there
are several bugs we are still trying to work through, where the
Tycho/Maven
build picks a different "compiler level" than t
Hi Szymon
Your list omits the 'culprit'.
It is org.eclipse.osgi.util.NLS that is now Java 6 putting paid to all
attempts at internationalization with Java 5.
Regards
Ed Willink
On 02/09/2013 16:41, Szymon Ptaszkiewicz wrote:
See
http://www.eclipse.org/projects/projec
clearly still good to
go for 1.5. It's the platform that causes a surprise.
Regards
Ed Willink
On 02/09/2013 16:34, David M Williams
wrote:
> So it seems that
the Platform no longer
supports Java 5.
change?
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Hi
I haven't had a message since the 30th, and I suspect the last few
hours may have been intermittent. I noticed not getting one but then
got others.
Regards
Ed Willink
On 02/09/2013 14:23, Thomas Watson
tor ensure that the swipe is well directed
Announce the activity
Announce availability of an alpha branch build
Let the GSoC participant address the impact on a major client e.g.
EMF/GEF/
Announce availability of a beta branch build
Assess overall community reaction
Regards
no
reason why an optional JFace update shouldn't be made available, apart
from the problem that every downstream project might be broken.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclips
I feel that there should be an announcement on this list of the
development branch name/build so that early adopters may try it out
before M3.
Regards
Ed Willink
___
cross-project-issues-dev mailing lis
uckmnister build.properties
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Hi
You must be very lucky and grateful that the rest of us are doing your
work for you.
I find it essential to build against the nightly repositories of my
dependencies in order to be able to react to their more 'innovative'
changes.
Regards
Ed Willink
On 21/08/
is important (David: we need a SimRel report)
about.ini ???
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
very obvious
benefit.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
A few other actions give Bad Gateway or Form expected.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
HI
I missed this decision too and although it inconveniences me for SR1, I
welcome it.
Arguably SR0 has the stronger constraint of the M6 API freeze and the M7
Feature freeze. I hope these will now become meaningful.
Regards
Ed Willink
On 15/08/2013 08:02, Igor Fedorenko
+1
The vanilla Welcome page is pretty empty. It could be rearranged so
that the Welcome and Customization Wizard teaser appeared together.
Regards
Ed Willink
On 30/07/2013 10:56, Mickael Istria
wrote:
On 07
capabilities?
And while I'm moaning, how do I get rid of the irritating Quick
Access box that I don't understand but which makes my toolbars wider
than my screen?
Regards
Ed Willink
On 15/07/2013 18:11, David M Williams
wrote:
r than each user.
Perhaps an extension to API tooling can validate that
- Import Plugin with Sources will inherit determinate settings
independent of the workspace
- Checkout Plugin from CM will inherit determinate settings
independent of the workspace
- multiply inherit
be looking for a way to provide it.
Regards
Ed Willink
On 12/07/2013 18:57, Ed Merks wrote:
Igor,
I think it's even stronger than that. In the end, WONTFIX shouldn't
mean "I don't have time or I don't feel like it" but rather "it's
working as des
Hi
Get a committer from a related but independent project to review the
Bugzilla discussion to form a less prejudiced on view on whether the
WONTFIX is justified.
Regards
Ed Willink
On 12/07/2013 17:25, Doug Schaefer
wrote
compiled classes should be made (e.g. load
them all?), to verify that dependencies in the repository are
compatible with those used at compile time.
That's what the smoke test should do. Activate enough classes from
enough places to demonstrate no CNFEs.
Regards
Ed Wi
missing
dependencies.
For instance for OCL, I already have tests that do a minimal amount of
editor liveness testing on an example project, which gives me some
confidence that Xtext is still there in a useable fashion.
Regards
Ed Willink
On 04/07/2013 10:25, Pascal Rapicault wrote
those fixes available individually.
Regards
Ed Willink
On 03/07/2013 18:30, Jesse McConnell
wrote:
LTS currently relies upon the existence of a simultaneous
release as
ng up. I
would be amazed if P2 could sort out the anarchy.
So the users will wait a long time, get given an irritating please
confirm this magic solution that excludes your favourite product
dialog.
Eclipse will become a laughing stock.
Regards
lease.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
find it quite
amazing that anyone could even think of starting Kepler with a
second maintenance release. Surely such maintenance releases could
only be appropriate for inactive mature projects?]
Regards
Ed Willink
On 27/06/2013 20
Hi Ed
I am trying to understand what if any release rigour exists in the
Eclipse release policies; indeed if there are any policies at all.
There is clearly a large discrepancy between my expectation and what I
observe in practice.
Regards
Ed Willink
On 27/06/2013 18:50, Ed
ither 2.4.2a or 2.4.3.
Regards
Ed Willink
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
301 - 400 of 499 matches
Mail list logo
