spockframework / spockframework/spock
Check for multiple Spock versions on class path
Open
Nobody has claimed this yet.
Module-Core
Type-Enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Originally reported on Google Code with ID 68
Every once in a while, users run into NoSuchMethodError etc. because they have multiple
Spock
versions on the class path (without being aware of it). We should check for this problem
(either
always or when an exception like NoSuchMethodError occurs) and tell the user what's
wrong.
Reported by pniederw on 2010-02-10 12:49:20
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reproducing the reported NoSuchMethodError with multiple Spock versions on the class path, then trace how Spock reports class-loading failures. Done means the conflicting versions are detected and the user is told what is wrong.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100