Instead of forking I would urge you to help updating the existing project. What is currently blocking a new release is that the karaf itests is failing. Not using OSGi my self I would really need help with this. An alternative would be to drop all OSGi support from camel-extra which I would be fine with.
But as Cause say this should be discussed on the camel-extra mailing list http://camel-extra.1091541.n5.nabble.com/ // Pontus On Fri, 9 Jun 2017 at 19:18 Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > You can fork any github repo, that is allowed for anyone to do. > > For example you can fork it, do some code changes in your own branch, > and then for example build the JARs locally and share / use them > within your own company (internally). That is what companies can do to > do their own patching etc. > > But you cannot for example publish from your own fork to a public > maven repo, as if it was an official release from camel-extra etc. > > > > On Fri, Jun 9, 2017 at 4:50 PM, fabryprog <fabrizio.spat...@bizmate.it> > wrote: > > Hello claus. > > > > i ask again: can i fork camel-esper project and upgrade and push it into > > another repo? > > > > Into an opensource world: nothing is impossible! :-) > > > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Esper-out-of-camel-extra-package-tp5802466p5802806.html > > Sent from the Camel Development mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
