Hi Brian, I have them on sight, but didn't have the time; will probably do next week, but can't guarantee you anything, I also want to look into your JSPWIKI-812 issues. OTOH, JSPWIKI-813 has been solved by Harry a few hours ago, and you've uploaded a new patch on JSPWIKI-814 today, so we can only ask for your patience, right now JSPWiki is 100% volunteer-driven time.
br, juan pablo On Mon, Mar 3, 2014 at 7:59 PM, Glen Mazza <glen.ma...@gmail.com> wrote: > According to JIRA, the status of your issues are "OPEN", the same as 130+ > other issues. So long as they are open they will never be forgotten. It's > just that we're volunteers with limited time and our own JSPWiki priorities > which may not be in sync with yours. If you need faster response time, you > may wish to look at a paid commercial Wiki alternative or a larger > open-source Wiki project, or get others to vote on JIRA for your issues to > improve their prioritization. > > Glen > > > On 03/03/2014 04:08 AM, Brian Burch wrote: > >> I can see that everyone has been busy over the last couple of weeks, so I >> have been waiting patiently. Now I'm beginning to wonder whether my two >> proposed changes to the trunk have been overlooked? >> >> I re-opened JIRA JSPWIKI-813 because the test class triggered log4j >> configuration error messages. My patch ensures the unit testing log4j >> environment is initialised properly. >> >> JSPWIKI-814 has been open a month or so. My original patches were >> incomplete and I had to write some more test cases to explore the problem >> fully. The set of patches I submitted 2 weeks ago seem to be stable and >> cover all sensible alternatives. >> >> Could someone spare a few minutes to review my patches and, if >> acceptable, commit them to the trunk for me? >> >> Thanks in anticipation, >> >> Brian >> > >
