Ok, it is fixed in trunk now. Just a silly bug.
-> richard
On 3/11/11 9:16, Richard S. Hall wrote:
On 3/11/11 9:14, Richard S. Hall wrote:
On 3/11/11 2:35, Guillaume Nodet wrote:
Btw, the bundle is available at:
http://repo2.maven.org/maven2/org/ops4j/pax/url/pax-url-mvn/1.2.4/pax-url-mvn
On 3/11/11 9:14, Richard S. Hall wrote:
On 3/11/11 2:35, Guillaume Nodet wrote:
Btw, the bundle is available at:
http://repo2.maven.org/maven2/org/ops4j/pax/url/pax-url-mvn/1.2.4/pax-url-mvn-1.2.4.jar
I just have to try to start this bundle to see the error?
Answering myself, yes.
Ok, I
On 3/11/11 2:35, Guillaume Nodet wrote:
Btw, the bundle is available at:
http://repo2.maven.org/maven2/org/ops4j/pax/url/pax-url-mvn/1.2.4/pax-url-mvn-1.2.4.jar
I just have to try to start this bundle to see the error?
-> richard
On Fri, Mar 11, 2011 at 08:33, Guillaume Nodet wrote:
I'
Btw, the bundle is available at:
http://repo2.maven.org/maven2/org/ops4j/pax/url/pax-url-mvn/1.2.4/pax-url-mvn-1.2.4.jar
On Fri, Mar 11, 2011 at 08:33, Guillaume Nodet wrote:
> I've had a look at the resolution problem i had with 3.0.8 but now hit
> a weird resolution exception on a singleton
I've had a look at the resolution problem i had with 3.0.8 but now hit
a weird resolution exception on a singleton bundle:
karaf@root> osgi:start --force 1
Error executing command: Unresolved constraint in bundle
org.ops4j.pax.url.mvn [1]: Unable to resolve 1.0
karaf@root> headers 1
OPS4J Pax Url
On 3/10/11 15:29, David Bosschaert wrote:
Hi Richard,
On 10 March 2011 20:01, Richard S. Hall wrote:
A heads up...
I've committed a pretty substantial patch to the framework resolver, which
furthers the goal of eventually making it a separate module/subproject.
Previously, the resolver did no
Hi Richard,
On 10 March 2011 20:01, Richard S. Hall wrote:
> A heads up...
>
> I've committed a pretty substantial patch to the framework resolver, which
> furthers the goal of eventually making it a separate module/subproject.
> Previously, the resolver did not actually handle fragments or singl
A heads up...
I've committed a pretty substantial patch to the framework resolver,
which furthers the goal of eventually making it a separate
module/subproject. Previously, the resolver did not actually handle
fragments or singleton bundles and instead left this up to the user of
the resolver
