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 <tal.li...@threecrickets.com> > 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 branch, it's its own tiny repository. I know you've made > many efforts to make things easier for contributers, but alas it's still > too cumbersome for me. The Restlet repository is enormous and unwieldy, and > in fact I haven't been able to build it at all. It's just too much effort > over no clear gain to be part of the "incubator" at this point. Maven > builds, especially, make it trivial to use the Restlet binaries without > having to be part of the git tree. Just treat the project as an incubator > if you like! > > > > 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 point of > > view you can't offer all the available open source licenses and would > need > > to pick one (I suggest Apache license). > > > > Best regards, > > Jerome > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3068100 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3068101
