Hi Steven Let me take a look then (including in the prop).
I will keep you posted. Regards JB On Wed, Feb 18, 2026 at 3:13 PM Steven Huypens <[email protected]> wrote: > Hi JB, > > I had a look at the code, but I’m not entirely confident about the required > changes, so I’d prefer if you could take care of it. > > That said, I did notice a potential issue in the snippet below. I would > expect the property key to include .offline: > > if (offline) { > props.put(ORG_OPS4J_PAX_URL_MVN_PID + "offline", "true"); > } > > Perhaps it should read ".offline" instead? > > Kind regards, > Steven > > On Tue, Feb 17, 2026 at 11:03 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi Steven > > > > Yes, a resolver update is also needed. I gonna address that for 4.4.11 > that > > can happen quickly (there's also Hibernate feature, etc). > > > > Feel free to submit a PR (or let me know if you prefer I do it), I will > > deal with the resolver update. > > > > Regards > > JB > > > > On Tue, Feb 17, 2026 at 10:43 AM Steven Huypens < > [email protected]> > > wrote: > > > > > Hi JB, > > > > > > With the release of Karaf 4.4.10 and Pax URL 2.7.0, I was hoping to > > finally > > > make use of splitRepositories. However, if I understand correctly, the > > > karaf-maven-plugin still requires an enhancement: > > > > > > https://issues.apache.org/jira/browse/KARAF-7667 > > > > > > Based on this discussion, the fix seems relatively straightforward: > > > > > > > > > > > > https://github.com/ops4j/org.ops4j.pax.url/issues/417#issuecomment-1500427845 > > > > > > Would you prefer that I submit a pull request for this, or would you > > rather > > > implement it yourselves? > > > > > > Kind regards, > > > Steven > > > > > > On Wed, Feb 4, 2026 at 11:40 AM Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > > > > Hi Steven > > > > > > > > Grzegorz and I worked on the Pax URL 3.x upgrade in Karaf. > > > > > > > > The problem is about webbundle URL handler that needs > jakarta.servlet, > > > not > > > > yet supported by Karaf (as it still uses Pax Web 8.x). > > > > > > > > As a workaround, Pax URL 2.7.0 has been released and it will be used > by > > > > Karaf (for now). Pax URL 2.7.0 is exactly the same as Pax URL 3.0.1 > but > > > > using javax.servlet instead of jakarta.servlet. > > > > > > > > So, Karaf will be upgraded to Pax URL 2.7.0, which includes the fix > you > > > are > > > > looking for. > > > > > > > > Regards > > > > JB > > > > > > > > On Tue, Feb 3, 2026 at 2:22 PM Steven Huypens < > > [email protected]> > > > > wrote: > > > > > > > > > Hi all, > > > > > > > > > > I'd like to know when pax-url-aether will be upgraded to 3.x in > > Karaf. > > > > We'd > > > > > like to use this: > > > https://github.com/ops4j/org.ops4j.pax.url/issues/417 > > > > > > > > > > Any plans? > > > > > > > > > > Kind regards, > > > > > Steven > > > > > > > > > > > > > > >
