paulrutter commented on PR #552:
URL: https://github.com/apache/felix-dev/pull/552#issuecomment-5532528269

   Added the silent-degradation warning, and the upstream half that makes it 
possible — [plurl#63](https://github.com/eclipse-osgi-technology/plurl/pull/63) 
now has a second commit.
   
   The problem: the plurl copy that wins the install in a JVM is the one that 
routes, and it may be older than the copy this framework brought. We register 
successfully and are then silently misrouted, with no way to tell — `bundle:` 
URLs can only be attributed by the UUID they carry, so without 
`shouldHandle(protocol, spec)` they go to whichever factory registered first.
   
   Upstream now answers a `plurlCapabilities` query. An implementation 
predating it rejects the operation with `IOException`, so absence of an answer 
is the answer and needs no cooperation from already-released plurl.
   
   - [`1947fc4`](https://github.com/apache/felix-dev/commit/1947fc465e) — 
vendored plurl change
   - [`45b65b6`](https://github.com/apache/felix-dev/commit/45b65b665c) — Felix 
warns at startup when the installed router can't route `bundle:` URLs, instead 
of leaving it to surface later as a failed resource lookup. The test pins the 
vendored copy's capability, so re-vendoring an older plurl fails there rather 
than quietly turning the warning on for everyone.
   
   Also [`cdd41d1`](https://github.com/apache/felix-dev/commit/cdd41d1244): the 
vendored plurl sources carry `Copyright (c) Contributors to the Eclipse 
Foundation` and were credited in no legal file — not NOTICE, not LICENSE, not 
DEPENDENCIES. Added the NOTICE entry alongside the existing OSGi Alliance one, 
which is the same case; no LICENSE change needed since plurl is ALv2 too. RAT 
doesn't catch this, it only checks source headers.
   
   Framework suite at the pre-existing baseline. @tjwatson no action needed on 
the Felix commits, but the capability commit upstream is take-it-or-leave-it — 
the selection commit stands on its own without it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to