That's fine Tal, whatever works best for you. Merging by hand won't be a
big issue anyway.
You might want to enter an issue in RF repo to let people discover this
support and let us communicate over it.
Best regards,
Jerome
2013/11/7 Tal Liron
> Thanks, Jerome.
>
> I picked the Apache License
Thanks, Jerome.
I picked the Apache License 2.0, and am hosting it as a separate project. I'm
assigning joint copyright on it to Restlet S.A.S, per the contributor
agreement, so you are free to merge it should you ever wish to do so:
https://github.com/tliron/restlet-jetty9
Rather than a branc
I suggest that you create a new
/restlet-framework-java/master/incubator/org.restlet.ext.jetty9 extension
by copying then adapting the o.r.e.jetty extension.
You can always have you own branch in GitHub and then merge it back when
master becomes ready for RF 3.0 (Java 7), but from a licensing poin
So, I went ahead and created a Jetty 9 extension for Restlet 2.2:
https://github.com/tliron/restlet-jetty9
It's not much tested (especially SSL), but it does work! There are also 2
helper parameters that I still haven't found how to duplicate on Jetty 9, so
they are just be ignored. Actually, I
4 matches
Mail list logo