Hi , > Looking at the number of issues, commits & messages, it looks like JEXL does > not have a very voicefull community; are there still some committers around > or is the project in a semi-abandoned state?
all Commons Committers can (theoretically) apply patches. But it cannot be too bad to bring back attention to this project. If you are able to contribute patches and bring up discussion with JEXL again, it might happen that this component gets more active again. > If so, I suppose it would be OK to "fork" a JEXL2 project (probably as a > Google project ) so some features could be added. It would stay true to the > Apache original and could be unforked if ever needed. > Opinions, alternatives ? If you do it with google its always a question of incubating the fork - this time consuming, confusing etc. Its better to apply patches on Jira and tell people on the mailinglist what you did. I might be able to help with committing those patches in the week after next week. Btw, if you would like to bring JEXL to Java 5 (just saw in one of your issue descriptions) you should bring this up in the mailinglist. I think it should be possible to make a branch or something like that. Happy patching :-) Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
