Closed GoogleCodeExporter closed 8 years ago
Annoying, but thanks for mentioning.
Original comment by marceloverdijk
on 7 Jan 2013 at 1:02
You most likely don't need the plugin (unless you make use of its single
feature).
In the next version, the plugin will be more useful, and will work with Maven
3.x.
Original comment by pnied...@gmail.com
on 7 Jan 2013 at 1:18
Sounds good. It turns out that I have do to "find-specs" in my maven build via
the spock-maven plugin. If I remove it, maven doesn't find or run my spock
tests.
Thanks, Peter!
Original comment by ambarsek...@gmail.com
on 7 Jan 2013 at 1:59
Some more information (I'm not using maven3):
[19:30:24] ~ $ mvn -version
Apache Maven 2.2.1 (rdebian-8)
Java version: 1.7.0_09
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en_IN, platform encoding: UTF-8
OS name: "linux" version: "3.2.0-35-generic" arch: "amd64" Family: "unix"
Original comment by ambarsek...@gmail.com
on 7 Jan 2013 at 2:00
Without the plugin, you'll have to adhere to the Maven/Surefire conventions for
test class names (*Test etc.), or reconfigure them (e.g. to *Spec). When using
the plugin, you can have arbitrary class names.
Original comment by pnied...@gmail.com
on 7 Jan 2013 at 2:07
Ah, thanks for pointing that out. In that case, I'll cheerfully continue to use
the spock-maven plugin :)
Original comment by ambarsek...@gmail.com
on 7 Jan 2013 at 2:11
Issue 295 has been merged into this issue.
Original comment by pnied...@gmail.com
on 25 Jan 2013 at 12:28
Issue 295 has been merged into this issue.
Original comment by pnied...@gmail.com
on 25 Jan 2013 at 12:29
Issue 303 has been merged into this issue.
Original comment by pnied...@gmail.com
on 21 Mar 2013 at 1:24
Issue 312 has been merged into this issue.
Original comment by pnied...@gmail.com
on 17 May 2013 at 3:30
Why is this issue marked as fixed? As far as I can tell the latest artifact
still has the incorrect version in the plugin descriptor.
Browse Spock artifacts in Maven central:
http://search.maven.org/#browse|15844207
The latest, as of today, is 0.7-groovy-2.0
Download the file, open it up and open META-INF/maven/plugin.xml and the
version is still <version>0.7-groovy-2.0-SNAPSHOT</version>
Is it "fixed" because there is a workaround?
Original comment by n...@faceture.com
on 28 Dec 2013 at 5:09
It's fixed in the development version (1.0-SNAPSHOT), which is available from
http://oss. sonatype.org/content/repositories/snapshots/.
Original comment by pnied...@gmail.com
on 28 Dec 2013 at 5:30
Issue 365 has been merged into this issue.
Original comment by pnied...@gmail.com
on 28 May 2014 at 4:40
How do I convert the directory back to the jar in the work around?
Original comment by ada...@gmail.com
on 16 Sep 2014 at 9:20
Original issue reported on code.google.com by
ambarsek...@gmail.com
on 26 Dec 2012 at 3:04