Hi Paul, The old enRoute code has been deprecated and is not under active development from anyone at the Alliance. If you would like something fixed then a pull request against the deprecated branch would be the right way to go.
For future reference if you want a long-term stable build you should avoid depending directly on branches in your build configuration and depend on tags (or just specific commits). Branches can (and do) change over time in ways which may change the result of your build. Tim Sent from my iPhone > On 15 May 2018, at 12:31, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > >> On 15/05/2018 6:43 PM, Tim Ward wrote: >> The correct link is >> https://github.com/osgi/osgi.enroute/blob/deprecated/osgi.enroute.pom.distro/distro-pom.xml >> >>> 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 > Thanks for correct link Tim, > > But what process is required to update the distro-pom? > Adding dependencies to central.xml as suggested by Peter does not work for me. > Do I need to create a pull request on the github distro pom? > > Paul > _______________________________________________ > 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
