THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Code review for any outstanding issues - We need to give JEXL a once over to make sure there are no obvious outstanding issues or bugs that need fixing.
- Call for Comments - Once we are certain there are no outstanding issues, call for comments on commons-dev
- Cut a release
- Publish to Maven repo
So, some outstanding issuesthis is somewhat ridiculous because components in Commons Proper should be released (or at least have a solid release plan). Let's get on this, what needs to be done?:
- Documentation
- Syntax Page - We need a page devoted to syntax, preferably we'll have an explanation of the syntax and a big table with some examples.
- Examples Page - Keep the small example on the front page, we'll need a quick page that reads like a small user's guide with a section demonstrating every usage situation.
- Related Resources on Index Page - Develop this related resources section put some more links to Velocity resources.
- package.html - Some of the packages have package.html content. We need to make sure that a developer has the necessary tools to use Jexl from the Javadoc alone.
- JavaDoc - We need some explanation about Pre and Post resolvers. Esp. why and how someone would ever want to use them. Also, keep an eye out for informal JavaDoc - the jexl package had some JavaDoc that sounded like development planning.
- Refactoring
- Unused Classes - There was one class (sort sort of LogAdapter) which was not referenced in thie commons-jexl project. Make sure that each class in jexl is relevant.
- General Refactoring - How's that for a catch all bullet point?