[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Thomas Watson wrote:
There currently is no implementation of OBR. If you look earlier in
this thread you will see talk of investigating an OBR repository
adaptor for p2. Thomas Hallgren showed interest in implementing such a
repository adaptor. Thomas, do you have any interest in
doing/contributing this work to Equinox? Perhaps start in the incubator?
For your Filter issue. I would open a bug against the apache version
of OBR. It should not be using the framework Filter implementation to
construct Filter objects.
Well, it's the only implementation we have. :-)
I suppose we could make a strict/non-strict flag or something...
-> richard
Tom
Inactive hide details for Peter Kriens ---01/22/2008 02:09:46 AM---RFC
112 is not a standard, but please note that > and < are Peter Kriens
---01/22/2008 02:09:46 AM---RFC 112 is not a standard, but please note
that > and < are specifically allowed. Rewriting bindex will not fix
the problem if
From:
Peter Kriens <Peter.Kriens@xxxxxxxxx>
To:
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date:
01/22/2008 02:09 AM
Subject:
Re: [equinox-dev] OBR
------------------------------------------------------------------------
RFC 112 is not a standard, but please note that > and < are
specifically allowed. Rewriting bindex will not fix the problem if you
want to interoperate, you have to use another filter impl to achieve that.
Kind regards,
Peter Kriens
On 21 jan 2008, at 16:18, ChangWoo Jung wrote:
I have been using OBR implementation from Apache Felix and
it uses "BundleContext#createFilter" to create the filter
which throws the exception in the equinox framework at the
end. So if I don't modify the bindex not to generate the <
or > operator, the repo xml can't be digested in the OBR
bundle for bundle resolution in the framework.
By the way, do we also have OBR implementation from equinox?
Sincerely,
ChangWoo Jung
From: Thomas Watson <_tjwatson@xxxxxx.com_
<mailto:tjwatson@xxxxxxxxxx>>
To: Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>
Date: 01/21/2008 11:44 PM
Subject: Re: [equinox-dev] OBR
------------------------------------------------------------------------
Peter, who parses the filter? If OBR uses a different
syntax from the Framework spec then the
FrameworkUtil#createFilter or BundleContext#createFilter
cannot be used. Who is throwing the syntax error in this
case? The Equinox Framework implementation of the OBR
implementation?
Tom
<mime-attachment.gif>Peter Kriens ---01/21/2008 02:27:18
AM---This is not really true. The OSGi filter and the OBR
filter are not required to be the same. RFC 112
specifically allows the >
<mime-attachment.gif>
From: <mime-attachment.gif>
Peter Kriens <_Peter.Kriens@aQute.biz_
<mailto:Peter.Kriens@xxxxxxxxx>>
<mime-attachment.gif>
To: <mime-attachment.gif>
BJ Hargrave/Austin/IBM@IBMUS
<mime-attachment.gif>
Cc: <mime-attachment.gif>
Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>
<mime-attachment.gif>
Date: <mime-attachment.gif>
01/21/2008 02:27 AM
<mime-attachment.gif>
Subject: <mime-attachment.gif>
Re: [equinox-dev] OBR
------------------------------------------------------------------------
This is not really true. The OSGi filter and the OBR
filter are not required to be the same. RFC 112
specifically allows the > and < (as well as some other
operators).
Kind regards,
Peter Kriens
On 20 jan 2008, at 15:51, BJ Hargrave wrote:
This may be a problem in the tool (from OSGi) which
generates the xml. OSGi recently decide to add < and > to
the set of filter operators. But this is not in the 4.1
spec. It will be in a future spec. So the tool which
generates the xml should not use the new operators.
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance_
__hargrave@xxxxxx.com_ <mailto:hargrave@xxxxxxxxxx>
Office: +1 386 848 1781 Mobile: +1 386 848 3788
------------------------------------------------------------------------
----- Original Message -----*
From: *ChangWoo Jung [_jungcw@xxxxxx.com_
<mailto:jungcw@xxxxxxxxxx>]*
Sent: *01/20/2008 07:43 AM*
To: *Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>*
Cc: *Peter Kriens <_Peter.Kriens@aQute.biz_
<mailto:Peter.Kriens@xxxxxxxxx>>*
Subject: *Re: [equinox-dev] OBR
I guess I found little bug in the generated OBR repo
(_http://download.eclipse.org/releases/europa/repository.zip_)
The generated filter seems to be incorrect which throws
exception in the runtime.
For example, Jetty Http Service
(org.eclipse.equinox.http.jetty), has dependency on
"javax.servlet" which is shown as
Import-Package: javax.servlet;version="[2.4.0,2.5.0)" in
the manifest.
It turns out be generated like below, (which seems to be
incorrect), so it throws "InvalidSyntaxException" when
equinox tries to create the filter upon that.
<require extend='false'
filter='(&(package=javax.servlet)(version>=2.4.0)(version<2.5.0))'
multiple='false' name='package' optional='false'>
Import package javax.servlet ;version=2.4.0
</require>
I guess there is minor bug on creating filter and after
applying my private fix it seems to be working.
wrong:
filter='(&(package=javax.servlet)(version>=2.4.0)(version<2.5.0))'
correct:
filter='(&(package=javax.servlet)(&(version>=2.4.0)(&(version!=2.5.0)(version<=2.5.0))))'
Which component will be the right place to report a bug
against that i can attach my fix there as well? Any pointers?
Thanks.
Sincerely,
ChangWoo Jung
From: Jeff McAffer <_Jeff_McAffer@xxxxxx.com_
<mailto:Jeff_McAffer@xxxxxxxxxx>>
To: Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>
Date: 01/12/2008 12:43 AM
Subject: Re: [equinox-dev] OBR
------------------------------------------------------------------------
We currently do host an OBR repo with the major releases.
Don't remember the URL but the required repository.xml/zip
file is there for Callisto and Europa. The OBR client code
may be interesting but our strategic direction is p2. For
the most part p2 has (or can be made to have) the same
functionality as the OBR client but goes further towards
solving the wider range of problems we see in the Eclipse
provisioning space.
I am all for supporting the use of OBR repositories in the
sense that some people will make their function available
that way. Given the p2 work however, it would be more
interesting (to me at least) to write an OBR repository
adaptor for p2 than to use the OBR api. Further, I hope
that eclipse projects will feel comfortable making their
content available as p2 repositories so that the Eclipse
user community is not put in a position of having to get
many different provisioning clients.
In short, we in p2 would very much like to have your
interaction and participation in making a provisioning
solution that solves your needs.
Jeff
*Thomas Hallgren <**_thomas@tada.se_*
<mailto:thomas@xxxxxxx>*>*
Sent by: _equinox-dev-bounces@eclipse.org_
<mailto:equinox-dev-bounces@xxxxxxxxxxx>
01/11/2008 10:19 AM
Please respond to
Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>
To
Equinox development mailing list
<_equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>>
cc
<mime-attachment.gif>
Subject
[equinox-dev] OBR
<mime-attachment.gif> <mime-attachment.gif>
Hi,
I'm wonder if any work has been done within Eclipse to
deal with OBR
repositories, and if so, how can I get access to that. If
not, and if no
one has a better idea, I'm planning to start an IP-zilla
to get the
Apache Felix OBR approved since we will want to map that
kind of
repositories in Buckminster and also provide OBR's as an
alternative to
update sites in the spaces project.
Regards,
Thomas Hallgren
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>_
__https://dev.eclipse.org/mailman/listinfo/equinox-dev_
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>_
__https://dev.eclipse.org/mailman/listinfo/equinox-dev_
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>_
__https://dev.eclipse.org/mailman/listinfo/equinox-dev_
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>_
__https://dev.eclipse.org/mailman/listinfo/equinox-dev_
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>_
__https://dev.eclipse.org/mailman/listinfo/equinox-dev_
_______________________________________________
equinox-dev mailing list_
__equinox-dev@eclipse.org_ <mailto:equinox-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
------------------------------------------------------------------------
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
