Skip to content
Browse files

Bumped to 0.1.1

  • Loading branch information...
1 parent 2297c07 commit 71df79dddce69f88d930c598803d1048713e44b1 @marick marick committed Jun 30, 2010
View
13 NOTES
@@ -2,12 +2,17 @@ The process for pushing a new version is too complicated and
manual.
* Touch the new version number whenever its used.
+ (Should only be in the project files.)
* Run the tests.
-* make jar and rename it to midje-x.x.x.jar
-* make pom
+* lein jar and rename it to midje-x.x.x.jar
+* lein pom
* scp pom.xml midje-x.x.x.jar clojars@clojars.org:
-* Run the example and compare to stashed result. (It should
- fetch the new version.)
+* Go to the example, 'lein clean', and 'lein deps'. (It should fetch the
+ new version.)
+* Run the example and compare to stashed result.
+* Make a new version of 'run' in the example directory.
+* Try it out against the expected output.
+* DO NOT CLEAN.
* Make new downloads
* git tag -a -m "message" v.x.x.x
* Push to github
View
BIN downloads/semi-sweet-examples.tar
Binary file not shown.
View
BIN downloads/semi-sweet-examples.zip
Binary file not shown.
View
41 examples/semi-sweet-examples/README.html
@@ -4,6 +4,40 @@
</head>
<body>
+
+<p>
+Did you download the zip or tar file described as the
+easiest way to try out Midje?
+</p>
+
+<ul>
+ <li><b>Yes!</b>
+ <p>
+ If you're on Unix (including the Mac), the shell script <code>run</code> runs the tests:
+ </p>
+
+ <pre>
+ % run
+ </pre>
+
+ <p>
+ If you're on Windows, you can look at the contents of the
+ script (two lines) and translate them into Windows terms.
+ </p>
+
+ <p>
+ The file in this folder called
+ <code>run-expected-output</code> shows what
+ the results should look like.
+ </p>
+ </li>
+
+
+
+
+<li><b>No.</b>
+
+<p>
<ol>
<li>
<p>
@@ -38,11 +72,14 @@
% lein test
</pre>
<p>
- Keep in mind that some of the "tests" intentionally fail.
+ The file in this directory called
+ <code>lein-expected-output</code> shows what
+ the results should look like.
</p>
</li>
</ol>
-
+</li>
+</ul>
</body> </html>
View
4 examples/semi-sweet-examples/project.clj
@@ -1,7 +1,7 @@
-(defproject semi-sweet-simple "0.1.0"
+(defproject semi-sweet-simple "0.2.0"
:description "An example of using Midje semi-sweet mocking"
:dependencies [[org.clojure/clojure "1.1.0"]
[org.clojure/clojure-contrib "1.1.0"]]
- :dev-dependencies [[midje "0.1.0"]]
+ :dev-dependencies [[midje "0.1.1"]]
)
View
2 examples/semi-sweet-examples/run
@@ -1,2 +1,2 @@
cd test
-java -cp ../lib/clojure-1.1.0.jar:../lib/clojure-contrib-1.1.0.jar:../lib/midje-0.1.0.jar clojure.main -i semi_sweet_simple/core_test.clj -e '(ns semi-sweet-simple.core-test)(run-tests)'
+java -cp ../lib/clojure-1.1.0.jar:../lib/clojure-contrib-1.1.0.jar:../lib/midje-0.1.1.jar clojure.main -i semi_sweet_simple/core_test.clj -e '(ns semi-sweet-simple.core-test)(run-tests)'
View
2 project.clj
@@ -1,4 +1,4 @@
-(defproject midje "0.1.0"
+(defproject midje "0.1.1"
:description "A mock/stubbing library for Clojure"
:dependencies [[org.clojure/clojure "1.1.0"]
[org.clojure/clojure-contrib "1.1.0"]])

0 comments on commit 71df79d

Please sign in to comment.
Something went wrong with that request. Please try again.