-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retire http://jmock.org/ #110
Comments
I've raised this before. I agree.
We also need to upgrade to junit5
…On Tue, 4 Sep 2018, 14:30 Toby, ***@***.***> wrote:
http://jmock.org/ seems really out of date and a bit misleading.
Shall we retire it and favour the Github docs? Otherwise, it could prob
use a freshen up.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#110>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAQK0FTyfNONMgyBcSk2bpZQdxkrGCvgks5uXoB7gaJpZM4WY_dV>
.
|
Could somebody explain how I edit the github pages to point to new releases? |
I've figured this out and pointed jmock.org at 2.9.0. |
Suggest considering moving docs to /docs directory. GH can publish from there. |
Agreed, /doc approach is better than switching branches.
I note somebody just did this for Hamcrest.
…On Tue, 30 Oct 2018 at 11:05, Steve Freeman ***@***.***> wrote:
Suggest considering moving docs to /docs directory. GH can publish from
there.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#110 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQK0KLrZZt5jKoaxrNpBvDSylKqBYgeks5uqDJrgaJpZM4WY_dV>
.
|
Updated the site to announce jMock 2.10.0-RC3 which supports JDK11. |
Searching for jmock on google leads to http://jmock.org/download.html which still mentions 2.6.1 (this release doesn't even exist) as latest release. |
http://jmock.org/ seems really out of date and a bit misleading.
Shall we retire it and favour the Github docs? Otherwise, it could prob use a freshen up.
The text was updated successfully, but these errors were encountered: