-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Running cucumber tests in Eclipse causes exception #259
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Why eclipse does that I have no clue. What I know is that given I have a maven project in eclipse with the directory layout:
For fixing #165 the md5 checksum was introduced. But can't we just ignore multiple feature files having the identical md5 checksum? So if there are 2 feature files on the classpath with identical md5 checksum only one of them is executed. If there are two feature files on the classpath having different md5 checksums a CucumberException is thrown. If I got it right this would not break #165. |
@remast that sounds like a good approach |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Running cucumber tests in eclipse causes an exception because the *.feature files exist duplicated in the classpath. Eclipse puts all resources including the *.feature files in the classpath. Additionally the classpath contains the directory with the resources.
-> As a result two identical versions of the same *.feature files exist in the classpath.
This causes the following code in the FeatureBuilder to throw a CucumberException:
Having two identical *.feature files on the claspath does no harm. So I suggest that's tolerated as long as both files have the same checksum. If desired a warning could be logged.
The text was updated successfully, but these errors were encountered: