Windows?
Works fine for me on OS X and Ubuntu.
Aslak
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cukes" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/cukes/-/6cFZGup6FJQJ.
> To post to this group, send email to cu...@googlegroups.com.
> To unsubscribe from this group, send email to
> cukes+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/cukes?hl=en.
>
> On Thu, Aug 18, 2011 at 6:20 PM, Konstantinos Papalias
> <pkwnst...@gmail.com> wrote:
>> Not sure if it's only me having this issue but while trying to build
>> cucumber-jvm with:
>> mvn clean install
>> it does fail in core project on ClasspathTest.
>> I'm attaching the generated errors for your convenience.
>
> Windows?
>
Should be easy to fix for Windows, just need to use backslashes in a few places.
Want to try fixing it?
Aslak.
--
Changing a test to make it pass is usually equivalent to sweeping dirt
under a carpet. It doesn't fix a problem, it just gives the illusion
of fixing it.
To make things work you'll have to make changes to Classpath.java so
it works on Windows. Maybe using File.PATH_SEPARATOR instead of "/" in
a few places will do the trick.
Aslak
Sent from my BlackBerry device on the Rogers Wireless Network
Of course, that goes without saying.
> Even if I manually fix the test-case for windows the first test will still
> fail with:
> looksUpInstantiableSubclassesOnClassPath(cucumber.runtime.ClasspathTest):
> expected:<[class cucumber.runtime.ClasspathTest$Wilma, class
> cucumber.runtime.ClasspathTest$Fred]> but was:<[]>
> By looking at the Classpath.java file we would need to replace the
> hard-coded forward slashes with File.separator plus all other Unix specific
> path attributes.
That sounds right. Please send a pull request when you have passing
tests, and I can verify that tests still pass on OS X/Linux.
Aslak
> Thanks,
> konstantinos