Hi Frederick! Thanks for posting this here. Currently, we have a 1.x branch that is stable and in a long-term maintenance mode and a 2.x branch that is not really ready for consumption yet. To be honest, it's been so long since i worked on 2.x that i can't remember what changes we did get done (i could go look). Most of the core committers are, for one reason or another, focusing their development energies elsewhere, with little intention to get back into it. That said, we do still actively oversee the project and are more than willing to help mentor any newcomers in navigating the ASF processes for contributing and working on new releases.
It sounds to me like the work you have done thus far is largely non-compatible with the 1.x branch. In particular, the removal of Texen/Anakia and LogChute. I'm not especially familiar with SLF4J, so i would love to hear your reasons for yanking the LogChute adaptor instead of just providing an SLF4J bridge for it. That said, if you are interested in jumping in on a 2.x branch, i would help you regardless of your decisions. People around here may have opinions on changes, but the "apache way" is that those who do the work should make the decisions. :) So, yes, we are interested in your work! Do you have it public anywhere we can look at it? Are you working on a fork of our git mirror? Or did you check it out of the subversion repo? The next question is whether you are interested in working through Apache's contribution/committer process. If so, you should take a look at the 2.x branch and consider putting a CLA (contributor's license agreement) on file with the ASF secretary, as that is needed for both large contributions and new committers (which you would hopefully become). -nathan On Thu, Sep 25, 2014 at 5:20 PM, Frederick N. Brier <fnbr...@gmail.com> wrote: > Dear Velocity Team Members, > > I was looking for a template engine that would work on Android, and had > used Velocity a couple of times, years ago. The latest version is 1.7. > There haven't been any code changes in 4 years, although there were some > recent bug reports. Log4j has some issues on Android and I shifted to > Maven from Ant back in its 2.x days. So I restructured the codebase to use > Maven, moved the Texen and Anakia code to the side, stripped out the custom > LogChute code and changed it to use SLF4J. There are some minor problems > just getting the 1.7 source distribution to build. I found a number of > bugs along the way and a number of the unit tests were not even being run > by the Ant build. I managed to get all but one of the unit tests to work > (UberSpect related) that had been working before, and several that were > not, are now. Several unit tests depended on the LogChute architecture, > which with great difficulty, I changed. Having unit tests depend on > logging feels like a hack, is very fragile, and difficult to understand > because it isn't clear where the logging statement is being executed. It > would be much better to restructure the code to use the more contemporary > IoC design patterns, so mock objects could be injected. Injecting the > MockIntrospectorCacheImpl was painful. Another unit test motivated me to > add an initial implementation of an EventListener for the Velocity engine. > > The rewritten library works under Android, but would still need a lot of > love before I'd be call it ready for a new release. What are Apache and > the Velocity team's plans for the project? Velocity is the template engine > used by Maven's Site component, so the project is still needed. My > priorities are to deliver my Android application, but if Apache is > interested, I could keep working and polishing it. Thank you for your time. > > Sincerely yours, > Frederick N. Brier > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > >
