Some jMock news... Version 1.1.0 RC1 has been published on the jMock site. Continuous Integration is working again. Snapshots are built and the website updated as we commit changes. --Nat.
Hi Nat, Nat Pryce wrote on Friday, April 28, 2006 9:28 PM: > Some jMock news... > > Version 1.1.0 RC1 has been published on the jMock site. > > Continuous Integration is working again. Snapshots are built and the > website updated as we commit changes. You mensioned on some of my issues "Hamcrest", but I could not find any reference about this project. - Jörg
On 5/2/06, Jörg Schaible <Joerg.Schaible@...> wrote: > You mensioned on some of my issues "Hamcrest", but I could not find any reference about this project. Hamcrest is a project Joe started to pull together all the Constraints/Matchers/etc. from different projects into one place so that they can be shared among different projects. It's at Sourceforge (http://www.sf.net/projects/hamcrest). I don't know what's happening on it at the moment. If it snowballs I was thinking of using it for jMock 2. We can't use it in jMock 1 without breaking backwards compatability. --Nat.
What is the recommended procedure for contributing documentation? Word files? Also, what is the recommended procedure for contributing javadocs if one is not a committer? Thanks much, /r:b: On 4/28/06, Nat Pryce <nat.pryce@...> wrote: > Some jMock news... > > Version 1.1.0 RC1 has been published on the jMock site. > > Continuous Integration is working again. Snapshots are built and the > website updated as we commit changes. > > --Nat. > -- ************************************************ Richard Bondi 33 Royal Ave #3 Cambridge, MA 02138-1301 Email: rbondi at gmail.com Phone: (617) 938-9562 ************************************************
check out the sources, we use simple HTML. Not sure what to do with javadoc. How about if you send a patch with a couple of examples and we'll take it from there? S. On 2 May 2006, at 13:09, Richard Bondi wrote: > What is the recommended procedure for contributing documentation? > Word files? > > Also, what is the recommended procedure for contributing javadocs if > one is not a committer? > > Thanks much, > /r:b: > > On 4/28/06, Nat Pryce <nat.pryce@...> wrote: >> Some jMock news... >> >> Version 1.1.0 RC1 has been published on the jMock site. >> >> Continuous Integration is working again. Snapshots are built and the >> website updated as we commit changes. >> >> --Nat. >> > > > --(Continue reading)
Not sure what you mean by "the sources" for documentation? Do you just mean what is on the site now? There is no documentation apart from javadocs in the RC download. I will email some source code with extra javadocs to the list, as you suggest. Best, /r:b: On 5/2/06, Steve Freeman <steve@...> wrote: > check out the sources, we use simple HTML. > > Not sure what to do with javadoc. How about if you send a patch with > a couple of examples and we'll take it from there? > > S. > > On 2 May 2006, at 13:09, Richard Bondi wrote: > > What is the recommended procedure for contributing documentation? > > Word files? > > > > Also, what is the recommended procedure for contributing javadocs if > > one is not a committer? > > > > Thanks much, > > /r:b: > > > > On 4/28/06, Nat Pryce <nat.pryce@...> wrote: > >> Some jMock news... > >>(Continue reading)
I mean a checkout from CVS. Everything's in there. By documentation, I meant some of the tutorials we've written which you can see on the jMock site. This is probably not a strictly correct use of the term :) S. On 2 May 2006, at 16:56, Richard Bondi wrote: > Not sure what you mean by "the sources" for documentation? Do you just > mean what is on the site now? There is no documentation apart from > javadocs in the RC download. > > I will email some source code with extra javadocs to the list, as > you suggest. > > Best, > /r:b: > > On 5/2/06, Steve Freeman <steve@...> wrote: >> check out the sources, we use simple HTML. >> >> Not sure what to do with javadoc. How about if you send a patch with >> a couple of examples and we'll take it from there? >> >> S. >> >> On 2 May 2006, at 13:09, Richard Bondi wrote: >> > What is the recommended procedure for contributing documentation? >> > Word files? >> > >> > Also, what is the recommended procedure for contributing(Continue reading)
All documentation is in plain, unadorned XHTML. The website build script adorns the plain content with navigation menus, logos, styles and munges the text a bit to make it look better when printed on paper. The documentation and all the rest of the website is in CVS. Check it out and play around. To build the website you'll need a recent version of Ruby and REXML. However, to browse the plain content, any web browser will do. To edit the content I've been using WYSIWYG XHTML editors like Amara and XML Mind. --Nat. On 5/2/06, Richard Bondi <rbondi@...> wrote: > What is the recommended procedure for contributing documentation? Word files? > > Also, what is the recommended procedure for contributing javadocs if > one is not a committer? > > Thanks much, > /r:b: > > On 4/28/06, Nat Pryce <nat.pryce@...> wrote: > > Some jMock news... > > > > Version 1.1.0 RC1 has been published on the jMock site. > > > > Continuous Integration is working again. Snapshots are built and the > > website updated as we commit changes. > >(Continue reading)
Hooray! Well done guys!
Look forward to using more of it.
Cheers,
Patrick
Some jMock news...
Version 1.1.0 RC1 has been published on the jMock site.
Continuous Integration is working again. Snapshots are built and the
website updated as we commit changes.
--Nat.
Nat Pryce wrote on Thursday, May 04, 2006 12:01 PM: > On 5/2/06, Jörg Schaible <Joerg.Schaible@...> wrote: >> You mensioned on some of my issues "Hamcrest", but I could > not find any reference about this project. > > Hamcrest is a project Joe started to pull together all the > Constraints/Matchers/etc. from different projects into one place so > that they can be shared among different projects. > > It's at Sourceforge (http://www.sf.net/projects/hamcrest). I don't > know what's happening on it at the moment. If it snowballs I was > thinking of using it for jMock 2. We can't use it in jMock 1 without > breaking backwards compatability. Ah. Did not show up on sf last time i searched for it. I'll contact Joe directly. Thanks. - Jörg
RSS Feed