On 6/1/19 12:25 PM, Nathan Bubna wrote: > Yeah, adopting Spring support is unlikely to be much burden and seems well > worthwhile. > > On Sat, Jun 1, 2019 at 1:48 AM Claude Brisson <cla...@renegat.net.invalid> > wrote: > >> Hi. >> >> We are aware of the situation, and we were more or less expecting >> someone to make such a proposal. Yes, it will benefit both communities. >> >> +1 for me. I guess that if your patch includes proper test cases, >> support won't be problematic. >> >> Claude >
Ok, great, thanks Claude and Nathan for the positive feedback. I'm just about to head out for a couple of weeks of vacation, but I'll look to do some work on this later in June. I'll be in touch with any questions. I do have 2 initial questions: 1) From the POMs it looks like Velocity is still primarily using Apache's Subversion repo, but there are also GitHub mirrors. Didn't know how "official" the latter are. Would doing the work in Git and doing GitHub pull-requests work here, or do I need to produce a Subversion-compatible patch? 2) Do you have any upcoming release(s) scheduled that I should know about and work around? If you have one coming up in July/August, I could probably make that. Thanks, Brent
