The correct link is https://github.com/osgi/osgi.enroute/blob/deprecated/osgi.enroute.pom.distro/distro-pom.xml
Sent from my iPhone > On 15 May 2018, at 09:14, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > > This does not work for me and the link to the distro pom is dead. > Is it still possible to alter the distro now that we have the new enRoute? > If so how would I do this as I am tied to bndtools 3.3 for now? > The latest jetty bundle is now at 4.0.0 > > Paul Fraser > >> On 1/12/2017 8:18 PM, Peter Kriens wrote: >> You can add the newer Jetty in your pom.xml in cnf/central.xml in your >> workspace. Need to touch build.bnd so Eclipse rebuilds. The latest distro >> pom on Github is actually 3.2 and should drag in the proper Jetty >> transitively? >> (https://github.com/osgi/osgi.enroute/blob/master/osgi.enroute.pom.distro/distro-pom.xml) >> >> Kind regards, >> >> Peter Kriens >> >>> On 1 Dec 2017, at 07:32, Paul F Fraser via osgi-dev >>> <osgi-dev@mail.osgi.org> wrote: >>> >>> Hi, >>> >>> The jetty bundles in the current distro (the one I have) are version 3.1 >>> which imports jetty 9.2.10. >>> >>> The latest felix bundle is 3.4.6 which imports jetty 9.3.9. >>> >>> What needs to be done to upgrade the distro or how can I force the resolver >>> to ignore the old version and work from a version in the local repo? >>> >>> Paul Fraser >> > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
